What is CVE-2019-18913?A medium-severity flaw in Elitedesk 800 G5 Dm Firmware, explained.
CVE-2019-18913 is a medium-severity flaw (CVSS 6.8) in Elitedesk 800 G5 Dm Firmware from HP, published on 31 January 2020. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.6%. If you run an affected version, plan in the vendor’s fix.
Published 31 January 2020. Record last updated 24 August 2020. We keep this page's data up to date.
What is CVE-2019-18913? In plain terms.
An attacker has to be physically at the device without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
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).
What kind of flaw is it?
- UnknownUnknown
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can bePhysically at the device
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read data, change data and take it offline
Severity vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is CVE-2019-18913 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.6%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2019-18913 scores 28. Action: Monitor.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2019-18913 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2019-18913? 66 products.
The published record lists 66 products from 1 vendor. Versions are shown as published: "before 02.04.02" means every version up to, but not including, 02.04.02. If you run one of these, check your version, then go to the fix below.
- Operating system
Elitedesk 800 G5 Dm Firmware
by HP
Affected versionsbefore 02.04.02 - Hardware
Elite Dragonfly
by HP
Affected versionsversion not specified - Operating system
Elite Dragonfly Firmware
by HP
Affected versionsbefore 01.04.02 - Hardware
Elite X2 G4
by HP
Affected versionsversion not specified - Operating system
Elite X2 G4 Firmware
by HP
Affected versionsbefore 01.04.02 - Hardware
Elitebook 830 G6
by HP
Affected versionsversion not specified - Operating system
Elitebook 830 G6 Firmware
by HP
Affected versionsbefore 01.04.02 - Hardware
Elitebook 836 G6
by HP
Affected versionsversion not specified - Operating system
Elitebook 836 G6 Firmware
by HP
Affected versionsbefore 01.04.02
How do I fix CVE-2019-18913? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
References
1 linkDoes CVE-2019-18913 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
A potential security vulnerability with pre-boot DMA may allow unauthorized UEFI code execution using open-case attacks. This industry-wide issue requires ph...
- Matched to
- Elitedesk 800 G5 Dm Firmware on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2019-18913 is a medium-severity flaw in Elitedesk 800 G5 Dm Firmware from HP, published on 31 January 2020. An attacker has to be physically at the device without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
It scores 6.8 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2019-18913 is 28 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.6%. That can change at any time, which is why we keep watching.
For Elitedesk 800 G5 Dm Firmware from HP: before 02.04.02. The record lists 66 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.