Vulnerability · CVE-2020-11501
GnuTLS 3.6.x before 3.6.13 uses incorrect cryptography for DTLS.
Published Apr 3, 2020 · catalog updated Oct 14, 2026 · GnuTLS 3.6.x before 3.6.13
Check if you run it
No confirmed exploitation is on record for CVE-2020-11501. EPSS is 3.39%. Act only if a listed version of GnuTLS 3.6.x before 3.6.13 is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (GnuTLS 3.6.x before 3.6.13).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High7.4
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 3.39%
- Remediation
- Advisory link
- Affected products
- cpe canonical/ubuntu linux · cpe debian/debian linux · cpe fedoraproject/fedora · cpe gnu/gnutls · cpe opensuse/leap
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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe canonical/ubuntu linux19.10
- cpe debian/debian linux10.0
- cpe fedoraproject/fedora31
- cpe fedoraproject/fedora32
- cpe gnu/gnutlsversion unspecified
- cpe opensuse/leap15.1
How to fix CVE-2020-11501
Recommended remediation
A patch or advisory reference is linked. Open the original publisher for availability by product version.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2020-11501. EPSS is 3.39%. Act only if a listed version of GnuTLS 3.6.x before 3.6.13 is installed.
Which versions are affected?
Compare what you have installed with canonical/ubuntu linux 19.10; debian/debian linux 10.0. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-330: Insufficiently Random Values. EPSS 3.39%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Apr 3, 2020 · NIST NVD
Detected
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.
Oct 14, 2026 · NIST NVD
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.
Sources
- CVE.orgVulnerability recordCVE-2020-11501
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2020-11501
30-day exploitation probability 3.4%
first.org - NIST NVDVulnerability recordCVE-2020-11501
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 negot
nvd.nist.gov
References
Freshness
Last verified in this catalog Oct 16, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.