CVE-2023-31034 is a medium severity flaw (CVSS 6.6) in NVIDIA DGX A100 firmware. A local attacker can cause input validation checks to be bypassed through an integer overflow. NVIDIA's fix is SBIOS 1.25 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.
The vector is local, high complexity, low privileges, with user interaction and a changed scope.
How to check if you're exposed
Read the SBIOS version from the host:
sudo dmidecode -s bios-version
The fixed SBIOS is 1.25 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 SBIOS 1.25 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-190, integer overflow or wraparound. A calculation exceeds the largest value its type can hold, wraps to a small number, and a later size or bounds check uses the wrong value. NVIDIA says the impact may include denial of service, information disclosure and data tampering.
The score is moderate because local access and user interaction are both needed. The CVE is not on the CISA KEV list.
Integer overflow bugs are a classic cause of memory corruption, and firmware is written largely in languages without automatic bounds checks. The update container fixes several firmware issues together, so applying it brings the BIOS in line with the other fixes in the same NVIDIA bulletin. Where firmware cannot be updated during business hours, schedule it with the next planned downtime and record the exception in the meantime. The vector in NVIDIA's bulletin needs user interaction, so a user must take some action for the flaw to be triggered. Review which accounts can run code locally on each DGX system, and remove access that no one needs.
Quick check
What does the overflow break?
Input validation checks, per NVIDIA's description.
Is user interaction needed?
The vector says yes.
Sources
Last reviewed: 19 October 2026.