dbcve.org
Dgx A100 FirmwareOperating system · Nvidia

CVE-2022-42289

HIGH · 8.8 CVSS v3.1 Published 2023-01-13
Fix available
A fix is available. Upgrade to 00.19.07 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 inject arbitrary shell commands, 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 firmware contains a command injection vulnerability in the SPX REST API where an authenticated attacker can inject arbitrary shell commands through API requests, leading to remote code execution with BMC privileges. This affects the baseboard management controller's web interface used for server hardware management.

MitigationApply NVIDIA's firmware update when available; in the interim, restrict network access to the BMC management interface to authorized administrators only and implement network segmentation.

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

CVSS:3.1/AV:N/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. Check DGX A100 BMC firmware version
    Access the BMC web interface or use IPMI command 'ipmitool -I lanplus -H <bmc-ip> -U <user> -P <pass> raw command' to retrieve firmware version information
    Affected if Firmware version is below 00.19.07
  2. Identify SPX REST API endpoint availability
    Attempt to reach the SPX REST API endpoint at the BMC (typically https://<bmc-ip>/api or /api/spx) using a web browser or curl command
    Affected if SPX REST API is exposed and responds to requests
  3. Verify BMC authentication is configured
    Check if BMC user accounts exist and authentication is enabled for the web interface and API endpoints
    Affected if BMC web interface permits authentication with valid credentials
  4. Confirm network accessibility of BMC management interface
    Verify the BMC IP address is reachable on the network and check if port 443 (HTTPS) or 80 (HTTP) is open
    Affected if BMC management interface is accessible from untrusted networks

A DGX A100 system is affected by CVE-2022-42289 when its BMC firmware version is below 00.19.07 and the SPX REST API is accessible with valid authentication credentials.

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 NVIDIA's firmware update when available; in the interim, restrict network access to the BMC management interface to authorized administrators only and implement network segmentation.

Recommended fix Moderate confidence

DGX A100 Firmware version 00.19.07 or later

  1. 1. Back up current BMC configuration to ensure settings can be restored if needed
  2. 2. Download the NVIDIA DGX A100 firmware version 00.19.07 or later from the NVIDIA enterprise support portal
  3. 3. Access the DGX A100 BMC web interface or use the BMC CLI
  4. 4. Navigate to the firmware update section (typically under 'Maintenance' or 'Firmware Update')
  5. 5. Upload and apply the new firmware image
  6. 6. Wait for the firmware update to complete - do not power off the system during this process
  7. 7. After reboot, verify the BMC firmware version shows 00.19.07 or later
  8. 8. Validate that SPX REST API functionality is operating normally
Caveat Firmware updates carry inherent risk; ensure proper backup and planned maintenance window as update may require system downtime

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

Fix this in Dgx A100 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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