CVE-2020-11501High· 7.4▾ TwilightGnuTLS 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 thu…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 40.7 · likelihood 0.7 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Oct 14.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via NVD
Last analysed / modified upstream
3.4%
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.
gnutls >= 3.6.3, < 3.6.13ubuntu_linux = 19.10debian_linux = 10.0leap = 15.1fedora = 31fedora = 32Upgrade past the affected range:
gnutls 3.6.13Connected by shared product, vendor, weakness, or advisory.
CVE-2023-0361High· 7.4A timing side-channel in the handling of RSA ClientKeyExchange messages was discovered in GnuTLS
CVE-2022-2509High· 7.5A vulnerability found in gnutls
CVE-2021-4209Medium· 6.5A NULL pointer dereference flaw was found in GnuTLS
CVE-2021-20231Critical· 9.8A flaw was found in gnutls
CVE-2021-20232Critical· 9.8A flaw was found in gnutls
CVE-2020-24659High· 7.5An issue was discovered in GnuTLS before 3.6.15