CVE-2023-25534
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 · uneditedNVIDIA DGX H100 BMC contains a vulnerability in IPMI, where an attacker may cause improper input validation. A successful exploit of this vulnerability may lead to code execution, denial of service, escalation of privileges, 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 · moderate confidenceNVIDIA DGX H100 Baseboard Management Controller (BMC) contains an improper input validation vulnerability in the IPMI subsystem. This critical flaw (CVSS 9.8) allows attackers to potentially achieve code execution, privilege escalation, denial of service, information disclosure, or data tampering through malformed IPMI commands.
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< 23.08.18CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm DGX H100 system modelIdentify the server hardware model through BMC web interface, IPMI command, or system inventory. This vulnerability only affects the DGX H100 platform.Affected if System is not an NVIDIA DGX H100
-
Retrieve BMC firmware versionAccess BMC firmware version via IPMI command 'ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> fru print' or through BMC web interface under Firmware/Info section. Compare against 23.08.18.Affected if BMC firmware version is lower than 23.08.18 or cannot be determined
-
Verify IPMI interface is accessibleTest IPMI communication using 'ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> mc info' or attempt connection to BMC port 623 (UDP). Confirm IPMI service is responding.Affected if IPMI interface is accessible on the network
-
Check IPMI network exposureReview IPMI network configuration via 'ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> lan print' or BMC web interface. Determine if IPMI is bound to non-trusted or public networks.Affected if IPMI is accessible from untrusted networks or management interfaces are not restricted
System is affected if it is a DGX H100 with BMC firmware version below 23.08.18 AND the IPMI interface is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped23.08.18
Apply the NVIDIA firmware update for the DGX H100 BMC when available; until then, isolate the management network, disable unnecessary IPMI access, and restrict BMC access to trusted IPs only.
DGX H100 firmware 23.08.18 or later
- Identify the current BMC firmware version on the NVIDIA DGX H100 system
- Download the DGX H100 firmware version 23.08.18 or later from the NVIDIA enterprise support portal (enterprise.nvidia.com) or NVIDIA NGC
- Follow NVIDIA's standard BMC firmware update procedure, typically via the BMC web interface or command-line tools such as ipmiutil or the NVIDIA DGX OS upgrade utilities
- Verify the firmware update was successful by confirming the new version in the BMC interface
- Reboot the system if required by the update process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25534 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-25534 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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