Local privilege escalation via authenticated-module buffer overwrite
Published May 12, 2022 · Updated May 5, 2025
Out-of-bounds write in Intel processor BIOS authenticated code modules allows privileged local users to escalate privileges. The module writes outside an intended memory buffer, but Intel has not disclosed the input or code path that triggers the write. Exploitation requires privileged local access and can cross a security boundary to affect confidentiality, integrity, and availability.
Summary
What happened
Out-of-bounds write in Intel processor BIOS authenticated code modules allows privileged local users to escalate privileges. The module writes outside an intended memory buffer, but Intel has not disclosed the input or code path that triggers the write. Exploitation requires privileged local access and can cross a security boundary to affect confidentiality, integrity, and availability.
The record
- CVE
- CVE-2021-33124
- Published
- May 12, 2022
- Updated
- May 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, 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.
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