CVE-2023-25530
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 the KVM service, 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, 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 confidenceNVIDIA DGX H100 BMC contains improper input validation vulnerability in the KVM (Keyboard-Video-Mouse) service. This flaw allows remote attackers to potentially execute code, cause denial of service, escalate privileges, and disclose information via specially crafted input to the KVM service running on the baseboard management controller.
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.
-
Identify the system modelCheck the server or BMC inventory to confirm the hardware is an NVIDIA DGX H100 systemAffected if The system is an NVIDIA DGX H100
-
Retrieve the BMC firmware versionAccess the BMC web interface or use IPMI/Redfish commands to query the BMC firmware version (for example, via 'ipmitool mc info' or the BMC firmware info page)Affected if The installed BMC firmware version is less than 23.08.18 (for example, 23.08.17 or earlier)
-
Confirm the KVM service is accessibleCheck if the KVM (Keyboard-Video-Mouse) functionality is enabled on the BMC. This may be visible in the BMC web interface under KVM settings, or via Redfish/IPMI queries to the KVM service endpointAffected if The KVM service is enabled and network-accessible on the BMC
You are affected if you have an NVIDIA DGX H100 system with BMC firmware version below 23.08.18 and the KVM service is enabled on the BMC.
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 NVIDIA firmware patches for the DGX H100 BMC when released. In the interim, isolate BMC management interfaces on restricted networks, disable unnecessary KVM functionality if possible, and enforce strict access controls to limit exposure.
23.08.18
- Obtain the DGX H100 BMC firmware update version 23.08.18 or later from NVIDIA's official support portal at nvidia.custhelp.com
- Follow NVIDIA's standard firmware update procedure for the DGX H100 system
- Update the BMC firmware to version 23.08.18 or later using the NVIDIA-provided update mechanism
- Verify the firmware version has been successfully updated post-installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing8.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,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25530 — 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-25530 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