Daemon crash via overwritten error return
Published Jul 22, 2021 · Updated Aug 4, 2024
NULL pointer dereference in the MIT Kerberos 5 KDC before 1.18.4 and 1.19.x before 1.19.2 allows remote attackers to crash the daemon. In ec_verify(), k5memdup0() overwrites an earlier error return when no FAST armor key exists, allowing krb5_c_fx_cf2_simple() to dereference that NULL key. An unauthenticated PA-ENCRYPTED-CHALLENGE request sent without FAST is sufficient, interrupting KDC authentication service until the daemon restarts.
Summary
What happened
NULL pointer dereference in the MIT Kerberos 5 KDC before 1.18.4 and 1.19.x before 1.19.2 allows remote attackers to crash the daemon. In ec_verify(), k5memdup0() overwrites an earlier error return when no FAST armor key exists, allowing krb5_c_fx_cf2_simple() to dereference that NULL key. An unauthenticated PA-ENCRYPTED-CHALLENGE request sent without FAST is sufficient, interrupting KDC authentication service until the daemon restarts.
The record
- CVE
- CVE-2021-36222
- Published
- Jul 22, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 22, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
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
- Upstream encrypted-challenge regression triggerproof of concept · demonstrated
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