dbcve.org
Probook 440 G8 FirmwareOperating system · Hp

CVE-2022-23953

MEDIUM · 5.5 CVSS v3.1 Published 2022-03-02
Fix available
A fix is available. Upgrade to 01.08.11 / 02.07.10 or later.
See remediation →
57/100
Remediation priority · Elevated
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 BIOS for some HP PC products which may allow denial of service.

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

A vulnerability in the BIOS firmware of certain HP PC products that could allow an authenticated local attacker to cause a denial of service by disrupting BIOS functionality.

MitigationApply the BIOS firmware update provided by HP for affected product models. This typically requires downloading the update from HP's support site and running the BIOS flash utility, often with the system in a powered-on AC state.

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
Probook 440 G8 FirmwareOperating system
Affected:< 01.08.11
Prodesk 405 G6 Small Form Factor FirmwareOperating 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Identify the exact HP product model
    Check the product label on the device casing or run 'wmic computersystem get model' in Command Prompt to confirm the exact model number
    Affected if Model is not Hp Probook 440 G8 or Hp Prodesk 405 G6 Small Form Factor - other models are not affected by this specific CVE
  2. Retrieve the installed BIOS version on Windows
    Open Command Prompt and run 'wmic bios get smbiosbiosversion' or check System Information (msinfo32) under BIOS Version/Date
    Affected if Unable to retrieve BIOS version - firmware may not be accessible for checking
  3. Compare BIOS version against affected threshold for Probook 440 G8
    If model is Hp Probook 440 G8, compare the installed version to 01.08.11 - versions below 01.08.11 are affected
    Affected if Installed version is less than 01.08.11 (e.g., 01.08.10, 01.07.05, etc.)
  4. Compare BIOS version against affected threshold for Prodesk 405 G6 SFF
    If model is Hp Prodesk 405 G6 Small Form Factor, compare the installed version to 02.07.10 - versions below 02.07.10 are affected
    Affected if Installed version is less than 02.07.10 (e.g., 02.07.01, 02.05.12, etc.)

User is affected if they own an Hp Probook 440 G8 with BIOS version below 01.08.11, or an Hp Prodesk 405 G6 Small Form Factor with BIOS version below 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 01.08.11 / 02.07.10 or later
Fixed in 01.08.1102.07.10
Interim mitigation

Apply the BIOS firmware update provided by HP for affected product models. This typically requires downloading the update from HP's support site and running the BIOS flash utility, often with the system in a powered-on AC state.

Recommended fix High confidence

BIOS version 01.08.11 or later for HP Probook 440 G8; BIOS version 02.07.10 or later for HP Prodesk 405 G6 Small Form Factor

  1. Identify your current BIOS version by pressing F10 during startup to enter BIOS setup, or check via HP Support Assistant
  2. Navigate to support.hp.com and enter your exact product model number (Probook 440 G8 or Prodesk 405 G6 SFF)
  3. Locate the BIOS updates section and download the firmware version 01.08.11 (for Probook 440 G8) or version 02.07.10 (for Prodesk 405 G6 SFF) or later
  4. Run the downloaded HP BIOS Update utility and follow the on-screen instructions
  5. Ensure the laptop is plugged into AC power and do not interrupt the update process until complete
  6. After the update completes, the system will restart and the new BIOS version will be active
Caveat BIOS updates carry inherent risk if interrupted; ensure stable power and follow HP's update instructions precisely

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

Fix this in Probook 440 G8 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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