Authenticated kadmind crash via iprop size overflow
Published Jan 16, 2026 · Updated Jan 16, 2026
Integer overflow in MIT Kerberos 5 before 1.22 allows remote authenticated users to crash kadmind through incremental propagation. The resize() function in src/lib/kdb/kdb_log.c calculates a block size from an oversized update without first enforcing the 16-bit maximum, then writes beyond the mapped iprop log region. The flaw is reachable only when incremental propagation is enabled, which is disabled by default, and a Kerberos-authenticated update crashes the administration daemon.
Summary
What happened
Integer overflow in MIT Kerberos 5 before 1.22 allows remote authenticated users to crash kadmind through incremental propagation. The resize() function in src/lib/kdb/kdb_log.c calculates a block size from an oversized update without first enforcing the 16-bit maximum, then writes beyond the mapped iprop log region. The flaw is reachable only when incremental propagation is enabled, which is disabled by default, and a Kerberos-authenticated update crashes the administration daemon.
The record
- CVE
- CVE-2025-24528
- Published
- Jan 16, 2026
- Updated
- Jan 16, 2026
- Vendor
- Massachusetts Institute of Technology
- Product
- Kerberos 5
- Classifications
- CWE-190, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 16, 2026CVE publishedPublication date reported by the CVE source.
- Jan 16, 2026Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.7 <1.22
What conditions does exploitation require?
What is affected?
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