Memory leak via unreleased sealing buffer
Published Feb 26, 2024 · Updated Aug 14, 2024
Memory leak in the GSSAPI sealing code in MIT Kerberos 5 1.21.2 allows attackers to consume memory during token encoding. gss_krb5int_make_seal_token_v3 allocates plain.data, then takes an error path without freeing it when a ciphertext-size bounds check fails. MIT states that no memory-valid API input is known to reach that check, so no practical service-interruption path has been established.
Summary
What happened
Memory leak in the GSSAPI sealing code in MIT Kerberos 5 1.21.2 allows attackers to consume memory during token encoding. gss_krb5int_make_seal_token_v3 allocates plain.data, then takes an error path without freeing it when a ciphertext-size bounds check fails. MIT states that no memory-valid API input is known to reach that check, so no practical service-interruption path has been established.
The record
- CVE
- CVE-2024-26461
- Published
- Feb 26, 2024
- Updated
- Aug 14, 2024
- Vendor
- Massachusetts Institute of Technology
- Product
- Kerberos 5
- Classifications
- CWE-770
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 26, 2024CVE publishedPublication date reported by the CVE source.
- Aug 14, 2024Record 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.21.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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