dbcve.org
Dgx A100 FirmwareOperating system · Nvidia

CVE-2022-42290

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. An authenticated attacker can inject arbitrary shell commands through the API, potentially achieving code execution, causing denial of service, or facilitating information disclosure and data tampering.

MitigationApply the NVIDIA firmware patch when available; restrict API access to minimum necessary personnel and network segments; disable unused REST API endpoints; monitor for unusual command execution patterns.

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. Identify if the system is a DGX A100
    Check the system hardware inventory or BMC web interface for the model name. On the BMC, navigate to 'System > Inventory' or run 'ipmitool mc info' to retrieve the system model.
    Affected if The system is an Nvidia DGX A100 server
  2. Check the BMC firmware version
    Access the BMC web interface and navigate to 'Settings > Firmware Update' or use the command 'ipmitool mc info' or 'ipmitool fru print' via IPMI to retrieve the current firmware version string.
    Affected if The installed firmware version is earlier than 00.19.07 (e.g., 00.18.x, 00.17.x)
  3. Verify if the SPX REST API is accessible
    Attempt to reach the REST API endpoint on the BMC (typically https://<bmc-ip>/api/spx or /redfish/v1/Managers/Self). Use a browser or curl with valid authentication credentials.
    Affected if The SPX REST API endpoint responds and accepts authenticated requests
  4. Check API authentication configuration
    Review BMC user accounts and API access controls in the web interface under 'Settings > Users' or via IPMI command 'ipmitool user list'. Confirm whether weak or default credentials exist.
    Affected if API access is granted to untrusted users or uses default credentials
  5. Review API access logs for suspicious activity
    Check BMC audit logs under 'Maintenance > Logs' or in /var/log on the BMC via SSH for unusual API calls, especially those containing shell metacharacters (;, |, $, `, etc.).
    Affected if Logs show API requests with anomalous command patterns

A user is affected if they operate a DGX A100 with BMC firmware below version 00.19.07 and have the SPX REST API accessible to authenticated users.

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 when available; restrict API access to minimum necessary personnel and network segments; disable unused REST API endpoints; monitor for unusual command execution patterns.

Recommended fix Moderate confidence

DGX A100 Firmware 00.19.07

  1. Identify current DGX A100 BMC firmware version via NVIDIA BMC web interface or IPMI command
  2. Navigate to NVIDIA's support portal (nvidia.custhelp.com) and locate the DGX A100 firmware download page
  3. Download firmware version 00.19.07 or later for DGX A100
  4. Apply the firmware update through the BMC web interface or using NVIDIA's firmware update utility
  5. Reboot the BMC after the update completes
  6. Verify the new firmware version reflects 00.19.07 or higher
Caveat Firmware updates may require brief system downtime; ensure proper shutdown procedures are followed

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

Fix this in Dgx A100 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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