dbcve.org
Dgx A100 FirmwareOperating system · Nvidia

CVE-2023-31031

HIGH · 7.8 CVSS v3.1 Published 2024-01-12
Fix available
A fix is available. Upgrade to 1.25 or later.
See remediation →
80/100
Remediation priority · High
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 Station A100 and DGX Station A800 SBIOS contains a vulnerability where a user may cause a heap-based buffer overflow by local access. A successful exploit of this vulnerability may lead to 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 · high confidence

Heap-based buffer overflow vulnerability in the SBIOS (system BIOS) firmware of NVIDIA DGX Station A100 and DGX Station A800 GPU computing workstations. Exploitation requires local/physical access and may allow attackers to achieve code execution, cause denial of service, or enable information disclosure and data tampering.

MitigationApply NVIDIA-provided BIOS firmware updates when available; until patched, enforce strict physical access controls and restrict local console access to trusted personnel 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:< 1.25

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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. Identify system model
    Run 'dmidecode -s system-product-name' or check /sys/class/dmi/id/product_name to confirm the hardware is a DGX Station A100 or DGX Station A800
    Affected if The system is NOT a DGX Station A100 or DGX Station A800 (not affected)
  2. Retrieve SBIOS firmware version
    Run 'dmidecode -s bios-version' or use vendor-specific tools like nvidia-smi --query-gpu=vbios_version to extract the system BIOS firmware version
    Affected if The SBIOS firmware version is detected and is below 1.25 (vulnerable)
  3. Confirm firmware version numbering
    Compare the detected version string against the affected range. Check if the version is formatted as a numeric release (e.g., 1.24, 1.23, etc.) and less than 1.25
    Affected if The firmware version is numerically less than 1.25 (affected)
  4. Verify local/physical access exposure
    Assess whether the system console or local access is available to untrusted users. Check physical security controls and console access policies
    Affected if Untrusted individuals have physical or local console access to the system (exploitation becomes feasible)

A user is affected if they have a DGX Station A100 or A800 with SBIOS firmware version below 1.25 and the system is accessible to untrusted local or physical users.

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 1.25 or later
Fixed in 1.25
Interim mitigation

Apply NVIDIA-provided BIOS firmware updates when available; until patched, enforce strict physical access controls and restrict local console access to trusted personnel only.

Recommended fix Moderate confidence

DGX A100/A800 SBIOS firmware version 1.25 or later

  1. Obtain the firmware update from NVIDIA's official support portal at nvidia.custhelp.com for your specific DGX Station model (A100 or A800)
  2. Verify the current SBIOS firmware version by accessing the system BIOS/UEFI setup or using NVIDIA system management tools
  3. Follow NVIDIA's standard firmware update procedure, typically involving either: (a) Using the NVIDIA System Management GUI or CLI tools to apply the firmware update, or (b) Accessing the BMC/ILO interface and uploading the firmware update through the web interface
  4. Restart the system after the firmware update is applied to ensure the new SBIOS is loaded
  5. Verify the firmware version has been updated to 1.25 or later to confirm the vulnerability is remediated
Caveat Firmware updates carry inherent risks and should be performed carefully; ensure proper backups and power stability during the update process

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

Fix this in Dgx A100 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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