CVE-2022-31641
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 · uneditedPotential 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 · moderate confidenceHP BIOS vulnerability allowing arbitrary code execution, privilege escalation, DoS, and information disclosure. This is a firmware-level issue affecting certain HP PC systems, likely exploitable through local or physical access vectors.
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< 01.21.01< 01.03.01< 01.01.03< 1.43< 01.21.01< 01.21.01< 01.03.01< 01.03.01< 01.03.01CVSS 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
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the HP system modelRun 'dmidecode -s system-product-name' or check the system label/packaging to confirm the exact HP modelAffected if The model matches any of the following: Elite Dragonfly, Elite Dragonfly G3, Elite X2 1012 G2, Elite X2 1013 G3, Elite X2 G4, Elite X360 1040 G9, Elite X360 830 G9, Elitebook 1040 G9
-
Retrieve the current BIOS/firmware versionRun 'dmidecode -s bios-version' or enter the BIOS setup (F10) and check the BIOS version listed on the main pageAffected if The installed version cannot be determined or is lower than the affected versions listed for your model
-
Compare the installed version against affected rangesFor your identified model, check if the installed firmware version is below: Elite Dragonfly < 01.21.01; Elite Dragonfly G3 < 01.03.01 or < 01.01.03; 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.01Affected if The installed version is lower than the specified threshold for your exact model and variant
-
Verify if BIOS updates have been appliedCheck HP Support Assistant, HP Business Support Center, or system management software for BIOS update history and current patch levelAffected if No BIOS firmware updates have been installed since the vulnerability disclosure date (2022) and the version remains in the affected range
You are affected if your HP system model matches one of the listed products and your current BIOS/firmware version is below the specified version threshold for that model.
Generated from the published advisory. Verify against your own configuration.
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 · scoped01.01.0301.03.0101.21.01
Apply HP BIOS/firmware updates from HP's support website for affected systems. Verify update compatibility in test environment before enterprise deployment due to firmware update risks.
BIOS firmware version 01.21.01 (Elite Dragonfly, Elite X2 1013 G3, Elite X2 G4) or 01.03.01 (Elite Dragonfly G3, Elite X360 1040 G9, Elite X360 830 G9, Elitebook 1040 G9) or 1.43 (Elite X2 1012 G2)
- Identify the exact HP Elite model from the affected product list
- Navigate to HP Support (support.hp.com) and enter the product model number
- Locate the BIOS/Firmware section and download the latest BIOS update
- Review the update release notes to confirm the version addresses CVE-2022-31641
- Connect the system to AC power and ensure the battery is sufficiently charged
- Execute the BIOS update utility from Windows or use HP's firmware update tool
- Allow the update to complete without interrupting power - do not turn off the system
- Restart the system after the update completes and verify the new BIOS version in BIOS setup
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31641 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-31641 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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