# CVE-2019-18913: Security feature bypass in HP Intel-based Business PCs that support Microsoft Windows 10 Kernel DMA protection.

> Attackers with physical access can bypass Kernel DMA protection to execute unauthorized UEFI code on HP Intel-based Business PCs.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jan 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-55w2-94jr-cc63

## What is CVE-2019-18913?

CVE-2019-18913 is a medium-severity vulnerability in HP Intel-based Business PCs that support Microsoft Windows 10 Kernel DMA protection., published on 31 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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).

## Which versions are affected by CVE-2019-18913?

It affects 33 products.


Products: Hp Elite Dragonfly Firmware, Hp Elite X2 G4 Firmware, Hp Elitebook 830 G6 Firmware, Hp Elitebook 836 G6 Firmware, Hp Elitebook 840 G6 Firmware, Hp Elitebook 840 G6 Healthcare Edition Firmware, Hp Elitebook 846 G6 Firmware, Hp Elitebook 846 G6 Healthcare Edition Firmware, Hp Elitebook 850 G6 Firmware, Hp Elitebook X360 1030 G4 Firmware, Hp Elitebook X360 1040 G6 Firmware, Hp Elitebook X360 830 G6 Firmware, Hp Elitedesk 800 G5 Dm Firmware, Hp Elitedesk 800 G5 Sff Firmware, Hp Elitedesk 800 G5 Twr Firmware, Hp Eliteone 800 G5 Aio Firmware, Hp Probook 640 G5 Firmware, Hp Probook 650 G5 Firmware, Hp Prodesk 400 G5 Dm Firmware, Hp Prodesk 400 G6 Mt Firmware and 13 more.

## How do I fix CVE-2019-18913?

No fix has been published for CVE-2019-18913 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-18913 being exploited?

There is no known exploitation of CVE-2019-18913 in the wild and no public exploit code.

## Other vulnerabilities in HP Intel-based Business PCs that support Microsoft Windows 10 Kernel DMA protection.

- [CVE-2021-3808](https://insights.sbomify.com/CVE-2021-3808/): Privilege escalation in HP PC BIOS (high 7.8)
- [CVE-2021-3809](https://insights.sbomify.com/CVE-2021-3809/): Privilege escalation in HP PC BIOS (high 7.8)
- [CVE-2022-31640](https://insights.sbomify.com/CVE-2022-31640/): Race condition in HP PC BIOS (high 7.0)
- [CVE-2022-31641](https://insights.sbomify.com/CVE-2022-31641/): Race condition in HP PC BIOS (high 7.0)
- [CVE-2022-31642](https://insights.sbomify.com/CVE-2022-31642/): Race condition in HP PC BIOS (high 7.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-18913 and fix it if it is affected.

What it is: CVE-2019-18913 is a medium-severity vulnerability in HP Intel-based Business PCs that support Microsoft Windows 10 Kernel DMA protection., published on 31 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-18913 in the wild and no public exploit code.

Affected product: HP Intel-based Business PCs that support Microsoft Windows 10 Kernel DMA protection.. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-18913/ (Markdown: https://insights.sbomify.com/CVE-2019-18913/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-18913
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-18913
- OSV: https://osv.dev/vulnerability/CVE-2019-18913

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-18913/
Summaries are generated and may contain mistakes; the official description above is the record.