Kerberos vulnerabilitiesRanked by how likely they are to be used.

Product102 versions
The short answer

Kerberos is made by Mit. We track 33 published vulnerabilities listed under that exact name, across 102 versions. None of them is on the list of flaws known to be exploited today. Mit lists newer releases under their own names, such as Kerberos 5, so check those pages too.

See the riskiest flaws

We keep watching the known-exploited list.

Other names

Is Kerberos listed under other names? Yes.

Mit also lists Kerberos under more specific names, such as Kerberos 5 and Kerberos FTP Client. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.

Known exploited

Which Kerberos vulnerabilities are being exploited?

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

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

Exploit likelihood

Which Kerberos 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. 39%

    Buffer overflow in BSD-based telnetd telnet daemon on various operating systems allows remote attackers to execute arbitrary commands via a set of options including AYT (Are You There), which is not properly handled...

    CVSS10.0Published14 Aug 2001
  2. 17%

    Buffer overflow in krb_rd_req function in Kerberos 4 and 5 allows remote attackers to gain root privileges.

    CVSS10.0Published16 May 2000
  3. 12%

    Multiple buffer overflows in krb5_aname_to_localname for MIT Kerberos 5 (krb5) 1.3.3 and earlier allow remote attackers to execute arbitrary code as root.

    CVSS10.0Published18 Aug 2004
  4. 7.6%

    Multiple integer underflows in the (1) AES and (2) RC4 decryption functionality in the crypto library in MIT Kerberos 5 (aka krb5) 1.3 through 1.6.3, and 1.7 before 1.7.1, allow remote attackers to cause a denial of...

    CVSS10.0Published13 Jan 2010
  5. 6.5%

    MIT Kerberos 5 (aka krb5) 1.7.x through 1.12.x before 1.12.2 allows remote attackers to cause a denial of service (buffer over-read or NULL pointer dereference, and application crash) by injecting invalid tokens into...

    CVSS5.0Published20 Jul 2014
  6. 5.6%

    The spnego_gss_accept_sec_context function in lib/gssapi/spnego/spnego_mech.c in MIT Kerberos 5 (aka krb5) 1.5 through 1.6.3, when SPNEGO is used, allows remote attackers to cause a denial of service (NULL pointer...

    CVSS5.0Published27 Mar 2009
  7. 4.3%

    The get_input_token function in the SPNEGO implementation in MIT Kerberos 5 (aka krb5) 1.5 through 1.6.3 allows remote attackers to cause a denial of service (daemon crash) and possibly obtain sensitive information...

    CVSS5.8Published9 Apr 2009
  8. 4.3%

    Version 4 of the Kerberos protocol (krb4), as used in Heimdal and other packages, allows an attacker to impersonate any principal in a realm via a chosen-plaintext attack.

    CVSS7.5Published24 Mar 2003
  9. 4.3%

    Certain weaknesses in the implementation of version 4 of the Kerberos protocol (krb4) in the krb5 distribution, when triple-DES keys are used to key krb4 services, allow an attacker to create krb4 tickets for...

    CVSS7.5Published24 Mar 2003
  10. 4.2%

    The unparse implementation in the Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) 1.6.x through 1.9, when an LDAP backend is used, allows remote attackers to cause a denial of service (file descriptor...

    CVSS5.0Published10 Feb 2011
Precursor Intelligence

Running Kerberos? 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 33 published vulnerabilities listed under the name Kerberos, across 102 versions.

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

Mit also lists Kerberos under more specific names, such as Kerberos 5 and Kerberos FTP Client. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

Create a Precursor Intelligence account and track Kerberos. 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.