dbcve.org
Dgx A100 FirmwareOperating system · Nvidia

CVE-2023-31030

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-12
Fix available
A fix is available. Upgrade to 00.22.05 or later.
See remediation →
100/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 A100 BMC contains a vulnerability in the host KVM daemon, where an unauthenticated attacker may cause a stack overflow by sending a specially crafted network packet. A successful exploit of this vulnerability may lead to arbitrary code execution, denial of service, 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 confidence

The NVIDIA DGX A100 BMC contains a stack overflow vulnerability in its host KVM daemon. An unauthenticated remote attacker can send a specially crafted network packet to trigger the overflow, potentially achieving arbitrary code execution with the privileges of the KVM daemon.

MitigationApply the NVIDIA firmware/security patch for CVE-2023-31030 when released. If no patch is available, restrict network access to the BMC management interface via network segmentation and ACLs to reduce attack surface.

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 A100 FirmwareOperating system
Affected:< 00.22.05

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm you are running an NVIDIA DGX A100 system
    Check the system model identifier via BMC web interface, IPMI command 'ipmiutil chassis -v', or physical system labeling
    Affected if The system is not an NVIDIA DGX A100, then it is not affected by this specific CVE
  2. Identify the BMC firmware version
    Run 'ipmiutil fru -v' or access BMC web interface to view firmware version information under System or Firmware status
    Affected if The installed BMC firmware version is 00.22.05 or higher (the fixed version); versions below 00.22.05 are affected
  3. Determine if KVM virtualization feature is enabled
    Check BMC KVM settings via web interface under KVM tab or via IPMI command 'ipmiutil sel -c' to see KVM-related events; verify if any virtual machines are configured
    Affected if KVM feature is actively enabled or in use; the vulnerability only applies when the KVM daemon is running
  4. Assess BMC network exposure
    Check BMC IP address configuration via 'ipmiutil lan -c' or BMC web interface under Network or IP settings
    Affected if BMC management interface is directly accessible from untrusted networks (not segmented/VLANed)

You are affected if you have an NVIDIA DGX A100 system with BMC firmware version below 00.22.05 and the KVM daemon feature is enabled on the BMC.

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 00.22.05 or later
Fixed in 00.22.05
Interim mitigation

Apply the NVIDIA firmware/security patch for CVE-2023-31030 when released. If no patch is available, restrict network access to the BMC management interface via network segmentation and ACLs to reduce attack surface.

Recommended fix Moderate confidence

DGX A100 Firmware 00.22.05

  1. 1. Obtain the DGX A100 firmware version 00.22.05 or later from the NVIDIA Enterprise Support portal at nvidia.custhelp.com
  2. 2. Access the DGX A100 BMC web interface or IPMI interface using administrative credentials
  3. 3. Navigate to the Firmware Update section in the BMC management interface
  4. 4. Upload and apply the firmware update package (00.22.05 or later) to the BMC
  5. 5. Verify the BMC firmware has been updated to the fixed version after the update completes
  6. 6. Reboot the BMC if required by the update process
Caveat Firmware updates to BMC components may require brief system downtime; ensure proper shutdown procedures are followed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dgx A100 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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