dbcve.org
Dgx H100 FirmwareOperating system · Nvidia

CVE-2023-25528

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 baseboard management controller (BMC) contains a vulnerability in a web server plugin, where an unauthenticated attacker may cause a stack overflow by sending a specially crafted network packet. A successful exploit of this vulnerability may lead to arbitrary code execution, denial of service, information disclosure, and data tampering.

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 · high confidence

A stack overflow vulnerability in the NVIDIA DGX H100 baseboard management controller (BMC) web server plugin allows unauthenticated remote attackers to send specially crafted network packets that overflow a stack buffer, potentially enabling arbitrary code execution, denial of service, information disclosure, or data tampering.

MitigationApply NVIDIA's firmware update for the DGX H100 BMC when available, and restrict network access to the BMC management interface (e.g., place on isolated management network) until the patch can be applied.

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 NVIDIA DGX H100 system
    Check the system model or hostname (e.g., run 'dmidecode -s system-product-name' or check physical labeling) to confirm it is an NVIDIA DGX H100 server
    Affected if System is not an NVIDIA DGX H100 (not affected)
  2. Check BMC firmware version
    Access the BMC web interface or use IPMI/Redfish to query the firmware version (e.g., via 'ipmitool -I lanplus -H <bmc_ip> -U admin bmc info' or Redfish GET /redfish/v1/Managers/1')
    Affected if BMC firmware version is earlier than 23.08.18
  3. Verify BMC web server is network-accessible
    Confirm the BMC management interface has an active IP address on the network and the web server (typically ports 80/443 or custom BMC ports) is reachable from non-isolated networks
    Affected if BMC web interface is exposed to untrusted networks (increases exposure)
  4. Review BMC access logs
    Check BMC logs for unusual or malformed HTTP requests, particularly from unauthenticated sources (via web UI logs or 'ipmitool -I lanplus -H <bmc_ip> -U admin sel elist')
    Affected if Evidence of suspicious network packets to the BMC web server

A system is affected if it is an NVIDIA DGX H100 with BMC firmware version earlier than 23.08.18 and the BMC web 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 restrict network access to the BMC management interface (e.g., place on isolated management network) until the patch can be applied.

Recommended fix High confidence

DGX H100 BMC firmware 23.08.18

  1. Download the DGX H100 BMC firmware version 23.08.18 or later from NVIDIA's official support website (nvidia.custhelp.com)
  2. Verify the integrity of the firmware update package using checksums provided by NVIDIA
  3. Access the DGX H100 BMC web interface or use NVIDIA's recommended firmware update mechanism
  4. Upload and apply the firmware update following NVIDIA's documented BMC firmware upgrade procedure
  5. After the update completes, verify that the BMC is running firmware version 23.08.18 or later to confirm the remediation
Caveat Firmware updates to BMC components carry inherent risks and should be performed according to NVIDIA's official documentation; ensure proper power backup and follow recommended update procedures to avoid BMC corruption

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

Fix this in Dgx H100 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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