CVE-2023-31030 is a critical severity flaw (CVSS 9.3) in NVIDIA DGX A100 firmware. An unauthenticated attacker may cause a stack overflow in the host KVM daemon by sending a crafted network packet. NVIDIA's fix is BMC firmware 00.22.05 or later, delivered in the firmware update container 23.12.1.
What's affected
NVIDIA's bulletin (revision 1.2, 25 January 2024) lists these fixed versions, delivered through the NVIDIA DGX A100 Firmware Update Container version 23.12.1 on the NVIDIA Enterprise Support Portal.
- BMC: all versions prior to 00.22.05 are affected. Fixed: 00.22.05.
- SBIOS: all versions prior to 1.25 are affected. Fixed: 1.25.
As with CVE-2023-31029, the published vector is local (AV:L) with a changed scope, even though the text mentions a network packet.
How to check if you're exposed
Read the BMC firmware version in the BMC web interface under firmware information, or from the host with this command if ipmitool is installed:
sudo ipmitool mc info
The Firmware Revision line should be 00.22.05 or later. This is a device or appliance issue, not a package you pull from a registry, so a dependency scan will not see it. Safeguard's free in-browser scan at https://gold.safeguard.sh/scan reads dependency manifests and will not detect firmware running on hardware. Use your asset inventory instead.
What to do now
- Find every NVIDIA DGX A100 system and record its BMC and SBIOS versions.
- Update to BMC firmware 00.22.05 or later by installing the DGX A100 Firmware Update Container 23.12.1 from the NVIDIA Enterprise Support Portal.
- Keep BMC interfaces on a separate management network that only administrators can reach.
Why it matters
This entry has wording nearly identical to CVE-2023-31029. NVIDIA lists both, with the same score and weakness types, CWE-121 and CWE-787. They are separate numbers, probably for separate code paths, and the bulletin does not say how they differ.
That is a practical reason to track both in your vulnerability tool and not close one on the strength of the other. One firmware release covers all of them. The CVE is not on the CISA KEV list.
Remote console features such as KVM over IP are convenient and widely used. If you do not need the feature, check whether it can be disabled in the BMC settings while you wait for the update. The bulletin does not list this as a mitigation, so treat it as a local hardening choice, not a vendor workaround.
Quick check
How is it different from CVE-2023-31029?
The bulletin does not say. Both are fixed by BMC 00.22.05.
What is the possible impact?
Code execution, denial of service, information disclosure and data tampering.
Sources
Last reviewed: 19 October 2026.