Local privilege escalation via improper BIOS input validation
Published May 12, 2022 · Updated May 5, 2025
Improper input validation in Intel processor BIOS firmware allows local users with existing privileges to escalate privileges through local access. Intel identifies the locus only as BIOS firmware and has not published which input is mishandled or which validation operation is missing. Exploitation requires privileged local access and crosses a security boundary, potentially granting control beyond the user's existing authorization.
Summary
What happened
Improper input validation in Intel processor BIOS firmware allows local users with existing privileges to escalate privileges through local access. Intel identifies the locus only as BIOS firmware and has not published which input is mishandled or which validation operation is missing. Exploitation requires privileged local access and crosses a security boundary, potentially granting control beyond the user's existing authorization.
The record
- CVE
- CVE-2021-0154
- Published
- May 12, 2022
- Updated
- May 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 12, 2022CVE publishedPublication date reported by the CVE source.
- May 5, 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