First published: Mon Jun 29 2020(Updated: )
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.
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Coturn Project Coturn | <4.5.1.3 | |
Debian Debian Linux | =8.0 | |
Debian Debian Linux | =9.0 | |
Debian Debian Linux | =10.0 | |
Fedoraproject Fedora | =31 | |
Fedoraproject Fedora | =32 | |
Canonical Ubuntu Linux | =16.04 | |
Canonical Ubuntu Linux | =18.04 | |
Canonical Ubuntu Linux | =19.10 | |
Canonical Ubuntu Linux | =20.04 | |
openSUSE Leap | =15.2 | |
debian/coturn | 4.5.2-3 4.6.1-1 4.6.1-2 | |
ubuntu/coturn | <4.5.0.7-1ubuntu2.18.04.2 | 4.5.0.7-1ubuntu2.18.04.2 |
ubuntu/coturn | <4.5.1.1-1.1ubuntu0.19.10.1 | 4.5.1.1-1.1ubuntu0.19.10.1 |
ubuntu/coturn | <4.5.1.1-1.1ubuntu0.20.04.1 | 4.5.1.1-1.1ubuntu0.20.04.1 |
ubuntu/coturn | <4.5.1.3-1 | 4.5.1.3-1 |
ubuntu/coturn | <4.5.0.3-1ubuntu0.3 | 4.5.0.3-1ubuntu0.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.