dbcve.org
Pc BiosOperating system · Hp

CVE-2022-23925

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

This is a firmware-level vulnerability in the system BIOS of certain HP PC products. BIOS vulnerabilities execute at the most privileged level of the system, before the operating system loads, making them extremely serious as they can provide persistent, stealthy access that survives OS reinstalls. The multiple potential impacts (privilege escalation, arbitrary/unauthorized code execution, DoS, information disclosure) indicate multiple attack vectors within the BIOS firmware.

MitigationApply the appropriate HP BIOS/firmware update from HP's support website for the affected system model; in enterprise environments, use centralized firmware management tools and test patches thoroughly before deployment due to the risk of rendering systems unbootable.

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 in Windows
    Open System Information (msinfo32) or HP Support Assistant, and look for the BIOS Version/Date entry under BIOS section. Alternatively, run 'wmic bios get smbiosbiosversion' in Command Prompt.
    Affected if The BIOS version shown is less than 02.07.10 (for example, 02.05.00, 02.06.01, etc.)
  2. Check BIOS version from Linux
    Boot into Linux and run 'sudo dmidecode -s bios-version' in terminal. The output will show the installed BIOS version string.
    Affected if The version returned is numerically lower than 02.07.10
  3. Check BIOS version from boot menu
    Restart the PC and press F10 (or Esc then F10 on some models) to enter BIOS Setup. Navigate to the Main or Information section to view the BIOS Version.
    Affected if The displayed BIOS version is earlier than 02.07.10
  4. Confirm HP PC model
    Verify the system is an HP consumer or business PC (not a server) by checking the system model via 'wmic computersystem get model' in Windows or 'dmidecode -s system-product-name' in Linux.
    Affected if The system is an HP PC model and the BIOS version is below 02.07.10

A system is affected if it is an HP PC with a BIOS version installed that is numerically less than 02.07.10.

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 the appropriate HP BIOS/firmware update from HP's support website for the affected system model; in enterprise environments, use centralized firmware management tools and test patches thoroughly before deployment due to the risk of rendering systems unbootable.

Recommended fix Moderate confidence

02.07.10 or later

  1. Identify your specific HP PC model number (found on the device or via system information)
  2. Navigate to HP Customer Support - Software and Driver Downloads (support.hp.com)
  3. Enter your product model number to find available BIOS updates
  4. Locate BIOS version 02.07.10 or later in the results
  5. Download the BIOS update file (typically an .exe or .rpm depending on OS)
  6. Run the BIOS update executable as Administrator
  7. Follow the on-screen prompts - do not interrupt the update process
  8. Allow the system to restart and complete the BIOS flashing procedure
Caveat BIOS updates carry inherent risk of system damage if interrupted; ensure stable power and do not interrupt the flashing process; some BIOS updates may reset configuration settings to defaults

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23925 — 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-23925 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