CVE-2025-69217

{"id": "CVE-2025-69217", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2025-69217", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2025-12-30T13:57:12.783500Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 7.7, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 4.0, "exploitabilityScore": 3.1}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "coturn", "product": "coturn", "versions": [{"status": "affected", "version": ">= 4.6.2r5, <= 4.7.0-r4"}]}]}], "published": "2025-12-30T01:15:41.390", "references": [{"url": "https://github.com/coturn/coturn/commit/11fc465f4bba70bb0ad8aae17d6c4a63a29917d9", "source": "security-advisories@github.com"}, {"url": "https://github.com/coturn/coturn/commit/88ced471385869d7e7fbbc4766e78ef521b36af6", "source": "security-advisories@github.com"}, {"url": "https://github.com/coturn/coturn/security/advisories/GHSA-fvj6-9jhg-9j84", "source": "security-advisories@github.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-338"}]}], "descriptions": [{"lang": "en", "value": "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 RAND_bytes 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."}, {"lang": "es", "value": "coturn es una implementaci\u00f3n de c\u00f3digo abierto gratuita de servidor TURN y STUN. Las versiones 4.6.2r5 a 4.7.0-r4 tienen un generador de n\u00fameros aleatorios deficiente para nonces y la aleatorizaci\u00f3n de puertos despu\u00e9s de la refactorizaci\u00f3n. Adem\u00e1s, los n\u00fameros aleatorios no se generan con RAND_bytes de OpenSSL sino con random() de libc (si no se ejecuta en Windows). Al obtener aproximadamente 50 nonces secuenciales (es decir, mediante el env\u00edo de 50 solicitudes de asignaci\u00f3n no autenticadas), es posible reconstruir completamente el estado actual del generador de n\u00fameros aleatorios, prediciendo as\u00ed el siguiente nonce. Esto permite la autenticaci\u00f3n mientras se suplantan IPs. Un atacante puede enviar mensajes autenticados sin recibir nunca las respuestas, incluido el nonce (requiere conocimiento de las credenciales, lo cual es, por ejemplo, a menudo el caso en entornos IoT). Dado que la aleatorizaci\u00f3n de puertos es determinista dada la semilla pseudoaleatoria, un atacante puede reconstruir exactamente los puertos y, por lo tanto, predecir la aleatorizaci\u00f3n de los puertos. Si un atacante asigna un puerto de retransmisi\u00f3n, conoce el puerto actual y puede predecir el siguiente puerto de retransmisi\u00f3n (al menos si no se ha utilizado antes). El commit 11fc465f4bba70bb0ad8aae17d6c4a63a29917d9 contiene una soluci\u00f3n."}], "lastModified": "2026-10-13T08:10:00.137", "sourceIdentifier": "security-advisories@github.com"}