dbcve.org
Pc BiosOperating system · Hp

CVE-2022-23933

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 CVE describes multiple potential vulnerabilities in HP PC BIOS that could allow an attacker to escalate privileges, execute arbitrary or unauthorized code, cause denial of service, or disclose sensitive information. The vulnerabilities reside in the system firmware layer, which operates with the highest privilege level on the system.

MitigationApply the appropriate HP BIOS firmware update for affected systems. HP typically releases BIOS updates through their support website or enterprise deployment tools; organizations should identify affected models via HP's security bulletin and deploy updates via their endpoint management infrastructure.

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 on Windows via WMIC
    Open Command Prompt and run: wmic bios get smbiosbiosversion
    Affected if The version shown is lower than 02.07.10 (e.g., 02.05.00, 02.01.05, etc.)
  2. Check BIOS version on Windows via system information
    Open Run dialog, type msinfo32, and look for BIOS Version/Date under System Summary
    Affected if The BIOS Version listed is below 02.07.10
  3. Check BIOS version on Linux via dmidecode
    Run command: sudo dmidecode -s bios-version
    Affected if The output displays a version string lower than 02.07.10
  4. Check BIOS version on Linux via sysfs
    Read the file: cat /sys/class/dmi/id/bios_version
    Affected if The version string returned is less than 02.07.10
  5. Verify BIOS vendor is HP
    Confirm the system is an HP computer: run wmic baseboard get manufacturer or check dmidecode -s system-manufacturer
    Affected if The manufacturer is Hewlett-Packard or HP and the BIOS version is below 02.07.10

A system is affected if it is an HP computer running BIOS firmware version lower 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 for affected systems. HP typically releases BIOS updates through their support website or enterprise deployment tools; organizations should identify affected models via HP's security bulletin and deploy updates via their endpoint management infrastructure.

Recommended fix Moderate confidence

BIOS version 02.07.10

  1. Navigate to support.hp.com and locate the driver download page for your specific HP PC model
  2. Identify the current BIOS version installed on your system (via BIOS setup or HP Support Assistant)
  3. Download the BIOS update package for version 02.07.10 or later for your specific model
  4. Run the BIOS update executable with administrator privileges
  5. Follow the on-screen prompts - the system will typically restart automatically to complete the flashing process
  6. Allow the update to complete fully without interrupting power
  7. Verify the BIOS has been updated to version 02.07.10 or later after the system restarts
Caveat BIOS updates carry inherent risk of system incompatibility; ensure stable power connection and do not interrupt the flashing 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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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