CVE-2023-31008
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 services, escalation of privileges, and 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 confidenceThe NVIDIA DGX H100 BMC contains a vulnerability in IPMI (Intelligent Platform Management Interface) where improper input validation may allow an authenticated attacker to inject malicious input. This could lead to code execution, denial of service, privilege escalation, or information disclosure. The vulnerability exists in the BMC firmware's IPMI implementation, which handles out-of-band management for the DGX H100 system.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 the system is a NVIDIA DGX H100Identify the hardware model through BMC web interface, ipmitool, or system inventory. The vulnerability applies specifically to the DGX H100 system.Affected if The system is not a NVIDIA DGX H100, then it is not affected by this specific CVE.
-
Determine the BMC firmware versionQuery the BMC firmware version using ipmitool (e.g., ipmitool mc info) or via the BMC web interface under firmware/information. Compare the installed version against the vulnerable range.Affected if The BMC firmware version is less than 23.08.18, indicating the system may be vulnerable.
-
Verify IPMI service statusCheck if IPMI is enabled and accessible on the BMC. Use ipmitool to test connectivity or check BMC configuration for IPMI/DCMI settings.Affected if IPMI is enabled and the BMC firmware version is below 23.08.18, the vulnerability is potentially exploitable.
The system is affected only if it is an NVIDIA DGX H100 with BMC firmware version below 23.08.18 and has IPMI enabled.
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-provided firmware patch for the DGX H100 BMC when available, or implement network segmentation to restrict IPMI access to trusted management networks only. Verify the BMC firmware version and monitor for NVIDIA security bulletins.
DGX H100 BMC firmware 23.08.18 or later
- Identify the current BMC firmware version on the NVIDIA DGX H100 system
- Download the DGX H100 BMC firmware version 23.08.18 or later from NVIDIA's official support portal (nvidia.custhelp.com)
- Follow NVIDIA's documented firmware update procedure for DGX H100 systems, which typically involves using the BMC web interface or command-line tools
- 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
- Implementation12.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 $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31008 — 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-31008 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