CVE-2025-69217: Coturn has unsafe nonce and relay port randomization due to weak random number generation.
coturn is a free open source implementation of TURN and STUN Server. Versions 4.6.2r5 through 4.7.0-r4 have a bad random number generator for nonces and port randomization after refactoring. Additionally, random numbers aren't generated with openssl's RANDbytes but libc's random() (if it's not running on Windows). When fetching about 50 sequential nonces (i.e., through sending 50 unauthenticated allocations requests) it is possible to completely reconstruct the current state of the random number generator, thereby predicting the next nonce. This allows authentication while spoofing IPs. An attacker can send authenticated messages without ever receiving the responses, including the nonce (requires knowledge of the credentials, which is e.g., often the case in IoT settings). Since the port randomization is deterministic given the pseudorandom seed, an attacker can exactly reconstruct the ports and, hence predict the randomization of the ports. If an attacker allocates a relay port, they know the current port, and they are able to predict the next relay port (at least if it is not used before). Commit 11fc465f4bba70bb0ad8aae17d6c4a63a29917d9 contains a fix.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-69217?
CVE-2025-69217 has been classified with a significant severity due to its potential impact on random number generation.
How do I fix CVE-2025-69217?
To fix CVE-2025-69217, upgrade coturn to version 4.7.0 or later which includes a proper random number generator.
What versions of coturn are affected by CVE-2025-69217?
CVE-2025-69217 affects coturn versions from 4.6.2r5 to 4.7.0-r4 inclusive.
What is the risk of using an affected version of coturn for CVE-2025-69217?
Using an affected version of coturn may lead to security vulnerabilities due to inadequate nonce and port randomization.
What should I do if I can't immediately update due to CVE-2025-69217?
If an immediate update is not possible for CVE-2025-69217, consider implementing additional security controls to mitigate risks from the uncertainty in random number generation.