dbcve.org
SbiosOperating system · Nvidia

CVE-2023-25506

HIGH · 8.2 CVSS v3.1 Published 2023-04-22
Fix available
A fix is available. Upgrade to 52w_3a13 or later.
See remediation →
84/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-1 contains a vulnerability in Ofbd in AMI SBIOS, where a preconditioned heap can allow a user with elevated privileges to cause an access beyond the end of a buffer, which may lead to code execution, escalation of privileges, denial of service and information disclosure. The scope of the impact of this vulnerability can extend to other components.

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-1 contains a heap-based buffer overflow vulnerability in the Ofbd component of AMI SBIOS. A privileged user can trigger an out-of-bounds memory access beyond the allocated buffer, potentially achieving code execution, privilege escalation, denial of service, or information disclosure. The vulnerability's impact may propagate to other system components.

MitigationApply the latest NVIDIA DGX-1 firmware/SBIOS update from NVIDIA's support channels. Restrict physical and privileged access to affected systems until the patch is deployed.

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
SbiosOperating system
Affected:< 52w_3a13

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/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 if the system is a NVIDIA DGX-1
    Run 'dmidecode -s system-product-name' or check system documentation/labels to confirm the hardware model
    Affected if The system is not a NVIDIA DGX-1, then this specific CVE does not apply
  2. Retrieve the installed SBIOS version
    Run 'dmidecode -s bios-version' on Linux, or access via IPMI: 'ipmitool -I lanplus -H <bmc_ip> -U admin -P <pass> raw' or check the BIOS/UEFI setup screen
    Affected if Unable to retrieve SBIOS version, cannot determine exposure
  3. Verify the Ofbd component is present
    The Ofbd (Open Firmware Debug) is part of the AMI SBIOS firmware - check SBIOS release notes or run 'dmidecode' to confirm AMI SBIOS implementation
    Affected if System uses a different SBIOS vendor, the specific vulnerability path may differ
  4. Compare installed version against 52w_3a13
    Compare the version retrieved in step 2 to the affected version threshold: any version less than 52w_3a13 is vulnerable
    Affected if Installed SBIOS version is 52w_3a13 or higher, the vulnerability is patched in this version and later

A user is affected if they have a NVIDIA DGX-1 system running an AMI SBIOS version lower than 52w_3a13 with the Ofbd component enabled.

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

Apply the latest NVIDIA DGX-1 firmware/SBIOS update from NVIDIA's support channels. Restrict physical and privileged access to affected systems until the patch is deployed.

Recommended fix High confidence

SBIOS version 52w_3a13 or later

  1. Identify the current SBIOS version running on the NVIDIA DGX-1 system
  2. Obtain the fixed SBIOS version 52w_3a13 or later from NVIDIA's official support portal (nvidia.custhelp.com)
  3. Follow NVIDIA's documented SBIOS update procedure for DGX-1, which typically involves flashing the new firmware
  4. Reboot the system to apply the SBIOS update
  5. Verify the SBIOS has been updated to version 52w_3a13 or later after the update completes

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

Fix this in Sbios Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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