dbcve.org
Elite Dragonfly G3 FirmwareOperating system · Hp

CVE-2022-31643

MEDIUM · 5.5 CVSS v3.1 Published 2023-04-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/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
A potential security vulnerability has been identified in the system BIOS for certain HP PC products which may allow loss of integrity. HP is releasing firmware updates to mitigate the potential vulnerability.

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 · moderate confidence

A vulnerability in HP PC system BIOS allows an attacker with local or physical access to modify firmware, potentially leading to loss of integrity. The specific attack vector and technical details are not disclosed, but the CVSS score of 5.5 indicates moderate severity with low attack complexity.

MitigationApply the HP firmware update for affected systems as specified in HP's security bulletin. BIOS updates should be deployed organization-wide following HP's recommended update procedures.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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 G3 FirmwareOperating system
Affected:= 01.03.01
Dragonfly Folio G3 FirmwareOperating system
Affected:= 01.03.01
Elite Dragonfly G2 FirmwareOperating system
Affected:= 01.10.00
Elite Dragonfly Max FirmwareOperating system
Affected:= 01.10.00
Elite X2 G8 FirmwareOperating system
Affected:= 01.10.00
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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the HP system model
    Run 'wmic computersystem get model' from Windows command prompt, or 'dmidecode -s system-product-name' from Linux terminal
    Affected if The model is one of: Elite Dragonfly G3, Dragonfly Folio G3, Elite Dragonfly G2, Elite Dragonfly Max, Elite X2 G8, Elite X360 1040 G9, Elite X360 830 G9, or Elitebook 1040 G9
  2. Check the installed BIOS firmware version
    Run 'wmic bios get smbiosbiosversion' from Windows command prompt, or 'dmidecode -s bios-version' from Linux terminal
    Affected if The BIOS version matches exactly: 01.03.01 (for Dragonfly G3, Dragonfly Folio G3, Elite X360 1040 G9, Elite X360 830 G9, Elitebook 1040 G9) OR 01.10.00 (for Dragonfly G2, Elite Dragonfly Max, Elite X2 G8)
  3. Verify BIOS version from HP hardware diagnostics
    Access HP PC Hardware Diagnostics UEFI via F2 during boot, or use HP Support Assistant to view system BIOS version details
    Affected if The BIOS version shown matches one of the affected versions listed above

The system is affected if it is one of the eight listed HP models AND its BIOS firmware version exactly matches 01.03.01 or 01.10.00 depending on model.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the HP firmware update for affected systems as specified in HP's security bulletin. BIOS updates should be deployed organization-wide following HP's recommended update procedures.

Recommended fix Moderate confidence

Latest BIOS firmware version available from HP support for your specific model (newer than 01.03.01 or 01.10.00)

  1. Navigate to HP Support (support.hp.com) and use the 'Software & Drivers' search to find your specific HP PC model
  2. Download the latest BIOS firmware update available for your device model
  3. Restart the computer and enter BIOS/UEFI setup (typically by pressing F10 or Esc during boot)
  4. Verify current BIOS version matches the affected version (01.03.01 or 01.10.00 depending on model)
  5. Return to Windows and run the downloaded BIOS update executable with the computer connected to AC power
  6. Allow the update to complete without interruption - do not power off or restart manually
  7. The system will automatically restart and complete the BIOS flash process
  8. After reboot, enter BIOS setup and verify the new BIOS version is installed
Caveat BIOS updates carry risk of system incompatibility; ensure AC power is connected during flash and do not interrupt the update process

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

Fix this in Elite Dragonfly G3 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31643 — 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-31643 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