dbcve.org
BmcOperating system · Nvidia

CVE-2022-42278

HIGH · 7.8 CVSS v3.1 Published 2023-01-13
Fix available
A fix is available. Upgrade to 00.19.07 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
NVIDIA BMC contains a vulnerability in SPX REST API, where an authorized attacker can read and write to arbitrary locations within the memory context of the IPMI server process, which may lead to code execution, denial of service, information disclosure and data tampering.

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

NVIDIA BMC contains a memory corruption vulnerability in the SPX REST API where an authorized attacker can read and write to arbitrary memory locations within the IPMI server process context. This arbitrary memory read/write capability can be exploited to achieve code execution, cause denial of service, disclose sensitive information, or tamper with data.

MitigationApply the NVIDIA firmware patch for this vulnerability when available, and in the interim, restrict network access to the BMC management interface and SPX REST API to minimize exposure.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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. Identify NVIDIA BMC hardware
    Access BMC web interface or run IPMI command: ipmiutil discover or check BMC hardware inventory
    Affected if System is not a NVIDIA BMC product (not applicable)
  2. Check BMC firmware version
    Run ipmiutil cmd -c "raw 0x00 0x08 0x01 0x00" or access BMC web interface under Firmware/Info section. Compare version string against 00.19.07
    Affected if Firmware version is lower than 00.19.07 (e.g., 00.19.00, 00.18.x, etc.)
  3. Verify SPX REST API availability
    Attempt HTTP request to BMC IP on port 443/8443 endpoint /api/spx or check BMC configuration for REST API service status
    Affected if SPX REST API endpoints respond and are accessible on the network
  4. Assess network exposure of BMC management interface
    Check firewall rules, VLAN configuration, and accessibility of BMC IP address from untrusted networks using nmap -p 443,623 <bmc_ip>
    Affected if BMC management ports (443, 8443, 623) are exposed to untrusted network segments or internet

Environment is affected if it runs NVIDIA BMC firmware version below 00.19.07 AND has SPX REST API accessible over the network.

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 when available, and in the interim, restrict network access to the BMC management interface and SPX REST API to minimize exposure.

Recommended fix Moderate confidence

NVIDIA BMC firmware version 00.19.07 or later

  1. 1. Identify the NVIDIA BMC device model and current firmware version
  2. 2. Download the firmware version 00.19.07 or later from NVIDIA's official support portal (nvidia.custhelp.com)
  3. 3. Review the firmware upgrade instructions specific to your BMC model
  4. 4. Back up current BMC configuration if applicable
  5. 5. Apply the firmware update following NVIDIA's documented upgrade procedure
  6. 6. Verify the firmware version has been updated to 00.19.07 or later
  7. 7. Validate that the SPX REST API functionality is operating normally
Caveat Ensure compatibility with your specific BMC hardware model before upgrading; review release notes for any configuration or feature changes

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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