CVE-2023-25522
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 · uneditedNVIDIA DGX A100/A800 contains a vulnerability in SBIOS where an attacker may cause improper input validation by providing configuration information in an unexpected format. A successful exploit of this vulnerability may lead to 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 · moderate confidenceNVIDIA DGX A100/A800 systems contain a vulnerability in the SBIOS where improper input validation occurs when configuration information is provided in an unexpected format. This input validation failure may allow attackers to cause denial of service, information disclosure, or data tampering.
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< 1.21< 1.21CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check SBIOS firmware version on DGX A100Run `dmidecode -s bios-version` or use IPMI: `ipmitool -I lanplus -H <BMC_IP> -U admin -P <password> raw` to query the BIOS version via the BMCAffected if The reported version is less than 1.21
-
Check SBIOS firmware version on DGX A800Run `dmidecode -s bios-version` or query the BMC using IPMI similar to the A100 checkAffected if The reported version is less than 1.21
-
Verify BMC firmware versionUse NVIDIA DGX system management tools or IPMI: `ipmitool -I lanplus -H <BMC_IP> -U admin -P <password> fru print` to confirm the system model and firmware inventoryAffected if The system is a DGX A100 or A800 with SBIOS version below 1.21
The system is affected if it is an NVIDIA DGX A100 or A800 with SBIOS firmware version installed below 1.21.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.21
Apply vendor-supplied SBIOS firmware updates for the NVIDIA DGX A100/A800 when available, and restrict access to BIOS configuration interfaces to prevent unauthorized configuration modifications.
DGX A100/A800 Firmware version 1.21 or later
- Verify current firmware version on the affected DGX A100 or DGX A800 system
- Download the latest firmware version 1.21 or later from NVIDIA's support portal at nvidia.custhelp.com
- Follow NVIDIA's standard firmware upgrade procedure for DGX systems, which typically involves using the NVIDIA System Management tool or BMC interface
- Ensure the system is powered on and stable during the firmware update process
- After upgrade, verify the firmware version has been successfully updated to 1.21 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation10.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25522 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-25522 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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