dbcve.org
Dgx H100 FirmwareOperating system · Nvidia

CVE-2023-25532

HIGH · 7.5 CVSS v3.1 Published 2023-09-20
Fix available
A fix is available. Upgrade to 23.08.18 or later.
See remediation →
84/100
Remediation priority · High
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 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 the IPMI (Intelligent Platform Management Interface) subsystem where credentials are insufficiently protected. An attacker with network access to the BMC can exploit this flaw to obtain sensitive credential information, leading to potential unauthorized access or further compromise of the system.

MitigationApply the NVIDIA firmware update for the DGX H100 BMC when available, change all credentials after patching, and restrict network access to the BMC/IPMI interfaces using network segmentation or firewall rules.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 you are running NVIDIA DGX H100 hardware
    Check system hardware inventory or physically verify the DGX H100 server model number
    Affected if System is not a DGX H100 (different models are not affected by this specific CVE)
  2. Identify BMC firmware version
    Access the BMC web interface or use IPMI commands (e.g., 'ipmitool -I lanplus -H <bmc_ip> -U admin -P <password> raw' or check firmware version via BMC UI under Firmware Information or System Information)
    Affected if BMC firmware version is below 23.08.18 or cannot be determined (unknown version)
  3. Verify IPMI interface is network-accessible
    Check if the BMC IPMI service is listening on the network by scanning for open ports (typically UDP/623 for IPMI) or attempting to reach the BMC IP address on the IPMI protocol port
    Affected if IPMI interface is exposed to network and accessible from untrusted networks
  4. Check IPMI credential exposure risk
    Review network configuration, firewall rules, and access controls around the BMC to determine if IPMI credentials could be intercepted or if the interface is accessible to unauthorized users
    Affected if IPMI is accessible without proper network segmentation or if credentials could be captured in transit

If the DGX H100 BMC firmware version is below 23.08.18 AND the IPMI interface is network-accessible, the environment is affected by this vulnerability.

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, change all credentials after patching, and restrict network access to the BMC/IPMI interfaces using network segmentation or firewall rules.

Recommended fix Moderate confidence

NVIDIA DGX H100 BMC firmware version 23.08.18

  1. 1. Identify the current BMC firmware version on the NVIDIA DGX H100 by accessing the BMC web interface or running ipmitool command: `ipmitool mc info`
  2. 2. Navigate to the NVIDIA Enterprise Support portal (nvidia.custhelp.com) or the NVIDIA DGX support page to download the DGX H100 BMC firmware version 23.08.18 or later
  3. 3. Follow NVIDIA's documented firmware update procedure for the DGX H100 BMC, which typically involves using the BMC web interface or ipmitool to apply the firmware update
  4. 4. After updating, verify the new firmware version is 23.08.18 or higher using: `ipmitool mc info`
  5. 5. Confirm the IPMI credential protection has been addressed by reviewing the security settings

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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