dbcve.org
Zcentral 4r Workstation FirmwareOperating system · Hp

CVE-2022-27539

HIGH · 7.8 CVSS v3.1 Developing 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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-01.

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

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
Recommended fix High confidence

BIOS firmware version 1.25 or later for Zcentral 4r | version 1.34 or later for Z1 All In One G3 | version 1.43 or later for Elitebook 725/745/755 G4, Probook 645/655 G3, and Mt43 Mobile Thin Client

  1. Identify the exact HP product model from the affected products list (Zcentral 4r, Z1 All In One G3, Elitebook 725/745/755 G4, Probook 645/655 G3, or Mt43 Mobile Thin Client)
  2. Navigate to the HP Support website (support.hp.com) and enter the product model number to access the product page
  3. Locate the 'BIOS' or 'Firmware' section under 'Driver & Downloads'
  4. Download the latest BIOS/firmware version available for the specific product
  5. Review the release notes to confirm the update addresses CVE-2022-27539
  6. Follow HP's instructions to update the BIOS - this typically requires: (a) running the HP BIOS Update utility, (b) ensuring AC power is connected, (c) allowing the update process to complete without interruption
  7. Restart the system after the BIOS update completes
  8. Verify the updated BIOS version matches the fixed release version
Caveat BIOS updates carry risk of system damage if interrupted; ensure stable power and do not interrupt the update process; some BIOS updates may reset BIOS settings to defaults

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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