Gnutls vulnerabilitiesRanked by how likely they are to be used.

Product367 versions
The short answer

Gnutls is made by Gnu. We track 69 published vulnerabilities in it, across 367 versions. None of them is on the list of flaws known to be exploited today. If you run Gnutls, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Gnutls vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Gnutls's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Gnutls flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 59%

    A vulnerability was found in gnutls versions from 3.5.8 before 3.6.7.

    CVSS7.5Published27 Mar 2019
  2. 33%

    Double free vulnerability in the gnutls_x509_ext_import_proxy function in GnuTLS before 3.3.26 and 3.5.x before 3.5.8 allows remote attackers to have unspecified impact via crafted policy language information in an...

    CVSS9.8Published24 Mar 2017
  3. 30%

    lib/x509/verify.c in GnuTLS before 3.1.22 and 3.2.x before 3.2.12 does not properly handle unspecified errors when verifying X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof...

    CVSS5.8Published7 Mar 2014
  4. 22%

    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).

    CVSS7.4Published4 Jun 2020
  5. 19%

    Double free vulnerability in GnuTLS before 3.3.17 and 3.4.x before 3.4.4 allows remote attackers to cause a denial of service via a long DistinguishedName (DN) entry in a certificate.

    CVSS5.0Published24 Aug 2015
  6. 12%

    The _gnutls_server_name_recv_params function in lib/ext_server_name.c in libgnutls in gnutls-serv in GnuTLS before 2.2.4 does not properly calculate the number of Server Names in a TLS 1.0 Client Hello message during...

    CVSS10.0Published21 May 2008
  7. 11%

    Buffer overflow in the read_server_hello function in lib/gnutls_handshake.c in GnuTLS before 3.1.25, 3.2.x before 3.2.15, and 3.3.x before 3.3.4 allows remote servers to cause a denial of service (memory corruption)...

    CVSS6.8Published3 Jun 2014
  8. 8.0%

    The stream reading functions in lib/opencdk/read-packet.c in GnuTLS before 3.3.26 and 3.5.x before 3.5.8 allow remote attackers to cause a denial of service (out-of-memory error and crash) via a crafted OpenPGP...

    CVSS7.5Published24 Mar 2017
  9. 7.9%

    lib/pk-libgcrypt.c in libgnutls in GnuTLS before 2.6.6 does not properly handle invalid DSA signatures, which allows remote attackers to cause a denial of service (application crash) and possibly have unspecified...

    CVSS4.3Published30 Apr 2009
Precursor Intelligence

Running Gnutls? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 69 published vulnerabilities listed under the name Gnutls, across 367 versions.

None of Gnutls's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Gnutls. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.