dbcve.org
Dgx H100 FirmwareOperating system · Nvidia

CVE-2023-31013

HIGH · 8.8 CVSS v3.1 Published 2023-09-20
Fix available
A fix is available. Upgrade to 23.08.18 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 DGX H100 BMC contains a vulnerability in the REST service, where an attacker may cause improper input validation. A successful exploit of this vulnerability may lead to escalation of privileges and information disclosure.

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

The NVIDIA DGX H100 Baseboard Management Controller (BMC) contains an improper input validation vulnerability in its REST service. This flaw allows an attacker to potentially escalate privileges and disclose information by exploiting insufficient validation of user inputs in the BMC's REST API endpoints.

MitigationApply the NVIDIA firmware patch for CVE-2023-31013 to the DGX H100 BMC. Review BMC access controls and restrict REST service access to authorized management networks until the patch is applied.

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 H100 FirmwareOperating system
Affected:< 23.08.18

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 the BMC firmware version
    Access the DGX H100 BMC web interface or use IPMI/redfish command (e.g., `ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> raw` or Redfish GET /redfish/v1/Managers/Self) to retrieve the current firmware version.
    Affected if The firmware version is below 23.08.18
  2. Verify the BMC REST service is accessible
    Attempt to reach the BMC REST API endpoint (e.g., `curl -k https://<BMC_IP>/redfish/v1/` or check if port 443/HTTPS is open and responding).
    Affected if The REST service is reachable and responding to requests
  3. Confirm BMC network exposure
    Review the BMC network configuration to determine if the REST service is bound to any network interface (management network, OOB, or data plane) and check firewall rules or ACLs controlling access.
    Affected if The BMC REST service is exposed to unauthorized or untrusted networks (not restricted to a dedicated management VLAN)
  4. Check BMC user account privileges
    List BMC user accounts and their privilege levels via the web UI or Redfish API (GET /redfish/v1/AccountService/Accounts).
    Affected if Multiple accounts exist with elevated privileges or there are accounts with unnecessary access to the REST API

You are affected if the DGX H100 BMC firmware version is below 23.08.18 and the REST service is accessible from a network where untrusted users could send crafted API requests.

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

Apply the NVIDIA firmware patch for CVE-2023-31013 to the DGX H100 BMC. Review BMC access controls and restrict REST service access to authorized management networks until the patch is applied.

Recommended fix Moderate confidence

NVIDIA DGX H100 BMC firmware version 23.08.18 or later

  1. Identify current BMC firmware version on the DGX H100 system using the BMC web interface or IPMI commands
  2. Download the fixed firmware version 23.08.18 or later from NVIDIA's support portal (nvidia.custhelp.com)
  3. Review NVIDIA's firmware update documentation for DGX H100 before proceeding
  4. Apply the firmware update to the BMC following NVIDIA's recommended procedure
  5. Verify the firmware update was successful by checking the BMC version
  6. Restart the BMC if required by the update procedure
  7. Validate that the REST service is functioning correctly after the update
Caveat Firmware updates carry inherent risks and should be performed according to NVIDIA's official documentation; ensure proper backup and downtime window

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

Fix this in Dgx H100 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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