CyberRota Analysis
AI-GeneratedCoturn versions prior to 4.15.0 are vulnerable to an on-path attack that allows an attacker to manipulate STUN requests by appending attributes after the MESSAGE-INTEGRITY field, potentially overriding allocation lifetimes, injecting permissions, or bypassing origin checks. The impact is primarily on the integrity of STUN communications, which could lead to unauthorized access or resource manipulation. Organizations using Coturn for TURN and STUN services should prioritize upgrading to version 4.15.0 to mitigate these risks, especially if they are not using TLS or DTLS.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Coturn is a free open source implementation of TURN and STUN Server. Prior to 4.15.0, an on-path attacker can append attributes after MESSAGE-INTEGRITY to an authenticated STUN request on plain UDP or TCP, adjust the STUN header length, and recompute the unkeyed FINGERPRINT while the original HMAC remains valid because it covers only the message prefix. Server-side parsing in src/server/ns_turn_server.c continues past MESSAGE-INTEGRITY through handle_turn_allocate(), handle_turn_create_permission(), handle_turn_refresh(), and handle_turn_command(), allowing trailing LIFETIME, XOR-PEER-ADDRESS, or ORIGIN attributes to override allocation lifetime, inject a permission, or bypass the origin check. TLS and DTLS deployments prevent this in-transit modification. This issue is fixed in version 4.15.0.