dbcve.org
Dgx H100 FirmwareOperating system · Nvidia

CVE-2023-31011

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 BMC contains a vulnerability in its REST service where improper input validation may allow an attacker to escalate privileges and disclose sensitive information. This affects the Baseboard Management Controller firmware, which provides out-of-band management for the DGX H100 system.

MitigationApply the latest NVIDIA firmware update for the DGX H100 BMC when available, and restrict access to the BMC management interface to authorized personnel only.

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. Confirm DGX H100 system identity
    Identify the system model through BMC web UI, IPMI, or Redfish API endpoint /Systems/1. Verify the system is specifically an NVIDIA DGX H100.
    Affected if System is not an NVIDIA DGX H100
  2. Retrieve BMC firmware version
    Access BMC firmware version via IPMI command 'ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> mc info', Redfish API endpoint /Managers/1, or BMC web interface firmware info page.
    Affected if Firmware version is present and less than 23.08.18
  3. Verify REST service is enabled
    Check if BMC REST API service is accessible by attempting a GET request to the Redfish service endpoint /redfish/v1/ or checking BMC service configuration via IPMI or web UI.
    Affected if REST/Redfish service is enabled and responding on the BMC
  4. Assess BMC network exposure
    Review BMC network configuration to determine if the management interface is accessible from untrusted networks. Check IP address assignment, VLAN settings, and access control lists.
    Affected if BMC management interface is reachable from network segments outside trusted administrative zones

Environment is affected if the system is an NVIDIA DGX H100 with BMC firmware version below 23.08.18 and the BMC REST/Redfish service is enabled and accessible.

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 latest NVIDIA firmware update for the DGX H100 BMC when available, and restrict access to the BMC management interface to authorized personnel only.

Recommended fix Moderate confidence

NVIDIA DGX H100 BMC Firmware 23.08.18 or later

  1. 1. Navigate to the NVIDIA Enterprise Support portal (enterprise.nvidia.com) or the NVIDIA DGX support site
  2. 2. Locate the firmware download section for DGX H100
  3. 3. Download firmware version 23.08.18 or later
  4. 4. Review the firmware upgrade instructions specific to DGX H100 BMC
  5. 5. Follow the documented BMC firmware update procedure, which typically involves: accessing the BMC web interface or using ipmitool, uploading the firmware image, and initiating the update
  6. 6. Verify the firmware version post-update to confirm the fix is applied
Caveat Firmware upgrades carry risk of system unavailability if interrupted; ensure stable power and follow NVIDIA's recommended update procedure

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

Fix this in Dgx H100 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,780
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,048.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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