CVE-2022-31635
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 race condition vulnerabilities in HP PC BIOS firmware that allow attackers to potentially execute arbitrary code, escalate privileges, cause denial of service, or obtain sensitive information by exploiting the time gap between security checks and resource usage operations.
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 modelCheck system information via 'systeminfo' on Windows or 'dmidecode -s system-product-name' on Linux, or look for the product label on the device itselfAffected if The model does not match any of the affected products listed (Zcentral 4r, Z1 All In One G3, Elitebook 725/745/755 G4, Probook 645/655 G3, Mt43 Mobile Thin Client)
-
Retrieve the installed BIOS firmware versionOn Windows, run 'wmic bios get version' or use HP Support Assistant. On Linux, run 'dmidecode -s bios-version' or check /sys/class/dmi/id/bios_versionAffected if Unable to retrieve a BIOS version number from the system
-
Compare the firmware version to affected rangesMatch your retrieved BIOS version against the affected version thresholds: Zcentral 4r <= 1.24, Z1 G3 <= 1.33, all other models <= 1.42Affected if Your installed firmware version is equal to or lower than the affected version for your specific model
-
Verify firmware update status through HP toolsUse HP Support Assistant, HP BIOS Configuration Tool (BCU), or enterprise management tools (SCCM/Intune) to check if a newer BIOS version has been appliedAffected if HP tools show the BIOS is still at or below the affected version and no update has been applied
You are affected if your HP device model matches one of the eight listed products AND your current BIOS firmware version is at or below the specified 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; verify patch status through HP support or enterprise management tools. TOCTOU bugs require careful code review and atomic operation implementation in firmware.
- Navigate to the official HP Support website (support.hp.com)
- Enter the specific product model (e.g., Elitebook 745 G4) in the search or product lookup
- Locate the BIOS/firmware section for your product
- Download the latest BIOS update package available
- Review the update release notes to confirm it addresses CVE-2022-31635
- Connect the system to AC power (do not update on battery)
- Execute the BIOS update utility following HP's provided instructions
- Allow the update process to complete without interruption - do not power off the system
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31635 — 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-31635 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