KDC resource exhaustion via invalid UTF-8 principal
Published Feb 26, 2024 · Updated Mar 25, 2025
Memory leak in MIT Kerberos 5 1.21.2 allows local users to exhaust KDC memory by supplying a principal containing invalid UTF-8. enc_wchar_pointer initializes a dynamic k5buf before UTF-8 conversion, then returns on conversion failure without releasing the allocation. Request-based reachability remains unconfirmed, and upstream states that elevated privilege can be required to reach the encoding path.
Summary
What happened
Memory leak in MIT Kerberos 5 1.21.2 allows local users to exhaust KDC memory by supplying a principal containing invalid UTF-8. enc_wchar_pointer initializes a dynamic k5buf before UTF-8 conversion, then returns on conversion failure without releasing the allocation. Request-based reachability remains unconfirmed, and upstream states that elevated privilege can be required to reach the encoding path.
The record
- CVE
- CVE-2024-26462
- Published
- Feb 26, 2024
- Updated
- Mar 25, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2024CVE publishedPublication date reported by the CVE source.
- Mar 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo