dbcve.org
Dgx A100 FirmwareOperating system · Nvidia

CVE-2023-31029

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 baseboard management controller (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

Stack overflow vulnerability in the host KVM daemon of NVIDIA DGX A100 baseboard management controller (BMC) allows unauthenticated remote attackers to execute arbitrary code via specially crafted network packets. This critical flaw affects the BMC firmware and can lead to code execution, denial of service, information disclosure, and data tampering.

MitigationApply NVIDIA firmware updates for DGX A100 BMC when available; prior to patch, restrict network access to BMC management interfaces using network segmentation and firewall rules.

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. Check BMC firmware version
    Access the BMC web interface and navigate to the Firmware/Version information page, or use IPMI command 'ipmi-fru' or Redfish API GET /redfish/v1/Managers/1 to retrieve the current firmware version.
    Affected if The firmware version is less than 00.22.05 (e.g., 00.22.04, 00.21.x, etc.)
  2. Verify KVM daemon is enabled
    Check the BMC settings via web interface under KVM settings, or query the BMC via IPMI to see if KVM virtual media services are active. Look for KVM or Virtual Media service status.
    Affected if KVM (Keyboard-Video-Mouse) or Virtual Media daemon is enabled and running on the BMC
  3. Confirm KVM network ports are accessible
    From an external system, test connectivity to typical KVM ports (5900-5901 for VNC, 623 for IPMI, 443 for BMC web) using telnet or nmap to determine if BMC management interfaces are exposed.
    Affected if BMC network ports are reachable from untrusted networks or the internet
  4. Check for KVM service process
    If you have SSH access to the BMC (limited in typical deployments), run 'ps | grep kvm' or check service status to see if the KVM daemon process is active.
    Affected if The KVM daemon process is running on the BMC system

You are affected if your DGX A100 BMC firmware version is below 00.22.05 AND the KVM/Virtual Media feature is enabled and accessible on the network.

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 NVIDIA firmware updates for DGX A100 BMC when available; prior to patch, restrict network access to BMC management interfaces using network segmentation and firewall rules.

Recommended fix High confidence

DGX A100 BMC Firmware 00.22.05 or later

  1. Identify the current DGX A100 BMC firmware version by accessing the BMC web interface or using IPMI commands
  2. Download the NVIDIA DGX A100 firmware version 00.22.05 or later from the NVIDIA Enterprise Support portal at nvidia.custhelp.com
  3. Follow NVIDIA's standard firmware update procedure for the DGX A100 BMC, which typically involves uploading the firmware file through the BMC web interface or using BMC update tools
  4. Verify the firmware update was successful by checking the BMC firmware version after the update completes
  5. Ensure the KVM daemon service is running properly after the update
Caveat Firmware upgrades on production systems carry risk of system downtime; ensure backups and maintenance windows are properly planned

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

Fix this in Dgx A100 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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