First published: Thu Apr 02 2020(Updated: )
GnuTLS 3.6.x before 3.6.13 uses incorrect cryptography for DTLS. The earliest affected version is 3.6.3 (2018-07-16) because of an error in a 2017-10-06 commit. The DTLS client always uses 32 '\0' bytes instead of a random value, and thus contributes no randomness to a DTLS negotiation. This breaks the security guarantees of the DTLS protocol.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/gnutls28 | 3.6.7-4+deb10u8 3.6.7-4+deb10u10 3.7.1-5+deb11u3 3.7.9-2 3.8.1-4 | |
ubuntu/gnutls28 | <3.6.9-5ubuntu1.1 | 3.6.9-5ubuntu1.1 |
ubuntu/gnutls28 | <3.6.13-2 | 3.6.13-2 |
GNU GnuTLS | >=3.6.3<3.6.13 | |
Canonical Ubuntu Linux | =19.10 | |
Debian Debian Linux | =10.0 | |
openSUSE Leap | =15.1 | |
Fedoraproject Fedora | =31 | |
Fedoraproject Fedora | =32 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2020-11501.
The severity of CVE-2020-11501 is high with a CVSS score of 7.4.
GnuTLS versions before 3.6.13 are affected by CVE-2020-11501.
CVE-2020-11501 allows an attacker to break the randomness of a DTLS negotiation, potentially compromising the security of the communication.
To fix CVE-2020-11501, update GnuTLS to version 3.6.13 or later.