CVE-2022-31637
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 confidenceThis is a time-of-check to time-of-use (TOCTOU) vulnerability in the BIOS firmware of certain HP PC products. TOCTOU flaws occur when there's a race condition between checking a condition (such as authentication or authorization) and acting on that check, allowing an attacker to manipulate the system state during that window. This could allow a local attacker to escalate privileges, execute arbitrary code in SMM or BIOS context, cause denial of service, or disclose sensitive information.
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 modelLook at the product label on the system chassis, check System Information in BIOS (press F10 during boot), or run 'wmic csproduct get name' in Windows command promptAffected if the product model matches one of the affected models listed in the CVE
-
Check the installed BIOS firmware versionAccess BIOS setup by pressing F10 during boot and navigate to 'BIOS Version' or 'System Information', or use HP's BIOS update utility (HPBIOSUPDREC64.exe) with the /s or /d flag to display current version, or run 'wmic bios get smbiosbiosversion' in WindowsAffected if the exact version number is displayed on screen or via command output
-
Compare your version against affected rangesMatch your product model to the corresponding version limit: 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 firmware version number is equal to or lower than the version listed for your product model
You are affected if your HP system model matches one of the listed products AND the installed BIOS/firmware version is at or below the specified version 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 systems when released. Until patches are available, limit physical access to systems, disable unnecessary boot options, and ensure Secure Boot is enabled as a compensating control.
HP BIOS firmware versions greater than 1.24 (Zcentral 4r), 1.33 (Z1 All In One G3), or 1.42 (all other models) - obtain exact fixed version from HP support.hp.com
- Identify the specific HP product model from the affected list (Zcentral 4r, Z1 All In One G3, Elitebook 725/745/755 G4, Probook 645/655 G3, or Mt43 Mobile Thin Client)
- Navigate to HP Support (support.hp.com) and enter the product model number
- Locate the BIOS/firmware updates section for the device
- Download the latest BIOS firmware version available (versions greater than those listed: >1.24 for Zcentral 4r, >1.33 for Z1 All In One G3, >1.42 for all other affected models)
- Review the BIOS update release notes for any prerequisites or special instructions
- Backup current BIOS settings if the option is available in the current firmware
- Connect the device to a reliable power source (do not interrupt the update process)
- Run the BIOS update utility and follow the on-screen prompts to complete the firmware update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31637 — 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-31637 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