CVE-2023-31010
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 escalation of privileges, information disclosure, and denial of service.
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 BMC contains an improper input validation vulnerability in the IPMI protocol. Attackers with authenticated access to IPMI may send specially crafted input that bypasses validation checks, potentially allowing privilege escalation, unauthorized information access through the BMC's out-of-band management interface, or denial of service via 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 hardware model of the system - verify it is an NVIDIA DGX H100 serverAffected if The system is not a DGX H100, this CVE does not apply
-
Check BMC firmware versionAccess the BMC web interface or use IPMI commands to retrieve the current BMC firmware versionAffected if The installed BMC firmware version is lower than 23.08.18
-
Verify IPMI is enabledCheck if the IPMI interface is active on the BMC - this can be done via BMC web UI or IPMItool command 'ipmitool -I lanplus -H <bmc_ip> mc info'Affected if IPMI is disabled on the BMC, the vulnerability cannot be exploited
-
Assess IPMI network exposureDetermine if the IPMI management interface is reachable from network segments outside of a restricted management networkAffected if IPMI is exposed to untrusted networks, making it accessible for an attacker with authenticated access to exploit the flaw
A system is affected if it is a DGX H100 with BMC firmware version below 23.08.18 and has IPMI enabled and accessible, even from restricted networks, since authenticated attackers could exploit the validation bypass.
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
Isolate BMC/IPMI management interfaces on restricted networks, enforce strong authentication for IPMI access, and apply NVIDIA firmware updates for the DGX H100 BMC when available.
NVIDIA DGX H100 BMC Firmware version 23.08.18 or later
- Verify current DGX H100 BMC firmware version via IPMI or NVIDIA CLI tools (e.g., nvidia-smi or BMC web interface)
- Download the NVIDIA DGX H100 firmware update package version 23.08.18 or later from the NVIDIA Enterprise Support portal (enterprise.nvidia.com)
- Review the firmware update release notes for any specific prerequisites or procedures
- Apply the firmware update following NVIDIA's documented BMC firmware update process, typically via the BMC web interface or IPMI firmware update command
- After update completes, verify the new firmware version is 23.08.18 or later
- Restart BMC services if required by the update procedure
- Confirm the IPMI service is operational and the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31010 — 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-31010 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