dbcve.org
Elite Dragonfly FirmwareOperating system · Hp

CVE-2022-31642

HIGH · 7.0 CVSS v3.1 Developing Published 2023-06-14
Fix available
A fix is available. Upgrade to 01.01.03 / 01.03.01 or later.
See remediation →
72/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Potential vulnerabilities have been identified in the system BIOS of certain HP PC products, which might allow arbitrary code execution, escalation of privilege, denial of service, and information disclosure.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-01.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Elite Dragonfly FirmwareOperating system
Affected:< 01.21.01
Elite Dragonfly G3 FirmwareOperating system
Affected:< 01.03.01< 01.01.03
Elite X2 1012 G2 FirmwareOperating system
Affected:< 1.43
Elite X2 1013 G3 FirmwareOperating system
Affected:< 01.21.01
Elite X2 G4 FirmwareOperating system
Affected:< 01.21.01
Elite X360 1040 G9 FirmwareOperating system
Affected:< 01.03.01
Elite X360 830 G9 FirmwareOperating system
Affected:< 01.03.01
Elitebook 1040 G9 FirmwareOperating system
Affected:< 01.03.01

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 01.01.03 / 01.03.01 / 01.21.01 or later
Fixed in 01.01.0301.03.0101.21.01
Recommended fix High confidence

BIOS firmware version 01.21.01 (Elite Dragonfly, Elite X2 1013 G3, Elite X2 G4), 01.03.01 (Elite Dragonfly G3, Elite X360 1040 G9, Elite X360 830 G9, Elitebook 1040 G9), 1.43 (Elite X2 1012 G2), or respective latest available BIOS revision

  1. 1. Identify the exact model of the HP device from the affected product list
  2. 2. Navigate to HP Support (support.hp.com) and enter the device model number
  3. 3. Locate the BIOS/firmware section for the specific product
  4. 4. Download the BIOS update version matching or exceeding: Elite Dragonfly: 01.21.01, Elite Dragonfly G3: 01.03.01, Elite X2 1012 G2: 1.43, Elite X2 1013 G3: 01.21.01, Elite X2 G4: 01.21.01, Elite X360 1040 G9: 01.03.01, Elite X360 830 G9: 01.03.01, Elitebook 1040 G9: 01.03.01
  5. 5. Connect the device to AC power (do not rely on battery alone)
  6. 6. Run the BIOS update utility and follow the on-screen prompts
  7. 7. Allow the update to complete fully; do not interrupt power or shut down the device
  8. 8. Verify the BIOS version has been updated post-reboot
Caveat BIOS updates carry a risk of bricking the device if interrupted; ensure stable power and do not interrupt the flashing process

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31642 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-31642 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data