DXE code execution via NVRAM function pointer
Published Aug 18, 2022 · Updated Feb 5, 2025
Improper input validation in Intel NUC Laptop Kit firmware before BC0076 allows physically proximate attackers to execute DXE code. The AMITSE DXE driver reads EsaVarPtr01 from NVRAM as a GetPackageListHandle function pointer and invokes the attacker-supplied address. Exploitation requires high privileges and physical SPI-flash modification; executed code can persist across the operating-system boot and runtime.
Summary
What happened
Improper input validation in Intel NUC Laptop Kit firmware before BC0076 allows physically proximate attackers to execute DXE code. The AMITSE DXE driver reads EsaVarPtr01 from NVRAM as a GetPackageListHandle function pointer and invokes the attacker-supplied address. Exploitation requires high privileges and physical SPI-flash modification; executed code can persist across the operating-system boot and runtime.
The record
- CVE
- CVE-2022-34345
- Published
- Aug 18, 2022
- Updated
- Feb 5, 2025
- Vendor
- Intel Corporation
- Product
- Intel NUC Laptop Kits
- Classifications
- CWE-20, T1542.001
- Attack vector
- physical
- Privileges
- admin
Timeline
How it unfolded
- Aug 18, 2022CVE publishedPublication date reported by the CVE source.
- Feb 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=before version BC0076
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- BRLY-2022-015 technical exploit demonstrationproof of concept · demonstrated
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