CVE-2019-18913: A potential security vulnerability with pre-boot DMA may allow unauthorized UEFI code execution using open-case attacks.
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.60% (FIRST EPSS).
- Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A potential security vulnerability with pre-boot DMA may allow unauthorized UEFI code execution using open-case attacks. This industry-wide issue requires physically accessing internal expansion slots with specialized hardware and software tools to modify UEFI code in memory. This affects HP Intel-based Business PCs that support Microsoft Windows 10 Kernel DMA protection. Affected versions depend on platform (prior to 01.04.02; or prior to 02.04.01; or prior to 02.04.02).
- Published
- Jan 31, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.6% · 48th percentile
- CWE
- —
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| hp | elitedesk 800 g5 dm firmware | cpe:2.3:o:hp:elitedesk_800_g5_dm_firmware |
| hp | elitedesk 800 g5 dm | cpe:2.3:h:hp:elitedesk_800_g5_dm |
| hp | elitedesk 800 g5 sff firmware | cpe:2.3:o:hp:elitedesk_800_g5_sff_firmware |
| hp | elitedesk 800 g5 sff | cpe:2.3:h:hp:elitedesk_800_g5_sff |
| hp | elitedesk 800 g5 twr firmware | cpe:2.3:o:hp:elitedesk_800_g5_twr_firmware |
| hp | elitedesk 800 g5 twr | cpe:2.3:h:hp:elitedesk_800_g5_twr |
| hp | eliteone 800 g5 aio firmware | cpe:2.3:o:hp:eliteone_800_g5_aio_firmware |
| hp | eliteone 800 g5 aio | cpe:2.3:h:hp:eliteone_800_g5_aio |
| hp | prodesk 400 g5 dm firmware | cpe:2.3:o:hp:prodesk_400_g5_dm_firmware |
| hp | prodesk 400 g5 dm | cpe:2.3:h:hp:prodesk_400_g5_dm |
| hp | prodesk 400 g6 mt firmware | cpe:2.3:o:hp:prodesk_400_g6_mt_firmware |
| hp | prodesk 400 g6 mt | cpe:2.3:h:hp:prodesk_400_g6_mt |
and 54 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hp elite dragonfly firmwarebefore 01.04.02
- hp elite x2 g4 firmwarebefore 01.04.02
- hp elitebook 830 g6 firmwarebefore 01.04.02
- hp elitebook 836 g6 firmwarebefore 01.04.02
- hp elitebook 840 g6 firmwarebefore 01.04.02
- hp elitebook 840 g6 healthcare edition firmwarebefore 01.04.02
- hp elitebook 846 g6 firmwarebefore 01.04.02
- hp elitebook 846 g6 healthcare edition firmwarebefore 01.04.02
- hp elitebook 850 g6 firmwarebefore 01.04.02
- hp elitebook x360 1030 g4 firmwarebefore 01.04.02
- hp elitebook x360 1040 g6 firmwarebefore 01.04.02
- hp elitebook x360 830 g6 firmwarebefore 01.04.02
- hp elitedesk 800 g5 dm firmwarebefore 02.04.02
- hp elitedesk 800 g5 sff firmwarebefore 02.04.02
- hp elitedesk 800 g5 twr firmwarebefore 02.04.02
- hp eliteone 800 g5 aio firmwarebefore 02.04.02
- hp probook 640 g5 firmwarebefore 01.04.02
- hp probook 650 g5 firmwarebefore 01.04.02
- hp prodesk 400 g5 dm firmwarebefore 02.04.01
- hp prodesk 400 g6 mt firmwarebefore 02.04.01
Versions reported by the vendor
Affected version ranges reported by the assigning authority (hp). Independent of NVD's CPE analysis and usually ahead of it.
HP Inc. HP Intel-based Business PCs that support Microsoft Windows 10 Kernel DMA protection.
- Depends on platform. Prior to 01.04.02, or prior to 02.04.01, or prior to 02.04.02.affected
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.