dbcve.org
Dgx H100 FirmwareOperating system · Nvidia

CVE-2023-25531

CRITICAL · 9.8 CVSS v3.1 Published 2023-09-20
Fix available
A fix is available. Upgrade to 23.08.18 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 IPMI, where an attacker may cause insufficient protection of credentials. A successful exploit of this vulnerability may lead to code execution, denial of service, information disclosure, and escalation of privileges.

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 DGX H100 BMC contains an IPMI vulnerability where credentials are insufficiently protected, potentially allowing attackers to intercept, decode, or bypass authentication mechanisms to gain unauthorized access to the BMC and execute code, cause denial of service, obtain sensitive information, or escalate privileges.

MitigationApply NVIDIA's firmware update for the DGX H100 BMC when available, and implement network segmentation to isolate BMC/IPMI interfaces from untrusted networks as a compensating control.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 system model
    Run 'ipmiutil sel' or check system inventory/machine type. For DGX H100, the system model typically shows as 'NVIDIA DGX H100' or similar. Alternatively, check /proc/boardinfo or vendor-specific tools like 'nvidia-smi' for system information.
    Affected if The system is not a DGX H100 (not affected product)
  2. Check BMC firmware version
    Use IPMI command 'ipmiutil ver -c' or connect to BMC web interface and navigate to firmware information page. The version is typically displayed as a build number in format like XX.XX.XX.
    Affected if Firmware version is below 23.08.18 (e.g., 23.04.00, 22.x.x series)
  3. Verify IPMI/BMC interface is enabled
    Run 'ipmiutil config -c' or check BMC web interface under IPMI settings. Look for 'LAN Interface' or 'IPMI over LAN' status.
    Affected if IPMI over LAN is enabled and accessible on the network
  4. Check network exposure of BMC interface
    Review network configuration: run 'ipmiutil lan -c' to see BMC IP address and subnet. Check if BMC is on an isolated management network or directly exposed. Use 'netstat -an | grep 623' to check for UDP 623 (IPMI) listening ports.
    Affected if BMC IPMI interface is reachable from untrusted network segments

You are affected if your DGX H100 BMC firmware version is below 23.08.18 AND the IPMI/BMC interface is network-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 NVIDIA's firmware update for the DGX H100 BMC when available, and implement network segmentation to isolate BMC/IPMI interfaces from untrusted networks as a compensating control.

Recommended fix Moderate confidence

DGX H100 BMC Firmware 23.08.18 or later

  1. Download the NVIDIA DGX H100 BMC firmware version 23.08.18 or later from NVIDIA's official support portal (nvidia.custhelp.com)
  2. Follow NVIDIA's documented firmware update procedure for the DGX H100 BMC, typically involving the update utility provided by NVIDIA
  3. Verify the BMC firmware has been updated to version 23.08.18 or later after the update process completes
  4. Confirm that IPMI functionality is operating normally after the firmware upgrade
Caveat Firmware updates to BMC components carry risk of system downtime; ensure proper backup and downtime window before applying

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
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
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,440.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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