dbcve.org
Pc BiosOperating system · Hp

CVE-2022-23929

HIGH · 8.2 CVSS v3.1 Published 2022-03-11
Fix available
A fix is available. Upgrade to 02.07.10 or later.
See remediation →
84/100
Remediation priority · High
Zero-click

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 · unedited
Potential vulnerabilities have been identified in the system BIOS of certain HP PC products which may allow Escalation of Privilege, Arbitrary Code Execution, Unauthorized Code Execution, 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 confidence

Multiple potential vulnerabilities exist in the system BIOS of certain HP PC products. These BIOS firmware flaws could allow an attacker to escalate privileges, execute arbitrary or unauthorized code, cause denial of service, or disclose sensitive information. The specific vulnerability types, affected versions, and exploitation details are not disclosed in the advisory.

MitigationApply HP BIOS updates for affected systems via HP support website, HP Image Assistant, or enterprise deployment tools (SCCM/HP Manageability Integration Kit) after identifying vulnerable models.

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
Pc BiosOperating system
Affected:< 02.07.10

CVSS 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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check BIOS version via Windows Command Prompt
    Open Command Prompt and run: wmic bios get smbiosbiosversion
    Affected if The version returned is less than 02.07.10
  2. Check BIOS version via Windows System Information
    Open System Information (msinfo32) and look for BIOS Version/Date under System Summary
    Affected if The BIOS Version listed is earlier than 02.07.10
  3. Check BIOS version via Linux terminal
    Run: sudo dmidecode -s bios-version
    Affected if The output shows a version number lower than 02.07.10
  4. Check BIOS version from BIOS setup screen
    Restart the system, enter BIOS/UEFI setup (typically F10 or Esc during POST), and view BIOS information page
    Affected if The BIOS revision shown is below 02.07.10
  5. Check BIOS version via HP tools
    Use HP Support Assistant or run: hp biosconfigutility (if available in your environment)
    Affected if The reported BIOS version is less than 02.07.10

You are affected if your installed HP PC BIOS version is below 02.07.10, regardless of which specific vulnerability within CVE-2022-23929 might apply.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 02.07.10 or later
Fixed in 02.07.10
Interim mitigation

Apply HP BIOS updates for affected systems via HP support website, HP Image Assistant, or enterprise deployment tools (SCCM/HP Manageability Integration Kit) after identifying vulnerable models.

Recommended fix Moderate confidence

BIOS version 02.07.10 or later

  1. Identify your exact HP PC model number (found on the product label or system information)
  2. Navigate to support.hp.com and enter your product model to access the drivers and downloads page
  3. Locate the BIOS section and check the current installed version (via BIOS setup F10 or HP Support Assistant)
  4. Download the BIOS update version 02.07.10 or later from the HP support page
  5. Follow HP's recommended BIOS update process - typically requires running the downloaded executable while connected to AC power
  6. Restart the system and enter BIOS setup (F10) to verify the updated version
Caveat BIOS updates carry a risk if interrupted; ensure stable power connection and do not interrupt the update process

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pc Bios Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23929 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-23929 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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