dbcve.org
Dgx A100 FirmwareOperating system · Nvidia

CVE-2023-31024

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 stack memory corruption 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

NVIDIA DGX A100 BMC contains a stack-based memory corruption vulnerability in the host KVM (Keyboard-Video-Mouse) daemon. An unauthenticated remote attacker can send specially crafted network packets to the BMC interface, triggering stack memory corruption that may lead to arbitrary code execution, denial of service, information disclosure, or data tampering.

MitigationApply NVIDIA firmware/security patches for DGX A100 when available; meanwhile, isolate BMC management network, disable unnecessary BMC services, and restrict IPMI/Redfish access to trusted IPs only.

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 the system is a DGX A100
    Check the system model via BMC web interface, IPMI command 'ipmitool -I lanplus -H <bmc_ip> -U admin -P <pass> raw', or inspect /sys/class/dmi/id/product_name
    Affected if System is not a DGX A100 (different models are not affected by this CVE)
  2. Determine BMC firmware version
    Access BMC web interface and navigate to the Firmware/BIOS page, or use IPMI command 'ipmitool -I lanplus -H <bmc_ip> -U admin -P <pass> raw 0x06 0x01' to retrieve firmware version
    Affected if Firmware version is below 00.22.05 (e.g., 00.22.04, 00.21.x, etc.)
  3. Verify if KVM-over-IP functionality is enabled
    Check BMC web interface under KVM settings or use Redfish API endpoint '/redfish/v1/Managers/1/RemoteConsoleService' to query KVM status
    Affected if KVM service is enabled and accessible on the BMC
  4. Check BMC network exposure
    Review network configuration to determine if BMC management interface is reachable from untrusted networks, or check firewall rules restricting access to port 443/80 on BMC
    Affected if BMC interface is accessible from network segments without proper access controls

The environment is affected if it is a DGX A100 system with BMC firmware version below 00.22.05 and the BMC/KVM service is network-accessible.

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/security patches for DGX A100 when available; meanwhile, isolate BMC management network, disable unnecessary BMC services, and restrict IPMI/Redfish access to trusted IPs only.

Recommended fix High confidence

DGX A100 Firmware version 00.22.05

  1. 1. Obtain the NVIDIA DGX A100 firmware version 00.22.05 or later from NVIDIA's official support portal at nvidia.custhelp.com
  2. 2. Access the BMC web interface or use IPMI/Redfish commands to initiate the firmware update
  3. 3. Upload the firmware image and apply the update following NVIDIA's standard BMC firmware update procedure
  4. 4. Verify the firmware version has been updated to 00.22.05 or later after the update completes
  5. 5. Reboot the BMC if required by the update process
Caveat Firmware updates to BMC components typically require brief system downtime; ensure proper maintenance windows and backup configurations

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

Fix this in Dgx A100 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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