Privilege escalation via improper BIOS input validation
Published May 10, 2023 · Updated Feb 13, 2025
Improper input validation in BIOS firmware for affected Intel Processors allows local users with existing high privileges to escalate privileges. Intel has not published the affected BIOS component, the untrusted input, or the validation operation that fails. Exploitation requires existing high privileges and local execution; Intel does not specify the resulting privilege level.
Summary
What happened
Improper input validation in BIOS firmware for affected Intel Processors allows local users with existing high privileges to escalate privileges. Intel has not published the affected BIOS component, the untrusted input, or the validation operation that fails. Exploitation requires existing high privileges and local execution; Intel does not specify the resulting privilege level.
The record
- CVE
- CVE-2022-33894
- Published
- May 10, 2023
- Updated
- Feb 13, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 10, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 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