Local privilege escalation via UEFI error handler
Published Sep 16, 2024 · Updated Nov 3, 2025
Improper input validation in Intel processor UEFI firmware allows local users to escalate privileges through its error handler. Intel identifies the locus as the UEFI firmware error handler but has not disclosed which input it validates incorrectly or how that operation crosses the security boundary. Exploitation requires local access, high privileges, high attack complexity, and additional attack requirements; successful exploitation grants privileges beyond the attacker's initial security context.
Summary
What happened
Improper input validation in Intel processor UEFI firmware allows local users to escalate privileges through its error handler. Intel identifies the locus as the UEFI firmware error handler but has not disclosed which input it validates incorrectly or how that operation crosses the security boundary. Exploitation requires local access, high privileges, high attack complexity, and additional attack requirements; successful exploitation grants privileges beyond the attacker's initial security context.
The record
- CVE
- CVE-2024-21829
- Published
- Sep 16, 2024
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 16, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 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.
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