Firmware code execution via reused GetVariable length
Published Aug 11, 2023 · Updated Oct 9, 2024
Stack-based buffer overflow in Intel NUC BIOS firmware allows local users with high privileges to execute code in a UEFI DXE driver. HandleTpm12VersionInfoAndPCRBitmap reuses a length variable after Tpm12VersionInfo can replace it with an attacker-controlled value, causing a later PCRBitmap GetVariable call to overflow a 20-byte stack buffer. Successful exploitation crosses from the operating system into firmware execution and permits persistent code or NVRAM modification across system boots.
Summary
What happened
Stack-based buffer overflow in Intel NUC BIOS firmware allows local users with high privileges to execute code in a UEFI DXE driver. HandleTpm12VersionInfoAndPCRBitmap reuses a length variable after Tpm12VersionInfo can replace it with an attacker-controlled value, causing a later PCRBitmap GetVariable call to overflow a 20-byte stack buffer. Successful exploitation crosses from the operating system into firmware execution and permits persistent code or NVRAM modification across system boots.
The record
- CVE
- CVE-2023-22449
- Published
- Aug 11, 2023
- Updated
- Oct 9, 2024
- Vendor
- Topcon Positioning Systems, Inc.
- Product
- Intel NUC BIOS Firmware
- Classifications
- CWE-20, T1542.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 11, 2023CVE publishedPublication date reported by the CVE source.
- Oct 9, 2024Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=See references
What conditions does exploitation require?
What is affected?
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