CVE-2022-23934
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 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 confidenceMultiple potential vulnerabilities in HP PC system BIOS that could allow privilege escalation, arbitrary/unauthorized code execution, denial of service, or information disclosure. The specific technical details of the vulnerability (affected models, attack vector, root cause) are not disclosed in the available description.
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< 02.07.10CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check BIOS version on WindowsOpen Command Prompt and run: wmic bios get smbiosbiosversion or systeminfo | findstr /C:"BIOS Version"Affected if The reported version is lower than 02.07.10
-
Check BIOS version via PowerShellRun PowerShell as administrator and execute: Get-CimInstance -ClassName Win32_BIOS | Select-Object -Property SMBIOSBIOSVersionAffected if The SMBIOSBIOSVersion shown is less than 02.07.10
-
Check BIOS version on LinuxRun command: sudo dmidecode -s bios-versionAffected if The output version is earlier than 02.07.10
-
Check BIOS version via HP toolsOpen HP Support Assistant or HP PC Hardware Diagnostics Windows, and locate the BIOS/firmware version information displayed in the system detailsAffected if The BIOS firmware version shown is below 02.07.10
-
Verify BIOS version from DMI dataOn Linux, read the version from: cat /sys/class/dmi/id/bios_version or sudo cat /sys/class/dmi/id/bios_verAffected if The version string is older than 02.07.10
If the installed HP PC BIOS version is less than 02.07.10, the system is affected by this vulnerability.
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 · scoped02.07.10
Apply BIOS/firmware updates from HP for affected PC products. BIOS vulnerabilities typically require updating system firmware from the vendor.
BIOS version 02.07.10 or later
- Identify your exact HP PC model number (found on the product label or system information)
- Navigate to HP Support at support.hp.com
- Enter your model number in the search bar
- Select your device from the results
- Go to the 'Drivers & Downloads' section
- Locate the BIOS category and look for a version >= 02.07.10
- Download the HP BIOS Update utility for your specific model
- Run the downloaded executable and follow the on-screen instructions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23934 — 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-23934 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