CVE-2023-31033 is a medium severity flaw (CVSS 6.8) in NVIDIA DGX A100 firmware. A user on an adjacent network may reach a critical function that has no authentication. 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.
NVIDIA's vector is adjacent network, low complexity, high privileges required.
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
The class is CWE-306, missing authentication for a critical function. A feature that changes important state does not check who is asking. NVIDIA lists impacts including privilege escalation, code execution, denial of service, information disclosure and data tampering.
The vector carries a high privilege requirement, which is why the score stays at 6.8 despite the broad impact list. On management networks, a flat layout means any compromised neighbour is in range. The CVE is not on the CISA KEV list.
Treat the adjacent network requirement as a design question. If a management VLAN holds many hosts, a compromise of any one of them puts the BMC in reach. Put BMCs behind a jump host or a dedicated management firewall, and log access to them. Log every administrative login to the BMC and send those logs to a place the BMC itself cannot alter, so unexpected access shows up.
Quick check
Is it exploitable from the internet?
The vector is adjacent network, so the attacker must be on the same segment.
What is the fix?
BMC firmware 00.22.05 or later.
Sources
Last reviewed: 19 October 2026.