CVE-2022-31639
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 time-of-check to time-of-use (TOCTOU) vulnerabilities have been identified in the BIOS for 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 confidenceTOCTOU (time-of-check to time-of-use) race condition vulnerabilities in HP PC BIOS firmware that could allow an attacker to exploit the gap between security checks and resource usage, potentially achieving arbitrary code execution, privilege escalation, denial of service, or information disclosure.
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<= 1.24<= 1.33<= 1.42<= 1.42<= 1.42<= 1.42<= 1.42<= 1.42CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/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 your HP product modelLocate the product name/number on the system label, in BIOS setup (press Esc/F10 at startup), or via system information tools (dmidecode -s system-product-name on Linux, wmic baseboard get product on Windows, or HP Support Assistant)Affected if The product model matches one of: Zcentral 4r Workstation, Z1 All In One G3, Elitebook 725 G4, Elitebook 745 G4, Elitebook 755 G4, Probook 645 G3, Probook 655 G3, or Mt43 Mobile Thin Client
-
Determine the installed BIOS versionAccess BIOS version information through one of: BIOS setup menu (Esc/F10 at boot), HP Support Assistant > Diagnostics > BIOS Update, or system information utilities (dmidecode -s bios-version on Linux, wmic bios get smbiosbiosversion on Windows)Affected if The installed BIOS version cannot be determined or is lower than the version threshold for your product
-
Compare your BIOS version to affected rangeMatch your product model to its threshold: Zcentral 4r <= 1.24, Z1 All In One G3 <= 1.33, Elitebook 725/745/755 G4 <= 1.42, Probook 645/655 G3 <= 1.42, Mt43 Mobile Thin Client <= 1.42Affected if Your installed BIOS version is at or below the threshold listed for your specific product model
You are affected if you have an HP system from the listed models running BIOS firmware at or 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 · scopedApply HP BIOS firmware updates for affected products. Organizations should identify affected systems using HP's product lookup, deploy updates via HP tools or enterprise management platforms, and verify successful deployment.
HP BIOS firmware update to version > 1.24 (Zcentral 4r), > 1.33 (Z1 All In One G3), or > 1.42 (all other models)
- 1. Identify the exact HP product model from the affected list (Zcentral 4r Workstation, Z1 All In One G3, Elitebook 725/745/755 G4, Probook 645/655 G3, or Mt43 Mobile Thin Client)
- 2. Navigate to HP Support (support.hp.com) and enter the product model number
- 3. Locate the BIOS/firmware section for the product
- 4. Download the latest BIOS firmware version available (version must be higher than the affected version: 1.24 for Zcentral 4r, 1.33 for Z1 All In One G3, 1.42 for all other affected models)
- 5. Follow HP's instructions to update the BIOS - typically requires running the HP BIOS Update utility from Windows or using HP Firmware Update (if available in the OS)
- 6. Restart the system to complete the BIOS update process
- 7. Verify the BIOS version has been updated to a version beyond the affected threshold
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31639 — 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-31639 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