Skip to main content
← Vulnerabilities

Krb5: mit krb5 kdc unauthenticated memory leak dos in kdb keytab key decryption error path

5.3MediumCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported
Published
Last modified
37/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

MIT Kerberos 5 (krb5) key distribution centers and kadmind services are affected by a memory leak that lets a remote attacker cause a denial of service without logging in. The attacker can reach the bug over the network by repeatedly sending requests that trigger key decryption failures, which causes memory to leak until the service fails.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

krb5_ktkdb_get_entry() in lib/kdb/keytab.c in MIT Kerberos 5 (aka krb5) 1.2.8 and later does not free decrypted key material when a post-decryption check fails, which allows remote attackers to cause a denial of service (memory leak in the KDC or kadmind) via requests that repeatedly trigger key decryption failures.

cve.now Index

37Pcve.now Index 37 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach10/20Shipped in major Linux distributions
  • Severity5.3/10CVSS 5.3
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 82 if added to CISA KEV
  • Would score about 77 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • krb5

    Version range not reported

  • krb5

    Version range not reported

  • krb5

    Version range not reported

  • krb5

    Version range not reported

  • krb5

    Version range not reported

  • krb5

    Version range not reported

Evidence 2

  1. Report
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.