dbcve.org
BmcOperating system · Nvidia

CVE-2022-42275

HIGH · 7.1 CVSS v3.1 Published 2023-01-13
Fix available
A fix is available. Upgrade to 00.19.07 or later.
See remediation →
73/100
Remediation priority · Elevated
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
NVIDIA BMC IPMI handler allows an unauthenticated host to write to a host SPI flash bypassing secureboot protections. This may lead to a loss of integrity and denial of service.

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 · high confidence

NVIDIA BMC IPMI handler contains a vulnerability allowing an unauthenticated host to write to the host SPI flash memory, bypassing secureboot protections. This enables modification of firmware/boot artifacts without authentication, compromising system integrity and potentially causing denial of service.

MitigationApply the NVIDIA firmware patch for this vulnerability and ensure BMC/IPMI interfaces are network-isolated from untrusted networks to prevent unauthenticated access.

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
BmcOperating system
Affected:< 00.19.07

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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. Confirm NVIDIA BMC hardware is present
    Identify the BMC hardware vendor/model on the system. NVIDIA BMC is typically found on NVIDIA enterprise servers or DGX systems. Check system inventory or BMC web interface for 'NVIDIA' or 'Nvidia' as the BMC manufacturer.
    Affected if The system does not have an NVIDIA BMC, this CVE does not apply.
  2. Retrieve the installed BMC firmware version
    Access the BMC web interface or use IPMI command: `ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> raw` or check the firmware version through the BMC web interface under 'Firmware Information' or 'System Information' section.
    Affected if Unable to retrieve version indicates non-NVIDIA BMC or limited access, but version must be confirmed as < 00.19.07.
  3. Compare installed version against vulnerable range
    Verify the BMC firmware version number. The vulnerable range is any version prior to 00.19.07 (for example, 00.19.06, 00.18.x, earlier releases).
    Affected if The installed version is less than 00.19.07 (for example, 00.19.06, 00.18.x).
  4. Verify IPMI interface accessibility
    Check if the IPMI over LAN interface is enabled and accessible from the network. Use command: `ipmitool -I lanplus -H <bmc_ip> channel info` or check BMC network settings. Confirm if IPMI port 623/UDP is exposed.
    Affected if IPMI interface is enabled and reachable from untrusted networks increases exposure risk for unauthenticated exploitation.
  5. Check host SPI flash write access
    Inspect IPMI SEL/SDR or BMC logs for SPI flash write attempts. Look for commands that could write to host SPI flash memory. In the BMC web interface, check if 'Host SPI Flash' or 'BIOS Flash' write access is available to unauthenticated hosts.
    Affected if Unauthenticated host SPI flash write access is enabled, the system is vulnerable to modification of firmware/boot artifacts.

The system is affected if it has an NVIDIA BMC with firmware version below 00.19.07 and the IPMI handler allows unauthenticated host access to SPI flash memory write operations.

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

Apply the NVIDIA firmware patch for this vulnerability and ensure BMC/IPMI interfaces are network-isolated from untrusted networks to prevent unauthenticated access.

Recommended fix Moderate confidence

BMC firmware version 00.19.07 or later

  1. Obtain the BMC firmware version 00.19.07 or later from NVIDIA's official support portal (nvidia.custhelp.com)
  2. Review NVIDIA's BMC firmware update documentation for your specific hardware platform
  3. Download the firmware update package from NVIDIA's secure download area
  4. Verify the integrity of the downloaded firmware package using checksums provided by NVIDIA
  5. Follow NVIDIA's recommended BMC firmware update procedure, which typically involves: a) Uploading the firmware via the BMC web interface or IPMI command, b) Initiating the update through the management interface, c) Allowing the BMC to reboot and complete the update process
  6. After update, verify the BMC firmware version reflects 00.19.07 or later
Caveat BMC firmware updates may require system downtime and should be performed according to NVIDIA's documented procedures; verify compatibility with your specific GPU and system configuration

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

Fix this in Bmc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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