Physical privilege escalation via improper firmware initialization
Published Feb 9, 2022 · Updated May 5, 2025
Improper initialization in Intel processor BIOS firmware allows physically proximate attackers with high privileges to escalate privileges. Intel identifies the faulty locus only as processor firmware and does not disclose which state is left uninitialized or how that state is consumed. Exploitation requires physical access and high privileges; Intel reports privilege escalation but does not specify the resulting authority or actions.
Summary
What happened
Improper initialization in Intel processor BIOS firmware allows physically proximate attackers with high privileges to escalate privileges. Intel identifies the faulty locus only as processor firmware and does not disclose which state is left uninitialized or how that state is consumed. Exploitation requires physical access and high privileges; Intel reports privilege escalation but does not specify the resulting authority or actions.
The record
- CVE
- CVE-2021-0119
- Published
- Feb 9, 2022
- Updated
- May 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-665, T1068
- Attack vector
- physical
- Privileges
- admin
Timeline
How it unfolded
- Feb 9, 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.
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