Elite Slice FirmwareOperating system · Hp

CVE-2022-37020

MEDIUM · 6.8 CVSS v3.1 Developing Published 2024-06-10
Fix available
A fix is available. Upgrade to 00.02.64 / 01.62 or later.
See remediation →
73/100
Remediation priority · Elevated
No privileges 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 for certain HP PC products, which might allow escalation of privileges and code execution. HP is releasing firmware updates to mitigate the potential vulnerabilities.

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
Elite Slice FirmwareOperating system
Affected:< 00.02.64
Elite Slice For Meeting Rooms FirmwareOperating system
Affected:< 00.02.64
Elitebook 1040 G3 FirmwareOperating system
Affected:< 01.62
Elitebook 820 G3 FirmwareOperating system
Affected:< 01.62
Elitebook 828 G3 FirmwareOperating system
Affected:< 01.62
Elitebook 840 G3 FirmwareOperating system
Affected:< 01.62
Elitebook 848 G3 FirmwareOperating system
Affected:< 01.62
Elitebook 850 G3 FirmwareOperating system
Affected:< 01.62

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

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 00.02.64 / 01.62 or later
Fixed in 00.02.6401.62
Recommended fix High confidence

Elite Slice Firmware: 00.02.64 | Elite Slice For Meeting Rooms Firmware: 00.02.64 | Elitebook 1040/820/828/840/848/850 G3 Firmware: 01.62

  1. Identify the exact HP PC model from the affected product list
  2. Navigate to HP Support (support.hp.com) and enter the product model number
  3. Locate the BIOS/firmware update section
  4. Download the firmware update version 00.02.64 (for Elite Slice models) or version 01.62 (for Elitebook 800 G3 series models)
  5. Follow HP's instructions to update the BIOS, which typically requires: booting into the BIOS setup, running the HP BIOS Update utility, or using HP Support Assistant
  6. Ensure the device is connected to power during the BIOS update process to prevent interruption
  7. Restart the system after the update is complete
Caveat BIOS updates carry risk of system damage if interrupted; ensure stable power and do not interrupt the flashing process

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,850. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-37020 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