CVE-2022-31644
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 confidenceMultiple vulnerabilities in HP PC system BIOS could allow an attacker to execute arbitrary code, escalate privileges, cause denial of service, or disclose sensitive information. The specific vulnerability types and attack vectors are not detailed in the available description, but the CVSS score of 7.8 indicates high severity with low attack complexity likely requiring local or adjacent network access.
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.01.03= 01.21.01= 01.03.01= 01.10.00= 01.10.00= not_impacted= 1.57= 1.43CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/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 exact HP device modelCheck the device model via system information (Windows: msinfo32, Linux: cat /sys/class/dmi/id/product_name), HP Support Assistant, or the label on the device casingAffected if The model is one of: Hp Dragonfly Folio G3 2 In 1, Hp Elite Dragonfly, Hp Elite Dragonfly G3, Hp Elite Dragonfly G2, Hp Elite Dragonfly Max, Hp Elite X2 1012 G1, or Hp Elite X2 1012 G2
-
Check the installed BIOS firmware versionRun 'wmic bios get smbiosbiosversion' on Windows or 'sudo dmidecode -s bios-version' on Linux, or view via HP Support Assistant, or press F10 during boot to enter BIOS setup and check the BIOS version thereAffected if The installed version matches one of the affected versions: 01.01.03 (Dragonfly Folio G3), 01.21.01 (Elite Dragonfly), 01.03.01 (Elite Dragonfly G3), 01.10.00 (Elite Dragonfly G2 or Max), 1.57 (Elite X2 1012 G1), or 1.43 (Elite X2 1012 G2)
-
Verify the system is using the vulnerable BIOS versionCompare the firmware version obtained from step 2 against the exact version numbers listed in the affected products tableAffected if Your installed BIOS version exactly matches any of the affected versions listed (the equal sign in the advisory indicates these specific versions are vulnerable, not version ranges)
You are affected if you own one of the listed HP models and your current BIOS firmware version exactly matches the vulnerable version shown 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.
From vendor dataApply the latest HP BIOS/firmware updates from HP's support website for affected models. Organizations should identify all vulnerable HP PC models in their environment and deploy the corresponding BIOS updates through their standard patch management or deployment tools.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31644 — 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-31644 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