Improper Initialization in coturn
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7epss 1.9%
exploitation probability
1.9%top 23% of all CVEs
observed exploitation
nono source reports it
In coturn before version 4.5.1.3, there is an issue whereby STUN/TURN response buffer is not initialized properly. There is a leak of information between different client connections. One client (an attacker) could use their connection to intelligently query coturn to get interesting bytes in the padding bytes from the connection of another client. This has been fixed in 4.5.1.3.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L
Affected products
coturn · coturnReferences
http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00010.htmlhttps://github.com/coturn/coturn/blob/aab60340b201d55c007bcdc853230f47aa2dfdf1/ChangeLog#L15https://github.com/coturn/coturn/issues/583https://github.com/coturn/coturn/security/advisories/GHSA-c8r8-8vp5-6gcmhttps://lists.debian.org/debian-lts-announce/2020/07/msg00002.htmlhttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/5G35UBNSRLL6SYRTODYTMBJ65TLQILUM/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/TNJJO77ZLGGFJWNUGP6VDG5HPAC5UDBK/https://usn.ubuntu.com/4415-1/https://www.debian.org/security/2020/dsa-4711