CVE-2020-11501: High severity GNU GnuTLS vulnerability
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/gnutls28to a version that resolves this vulnerability.Fixed in 3.7.9-2+deb12u7Fixed in 3.8.9-3+deb13u4Fixed in 3.8.13-1 - Upgrade
Upgrade
GnuTLSto a version that resolves this vulnerability.Fixed in 3.6.13
Event History
Frequently Asked Questions
What is the vulnerability ID for this issue?
The vulnerability ID is CVE-2020-11501.
What is the severity of CVE-2020-11501?
The severity of CVE-2020-11501 is high with a CVSS score of 7.4.
Which versions of GnuTLS are affected by CVE-2020-11501?
GnuTLS versions before 3.6.13 are affected by CVE-2020-11501.
What is the impact of CVE-2020-11501?
CVE-2020-11501 allows an attacker to break the randomness of a DTLS negotiation, potentially compromising the security of the communication.
How can I fix CVE-2020-11501?
To fix CVE-2020-11501, update GnuTLS to version 3.6.13 or later.