dbcve.org
Dgx H100 FirmwareOperating system · Nvidia

CVE-2023-31012

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 API service. An authenticated or potentially unauthenticated attacker can exploit this by sending specially crafted requests to the REST endpoint, bypassing normal input sanitization. This allows the attacker to elevate privileges beyond their assigned role and access sensitive system information that should be restricted.

MitigationApply the latest NVIDIA firmware update for the DGX H100 BMC when available, and restrict network access to the BMC management interface to trusted IP addresses 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. Identify BMC firmware version
    Log into the NVIDIA DGX H100 BMC web interface or use IPMI/Redfish to query the firmware version. Typically this is found under 'Firmware Information' or 'System Information' in the BMC dashboard, or via command: `ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> fru` or Redfish endpoint `/redfish/v1/Managers/Self`
    Affected if Firmware version is below 23.08.18 (for example, 23.07.x or earlier)
  2. Confirm REST API service status
    Access the BMC REST API endpoint to verify it is running. This can be done via curl or a browser to `https://<bmc_ip>/redfish/v1/` or the legacy REST API at `https://<bmc_ip>/api`. Check for a valid JSON response indicating the service is active.
    Affected if The REST API returns a valid response, indicating the service is enabled and accessible
  3. Verify BMC network accessibility
    Determine if the BMC management interface is reachable from untrusted networks. Run a port scan or check network configuration: `nmap -p 443,623 <bmc_ip>` (where 443 is HTTPS and 623 is IPMI). Review firewall rules or VLAN segmentation restricting BMC access.
    Affected if The BMC is accessible from networks beyond trusted administration subnets
  4. Check authentication configuration
    Review BMC user accounts and role assignments via the web UI under 'User Management' or via Redfish endpoint `/redfish/v1/Managers/Self/RemoteAccountService`. Identify whether default accounts exist or if guest/anonymous access is permitted.
    Affected if Multiple user roles exist, or guest/anonymous authentication is enabled, allowing potential privilege escalation

The environment is likely affected if the DGX H100 BMC firmware version is below 23.08.18 and the REST API service is network-accessible, regardless of authentication status.

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 network access to the BMC management interface to trusted IP addresses only.

Recommended fix High confidence

DGX H100 Firmware 23.08.18 or later

  1. Identify the current DGX H100 BMC firmware version using the BMC web interface or command line tools
  2. Download the DGX H100 firmware version 23.08.18 or later from the NVIDIA Enterprise Support portal at nvidia.custhelp.com
  3. Follow NVIDIA's standard BMC firmware update procedure to apply the new firmware version
  4. Verify the firmware update was successful by checking the BMC version after reboot
  5. Confirm the vulnerability is resolved by verifying the installed firmware version is 23.08.18 or higher

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

Fix this in Dgx H100 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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