dbcve.org
348 G4 FirmwareOperating system · Hp

CVE-2022-43779

HIGH · 7.0 CVSS v3.1 Published 2023-02-12
Fix available
A fix is available. Upgrade to 00.02.40 / 02.02.40 or later.
See remediation →
72/100
Remediation priority · Elevated
Zero-click Patch available

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
A potential Time-of-Check to Time-of-Use (TOCTOU) vulnerability has been identified in certain HP PC products using AMI UEFI Firmware (system BIOS) which might allow arbitrary code execution, denial of service, and information disclosure. AMI has released updates to mitigate the potential vulnerability.

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

A detailed technical summary for this CVE is being prepared.

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
348 G4 FirmwareOperating system
Affected:< f.65
260 G2 Desktop Mini FirmwareOperating system
Affected:< 2.26
218 Pro G5 Mt FirmwareOperating system
Affected:< f15
260 G3 Desktop Mini FirmwareOperating system
Affected:< 02.20.00
260 G4 Desktop Mini FirmwareOperating system
Affected:< 02.12.00
280 G3 Microtower Pc FirmwareOperating system
Affected:< 02.02.40
280 G3 Pci Microtower Pc FirmwareOperating system
Affected:< 02.02.40
288 Pro G3 Microtower Pc FirmwareOperating system
Affected:< 00.02.40

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/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 00.02.40 / 02.02.40 / 02.12.00 or later
Fixed in 00.02.4002.02.4002.12.00
Vendor patch support.hp.com →
Recommended fix High confidence

AMI UEFI Firmware updates to version f.65 (348 G4), 2.26 (260 G2), f15 (218 Pro G5 Mt), 02.20.00 (260 G3), 02.12.00 (260 G4), 02.02.40 (280 G3), or 00.02.40 (288 Pro G3) depending on model

  1. 1. Identify the exact HP model number and current firmware version of the affected system
  2. 2. Navigate to the HP Support page: https://support.hp.com/us-en/document/ish_7394557-7394585-16/hpsbhf03829
  3. 3. Select the specific product model from the list of affected systems
  4. 4. Download the corresponding BIOS/firmware update: 348 G4: f.65 | 260 G2 Desktop Mini: 2.26 | 218 Pro G5 Mt: f15 | 260 G3 Desktop Mini: 02.20.00 | 260 G4 Desktop Mini: 02.12.00 | 280 G3 Microtower Pc: 02.02.40 | 280 G3 Pci Microtower Pc: 02.02.40 | 288 Pro G3 Microtower Pc: 00.02.40
  5. 5. Follow HP's instructions to update the UEFI BIOS firmware, typically via HP Support Assistant or by running the downloaded executable while the system is plugged into AC power
Caveat UEFI firmware updates carry a risk if interrupted; ensure stable power and do not interrupt the update 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 $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-43779 — 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-43779 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