dbcve.org
Elite Mini 600 G9 FirmwareOperating system · Hp

CVE-2022-48220

MEDIUM · 6.4 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to 02.12.02 or later.
See remediation →
69/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 certain HP Desktop PC products using the HP TamperLock feature, which might allow intrusion detection bypass via a physical attack. HP is releasing firmware and guidance to mitigate these 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 · moderate confidence

Vulnerabilities in the HP TamperLock feature on certain HP Desktop PC products could allow an attacker to bypass physical intrusion detection mechanisms. An attacker with physical access could tamper with the system (e.g., open the case, access components) without triggering the expected tamper alerts, potentially enabling further malicious modifications to the hardware or firmware.

MitigationApply HP-released firmware updates to affected Desktop PC products and follow HP security guidance to restore proper physical intrusion detection capabilities.

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
Elite Mini 600 G9 FirmwareOperating system
Affected:< 02.12.02
Elite Mini 800 G9 FirmwareOperating system
Affected:< 02.12.02
Elite Sff 600 G9 FirmwareOperating system
Affected:< 02.12.02
Elite Sff 800 G9 FirmwareOperating system
Affected:< 02.12.02
Elite Tower 600 G9 FirmwareOperating system
Affected:< 02.12.02
Elite Tower 680 G9 FirmwareOperating system
Affected:< 02.12.02
Elite Tower 800 G9 FirmwareOperating system
Affected:< 02.12.02
Elite Tower 880 G9 FirmwareOperating system
Affected:< 02.12.02

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

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

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 Desktop model
    Check the system model number on the chassis or via system information ( BIOS setup, HP Support Assistant, or system information tools). Look for model numbers: Elite Mini 600 G9, Elite Mini 800 G9, Elite SFF 600 G9, Elite SFF 800 G9, Elite Tower 600 G9, Elite Tower 680 G9, Elite Tower 800 G9, or Elite Tower 880 G9.
    Affected if The model is one of the eight listed HP Elite Desktop products.
  2. Retrieve the current system firmware version
    Access the HP BIOS/firmware version through BIOS setup (press Esc or F10 at startup), HP Support Assistant, or the HP Firmware Update utility. Note the firmware version displayed.
    Affected if The firmware version cannot be retrieved or is below 02.12.02.
  3. Compare installed firmware against the affected version range
    Compare the retrieved firmware version number to the affected range. Versions below 02.12.02 are vulnerable; version 02.12.02 and above contain the fix.
    Affected if The installed firmware version is less than 02.12.02.
  4. Verify TamperLock configuration status
    Check if the HP TamperLock feature is enabled in BIOS settings (typically under Security or Advanced settings). Access BIOS setup during boot and locate the TamperLock or physical intrusion detection option.
    Affected if TamperLock is enabled and the firmware version is below 02.12.02.

A user is affected if they own one of the eight listed HP Elite Desktop models AND have firmware version installed that is earlier than 02.12.02, regardless of TamperLock configuration status.

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 02.12.02 or later
Fixed in 02.12.02
Interim mitigation

Apply HP-released firmware updates to affected Desktop PC products and follow HP security guidance to restore proper physical intrusion detection capabilities.

Recommended fix Moderate confidence

Firmware version 02.12.02 or later

  1. Identify the current firmware version of the HP Elite system by accessing the BIOS/UEFI setup (typically via F10 during boot) or using HP Support Assistant
  2. Navigate to support.hp.com and enter the specific product model number (e.g., Elite Mini 600 G9) to locate firmware downloads
  3. Download the HP BIOS/firmware update package version 02.12.02 or later for the affected model
  4. Apply the firmware update following HP's instructions - this typically involves running the HP BIOS Update utility from Windows or creating a USB recovery key
  5. Restart the system to complete the firmware update process
  6. Verify the installed firmware version shows 02.12.02 or later after update
Caveat Firmware updates carry a small risk of system instability if interrupted; ensure stable power during update process

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

Fix this in Elite Mini 600 G9 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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