dbcve.org
Dgx H100 FirmwareOperating system · Nvidia

CVE-2023-31015

HIGH · 7.8 CVSS v3.1 Published 2023-09-20
Fix available
A fix is available. Upgrade to 23.08.18 or later.
See remediation →
80/100
Remediation priority · High
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 a host user may cause as improper authentication issue. A successful exploit of this vulnerability may lead to escalation of privileges, information disclosure, code execution, and denial of service.

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 an improper authentication vulnerability in its REST service API. A host user with existing access can bypass authentication mechanisms in the BMC REST API, potentially leading to privilege escalation, information disclosure, code execution, or denial of service.

MitigationApply the NVIDIA firmware update for the DGX H100 BMC when available. In the interim, restrict network access to the BMC management interface using network segmentation and enforce strict access controls.

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

CVSS:3.1/AV:L/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 DGX H100 BMC firmware version
    Access the BMC web interface or use IPMI command: `ipmitool -I lanplus -H <bmc-ip> -U <user> -P <pass> raw` or check via Redfish API endpoint `/redfish/v1/Managers/Self` to retrieve the firmware version attribute.
    Affected if The firmware version is lower than 23.08.18 (e.g., 23.05.x, 22.x.x, etc.)
  2. Confirm the system is a DGX H100
    Check the BMC model or system product name via Redfish: GET `/redfish/v1/Systems/Self` or via IPMI: `ipmitool -I lanplus -H <bmc-ip> -U <user> -P <pass> raw 0x06 0x01` to retrieve system info.
    Affected if The system is identified as an NVIDIA DGX H100 with vulnerable firmware < 23.08.18
  3. Verify BMC REST API accessibility
    Check if the BMC REST API endpoints are exposed by attempting a connection to the BMC IP on port 443 or 80, or query the Redfish service endpoint: GET `https://<bmc-ip>/redfish/v1/`
    Affected if The BMC REST API (Redfish/HTTP) is accessible from a network where an untrusted host user could reach it

The environment is affected if the system is an NVIDIA DGX H100 with BMC firmware version below 23.08.18 and the BMC REST API is network-accessible to users who already have host-level access.

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 update for the DGX H100 BMC when available. In the interim, restrict network access to the BMC management interface using network segmentation and enforce strict access controls.

Recommended fix Moderate confidence

DGX H100 BMC firmware version 23.08.18

  1. Navigate to NVIDIA's support portal (nvidia.custhelp.com) and locate the DGX H100 firmware download page
  2. Download the DGX H100 BMC firmware version 23.08.18 or later from NVIDIA's official website
  3. Access the DGX H100 BMC web interface using administrative credentials
  4. Navigate to the Firmware Update section in the BMC management console
  5. Upload the downloaded firmware file and initiate the update process
  6. Wait for the firmware update to complete and the BMC to reboot
  7. Verify the installed firmware version shows 23.08.18 or later after the update

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
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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