Privilege escalation via unchecked firmware return value
Published Feb 9, 2022 · Updated May 5, 2025
Unchecked return handling in Intel Processor firmware allows privileged local users to escalate privileges through local access. Intel identifies only an unchecked return value in processor firmware and has not published the affected routine or failed operation. Exploitation requires existing high privileges and local code execution; successful exploitation crosses a security boundary and compromises confidentiality and integrity.
Summary
What happened
Unchecked return handling in Intel Processor firmware allows privileged local users to escalate privileges through local access. Intel identifies only an unchecked return value in processor firmware and has not published the affected routine or failed operation. Exploitation requires existing high privileges and local code execution; successful exploitation crosses a security boundary and compromises confidentiality and integrity.
The record
- CVE
- CVE-2021-0107
- Published
- Feb 9, 2022
- Updated
- May 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-252, T1068
- Attack vector
- local
- 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.
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.
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