UEFI code execution via internal PCIe DMA
Published Jan 31, 2020 · Updated Aug 5, 2024
Pre-boot DMA protection gaps in HP business PC firmware allow physically proximate attackers to execute unauthorized UEFI code. Unprotected internal PCI Express slots permit specialized DMA hardware to modify UEFI code in memory before the operating system starts. Exploitation requires physical access inside an open chassis plus specialized hardware and software, enabling firmware-level code execution and information disclosure.
Summary
What happened
Pre-boot DMA protection gaps in HP business PC firmware allow physically proximate attackers to execute unauthorized UEFI code. Unprotected internal PCI Express slots permit specialized DMA hardware to modify UEFI code in memory before the operating system starts. Exploitation requires physical access inside an open chassis plus specialized hardware and software, enabling firmware-level code execution and information disclosure.
The record
- CVE
- CVE-2019-18913
- Published
- Jan 31, 2020
- Updated
- Aug 5, 2024
- Vendor
- HP Inc.
- Product
- HP Intel-based Business PCs supporting Microsoft Windows 10 Kernel DMA Protection
- Classifications
- T1542.001
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 31, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=Depends on platform. Prior to 01.04.02
- Affected versionversion=or prior to 02.04.01
- Affected versionversion=or prior to 02.04.02.
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.
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