dbcve.org
Pc BiosOperating system · Hp

CVE-2022-23930

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 critical vulnerabilities exist in the system BIOS firmware of certain HP PC products that could allow an attacker to escalate privileges, execute arbitrary code, cause denial of service, or disclose sensitive information. The 8.2 CVSS score indicates significant risk requiring urgent attention.

MitigationApply HP BIOS/firmware updates from HP's official support website for all affected HP PC models. BIOS updates must be downloaded and installed specifically for each affected system's model number.

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 installed BIOS version via System Information
    Open Windows Run dialog (Win+R), type 'msinfo32', and look for 'BIOS Version' under 'System Summary'. Alternatively, open Command Prompt and run: wmic bios get name,version
    Affected if The BIOS version displayed is lower than 02.07.10 (for example, 02.05.00, 02.06.01, etc.)
  2. Check installed BIOS version via HP Support Assistant
    Open HP Support Assistant, go to the 'Diagnostics' or 'System Information' section, and locate the BIOS/firmware version listed for your device
    Affected if The reported BIOS version is below 02.07.10
  3. Check BIOS version from boot menu
    Restart the computer and press F10 (or the designated key shown on screen) to enter BIOS Setup. The BIOS version is typically displayed on the main or 'About' screen of the BIOS utility
    Affected if The BIOS version shown is less than 02.07.10
  4. Verify HP PC model and cross-reference
    Note your exact HP PC model number (found on the product label, in System Information under 'System Model', or on the BIOS main screen). Then check HP's official support website to confirm the latest BIOS version for that specific model matches 02.07.10 or higher
    Affected if HP's published BIOS update for your model is version 02.07.10 or higher, but your current installed version is older

You are affected if your HP PC is running BIOS firmware version lower than 02.07.10, regardless of which specific vulnerability in CVE-2022-23930 is present.

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/firmware updates from HP's official support website for all affected HP PC models. BIOS updates must be downloaded and installed specifically for each affected system's model number.

Recommended fix Moderate confidence

HP BIOS version 02.07.10 or later for affected HP PC models

  1. Identify the specific HP PC model number by checking the product label or system information (Win+R, type 'msinfo32')
  2. Navigate to HP Support at support.hp.com and enter the model number to find drivers and downloads
  3. Locate the BIOS update for the system and verify the version is 02.07.10 or higher
  4. Download the HP BIOS update utility and save it to a reliable location
  5. Connect the system to AC power (do not run on battery) and ensure a stable power connection
  6. Close all open applications and disable antivirus software temporarily if prompted
  7. Run the BIOS update executable and follow the on-screen instructions exactly
  8. Do not interrupt the update process or restart the system until complete
Caveat BIOS updates carry a 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
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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