Local privilege escalation via BIOS control-flow failure
Published May 12, 2022 · Updated May 5, 2025
Insufficient control-flow management in Intel processor BIOS firmware allows local users with high privileges to escalate privileges. Intel has not published the affected BIOS routine or how its control flow is manipulated. Exploitation requires local access with high privileges and can modify protected state or interrupt system operation.
Summary
What happened
Insufficient control-flow management in Intel processor BIOS firmware allows local users with high privileges to escalate privileges. Intel has not published the affected BIOS routine or how its control flow is manipulated. Exploitation requires local access with high privileges and can modify protected state or interrupt system operation.
The record
- CVE
- CVE-2021-33122
- Published
- May 12, 2022
- Updated
- May 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- 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.
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