dbcve.org
Zcentral 4r Workstation FirmwareOperating system · Hp

CVE-2022-43777

HIGH · 7.8 CVSS v3.1 Published 2023-06-12
Fix available
A fix is available. Upgrade to after 1.42 or later.
See remediation →
80/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 Time-of-Check to Time-of Use (TOCTOU) vulnerabilities have been identified in the HP BIOS for certain HP PC products which may allow arbitrary 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

TOCTOU vulnerability in HP BIOS allowing race condition between security check and resource use. Could allow privileged attacker to bypass BIOS security controls for arbitrary code execution, denial of service, or information disclosure.

MitigationApply HP BIOS firmware updates from HP support for affected products. BIOS updates typically require controlled deployment with testing, potential downtime, and verification.

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
Zcentral 4r Workstation FirmwareOperating system
Affected:<= 1.24
Z1 All In One G3 Workstation FirmwareOperating system
Affected:<= 1.33
Elitebook 725 G4 FirmwareOperating system
Affected:<= 1.42
Elitebook 745 G4 FirmwareOperating system
Affected:<= 1.42
Elitebook 755 G4 FirmwareOperating system
Affected:<= 1.42
Probook 645 G3 FirmwareOperating system
Affected:<= 1.42
Probook 655 G3 FirmwareOperating system
Affected:<= 1.42
Mt43 Mobile Thin Client FirmwareOperating system
Affected:<= 1.42

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
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/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. Identify your HP device model
    Run 'systeminfo' on Windows or 'dmidecode -s system-product-name' on Linux to obtain the exact product name and model number.
    Affected if The device model matches one of: Zcentral 4r Workstation, Z1 All In One G3 Workstation, Elitebook 725 G4, Elitebook 745 G4, Elitebook 755 G4, Probook 645 G3, Probook 655 G3, or Mt43 Mobile Thin Client.
  2. Retrieve the BIOS firmware version
    Run 'wmic bios get smbiosbiosversion' on Windows or 'dmidecode -s bios-version' on Linux to obtain the installed BIOS version.
    Affected if The command returns a version number that can be compared against the affected ranges.
  3. Compare your BIOS version against affected ranges
    Match your extracted BIOS version number to the affected versions: Zcentral 4r <= 1.24, Z1 All In One G3 <= 1.33, or the remaining models <= 1.42. Versions are numeric comparisons.
    Affected if Your BIOS version is equal to or lower than the version limit for your specific model.
  4. Check BIOS date as secondary verification
    Run 'wmic bios get releasedate' on Windows or 'dmidecode -s bios-release-date' on Linux to see when the BIOS was released.
    Affected if The BIOS release date is prior to the patch release date for your model, indicating an unpatched version.

You are affected if your HP device model matches one of the eight listed products AND your installed BIOS firmware version is at or below the specified version limit for that model.

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 a release after 1.42
Interim mitigation

Apply HP BIOS firmware updates from HP support for affected products. BIOS updates typically require controlled deployment with testing, potential downtime, and verification.

Recommended fix Moderate confidence

Latest available BIOS firmware from HP support for each specific model (versions greater than 1.24 for Zcentral 4r, greater than 1.33 for Z1 All In One G3, greater than 1.42 for remaining models)

  1. Identify the specific HP product model from the affected list (Zcentral 4r Workstation, Z1 All In One G3, Elitebook 725/745/755 G4, Probook 645/655 G3, or Mt43 Mobile Thin Client)
  2. Navigate to support.hp.com and enter the product model number to access the product support page
  3. Locate the 'Driver' or 'BIOS' section for firmware updates
  4. Download the latest available BIOS firmware version for the specific product
  5. Review the BIOS update release notes to confirm the update addresses security vulnerabilities
  6. Follow HP's provided instructions to update the BIOS firmware, which typically requires: rebooting the system, running the HP BIOS Update utility, and allowing the update process to complete without interruption
  7. After updating, verify the BIOS version has changed to confirm successful installation
Caveat BIOS updates may reset certain configurations to defaults; backup custom BIOS settings before updating if applicable

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

Fix this in Zcentral 4r Workstation Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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