dbcve.org
Dgx H100 FirmwareOperating system · Nvidia

CVE-2023-25529

HIGH · 8.1 CVSS v3.1 Published 2023-09-20
Fix available
A fix is available. Upgrade to 23.08.18 or later.
See remediation →
90/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 and DGX A100 BMC contains a vulnerability in the host KVM daemon, where an unauthenticated attacker may cause a leak of another user’s session token by observing timing discrepancies between server responses. A successful exploit of this vulnerability may lead to information disclosure, escalation of privileges, 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 · moderate confidence

The NVIDIA DGX H100 BMC and DGX A100 BMC host KVM daemon contains a timing-based side-channel vulnerability. An unauthenticated attacker can infer valid session tokens from other users by measuring subtle timing differences in server responses, potentially enabling session hijacking, privilege escalation, and data tampering.

MitigationApply the vendor-provided BMC firmware patch when released. In the interim, restrict network access to the BMC management interface using firewall rules and network segmentation to limit exposure to unauthenticated attackers.

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

CVSS:3.1/AV:N/AC:H/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. Check BMC firmware version on NVIDIA DGX H100
    Access the BMC web interface or use IPMI command 'ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> mc info' to retrieve the firmware version. Compare the version string to 23.08.18.
    Affected if The firmware version is lower than 23.08.18 on a DGX H100 system.
  2. Check BMC firmware version on NVIDIA DGX A100
    Access the BMC web interface or use IPMI command 'ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> mc info' to retrieve the firmware version.
    Affected if The firmware version is any version on a DGX A100 system (full version range not specified in provided data).
  3. Verify if KVM over IP feature is enabled
    Log into the BMC web interface and navigate to the KVM settings, or use IPMI to query KVM status: 'ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> raw' commands related to KVM SOL/VM. Check if remote KVM sessions can be initiated.
    Affected if KVM feature is enabled and accessible on the BMC.
  4. Assess network exposure of BMC management interface
    Verify that the BMC IP is accessible from untrusted networks. Use nmap or similar tool to check if ports 443 (HTTPS) or 80 (HTTP) are exposed to the network where unauthenticated attackers could potentially send timing-based requests.
    Affected if The BMC management interface is reachable from untrusted or external networks without firewall protection.

A system is affected if it runs NVIDIA DGX H100 BMC firmware below version 23.08.18 (or any DGX A100 BMC version) with KVM enabled and the BMC interface is network-accessible to unauthenticated attackers.

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 vendor-provided BMC firmware patch when released. In the interim, restrict network access to the BMC management interface using firewall rules and network segmentation to limit exposure to unauthenticated attackers.

Recommended fix Moderate confidence

NVIDIA DGX H100 BMC firmware >= 23.08.18 (and corresponding DGX A100 BMC firmware update from NVIDIA)

  1. 1. Identify current BMC firmware version by running 'ipmitool mc info' or accessing the BMC web interface
  2. 2. Navigate to NVIDIA's DGX support portal at nvidia.custhelp.com to download firmware version 23.08.18 or later
  3. 3. Review NVIDIA's firmware update documentation for DGX H100 or DGX A100 systems
  4. 4. Apply the firmware update using NVIDIA's recommended procedure (typically via BMC web interface, ipmitool, or NVIDIA DGX OS)
  5. 5. Verify the firmware has been updated to version 23.08.18 or later after the update completes
  6. 6. Test KVM functionality to ensure the update was successful and the vulnerability is remediated
Caveat Firmware updates may require system downtime; ensure proper backup and coordinated maintenance window

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
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
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,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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