Gnutls Gnutls

Do you want an email whenever new security vulnerabilities are reported in Gnutls?

By the Year

In 2022 there have been 1 vulnerability in Gnutls with an average score of 7.5 out of ten. Last year Gnutls had 2 security vulnerabilities published. Right now, Gnutls is on track to have less security vulnerabilities in 2022 than it did last year. Last year, the average CVE base score was greater by 2.30

Year Vulnerabilities Average Score
2022 1 7.50
2021 2 9.80
2020 3 7.43
2019 2 7.50
2018 4 5.75

It may take a day or so for new Gnutls vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Gnutls Security Vulnerabilities

A vulnerability found in gnutls

CVE-2022-2509 7.5 - High - August 01, 2022

A vulnerability found in gnutls. This security flaw happens because of a double free error occurs during verification of pkcs7 signatures in gnutls_pkcs7_verify function.

Double-free

A flaw was found in gnutls

CVE-2021-20231 9.8 - Critical - March 12, 2021

A flaw was found in gnutls. A use after free issue in client sending key_share extension may lead to memory corruption and other consequences.

Dangling pointer

A flaw was found in gnutls

CVE-2021-20232 9.8 - Critical - March 12, 2021

A flaw was found in gnutls. A use after free issue in client_send_params in lib/ext/pre_shared_key.c may lead to memory corruption and other potential consequences.

Dangling pointer

An issue was discovered in GnuTLS before 3.6.15

CVE-2020-24659 7.5 - High - September 04, 2020

An issue was discovered in GnuTLS before 3.6.15. A server can trigger a NULL pointer dereference in a TLS 1.3 client if a no_renegotiation alert is sent with unexpected timing, and then an invalid second handshake occurs. The crash happens in the application's error handling path, where the gnutls_deinit function is called after detecting a handshake failure.

Memory Corruption

GnuTLS 3.6.x before 3.6.14 uses incorrect cryptography for encrypting a session ticket (a loss of confidentiality in TLS 1.2

CVE-2020-13777 7.4 - High - June 04, 2020

GnuTLS 3.6.x before 3.6.14 uses incorrect cryptography for encrypting a session ticket (a loss of confidentiality in TLS 1.2, and an authentication bypass in TLS 1.3). The earliest affected version is 3.6.4 (2018-09-24) because of an error in a 2018-09-18 commit. Until the first key rotation, the TLS server always uses wrong data in place of an encryption key derived from an application.

Use of a Broken or Risky Cryptographic Algorithm

GnuTLS 3.6.x before 3.6.13 uses incorrect cryptography for DTLS

CVE-2020-11501 7.4 - High - April 03, 2020

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.

Use of a Broken or Risky Cryptographic Algorithm

It was discovered in gnutls before version 3.6.7 upstream

CVE-2019-3836 7.5 - High - April 01, 2019

It was discovered in gnutls before version 3.6.7 upstream that there is an uninitialized pointer access in gnutls versions 3.6.3 or later which can be triggered by certain post-handshake messages.

Access of Uninitialized Pointer

A vulnerability was found in gnutls versions from 3.5.8 before 3.6.7

CVE-2019-3829 7.5 - High - March 27, 2019

A vulnerability was found in gnutls versions from 3.5.8 before 3.6.7. A memory corruption (double free) vulnerability in the certificate verification API. Any client or server application that verifies X.509 certificates with GnuTLS 3.5.8 or later is affected.

Double-free

A Bleichenbacher type side-channel based padding oracle attack was found in the way gnutls handles verification of RSA decrypted PKCS#1 v1.5 data

CVE-2018-16868 5.6 - Medium - December 03, 2018

A Bleichenbacher type side-channel based padding oracle attack was found in the way gnutls handles verification of RSA decrypted PKCS#1 v1.5 data. An attacker who is able to run process on the same physical core as the victim process, could use this to extract plaintext or in some cases downgrade any TLS connections to a vulnerable server.

Cryptographic Issues

It was found that the GnuTLS implementation of HMAC-SHA-256 was vulnerable to a Lucky thirteen style attack

CVE-2018-10844 5.9 - Medium - August 22, 2018

It was found that the GnuTLS implementation of HMAC-SHA-256 was vulnerable to a Lucky thirteen style attack. Remote attackers could use this flaw to conduct distinguishing attacks and plaintext-recovery attacks via statistical analysis of timing data using crafted packets.

Use of a Broken or Risky Cryptographic Algorithm

It was found that the GnuTLS implementation of HMAC-SHA-384 was vulnerable to a Lucky thirteen style attack

CVE-2018-10845 5.9 - Medium - August 22, 2018

It was found that the GnuTLS implementation of HMAC-SHA-384 was vulnerable to a Lucky thirteen style attack. Remote attackers could use this flaw to conduct distinguishing attacks and plain text recovery attacks via statistical analysis of timing data using crafted packets.

Use of a Broken or Risky Cryptographic Algorithm

A cache-based side channel in GnuTLS implementation that leads to plain text recovery in cross-VM attack setting was found

CVE-2018-10846 5.6 - Medium - August 22, 2018

A cache-based side channel in GnuTLS implementation that leads to plain text recovery in cross-VM attack setting was found. An attacker could use a combination of "Just in Time" Prime+probe attack in combination with Lucky-13 attack to recover plain text using crafted packets.

Use of a Broken or Risky Cryptographic Algorithm

The "GNUTLS_KEYLOGFILE" environment variable in gnutls 3.4.12

CVE-2016-4456 7.5 - High - August 08, 2017

The "GNUTLS_KEYLOGFILE" environment variable in gnutls 3.4.12 allows remote attackers to overwrite and corrupt arbitrary files in the filesystem.

Improper Input Validation

The TLS protocol, and the SSL protocol 3.0 and possibly earlier, as used in Microsoft Internet Information Services (IIS) 7.0, mod_ssl in the Apache HTTP Server 2.2.14 and earlier, OpenSSL before 0.9.8l, GnuTLS 2.8.5 and earlier, Mozilla Network Security Services (NSS) 3.12.4 and earlier, multiple Cisco products, and other products, does not properly associate renegotiation handshakes with an existing connection, which allows man-in-the-middle attackers to insert data into HTTPS sessions, and possibly other types of sessions protected by TLS or SSL, by sending an unauthenticated request

CVE-2009-3555 - November 09, 2009

The TLS protocol, and the SSL protocol 3.0 and possibly earlier, as used in Microsoft Internet Information Services (IIS) 7.0, mod_ssl in the Apache HTTP Server 2.2.14 and earlier, OpenSSL before 0.9.8l, GnuTLS 2.8.5 and earlier, Mozilla Network Security Services (NSS) 3.12.4 and earlier, multiple Cisco products, and other products, does not properly associate renegotiation handshakes with an existing connection, which allows man-in-the-middle attackers to insert data into HTTPS sessions, and possibly other types of sessions protected by TLS or SSL, by sending an unauthenticated request that is processed retroactively by a server in a post-renegotiation context, related to a "plaintext injection" attack, aka the "Project Mogul" issue.

Improper Certificate Validation

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for F5 Networks Nginx or by GNU? Click the Watch button to subscribe.

GNU
Vendor

Gnutls
Product

subscribe