CVE-2023-0202
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 SBIOS contains a vulnerability where an attacker may modify arbitrary memory of SMRAM by exploiting the GenericSio and LegacySmmSredir SMM APIs. A successful exploit of this vulnerability may lead to denial of service, escalation of privileges, and information disclosure.
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 confidenceThe NVIDIA DGX A100 SBIOS contains a vulnerability in the GenericSio and LegacySmmSredir SMM (System Management Mode) APIs that allows an attacker to modify arbitrary memory in SMRAM (System Management RAM). Successful exploitation enables privilege escalation to SMM level, potentially allowing denial of service, code execution at the highest privilege level, and information disclosure.
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.18CVSS 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 the installed SBIOS firmware version on the DGX A100Access the BMC (Baseboard Management Controller) web interface or use IPMI command 'ipmitool raw' to query the BIOS version. On the DGX A100, you can also check via the NVIDIA DGX System Management tool or by viewing the BIOS setup screen during boot. Look for the SBIOS or System BIOS version string.Affected if The displayed SBIOS version is lower than 1.18 (for example, 1.17, 1.16, etc.)
-
Verify the firmware version through BMC firmware inventoryLog into the NVIDIA DGX A100 BMC and navigate to the Firmware Inventory or System Information page. Locate the entry for 'SBIOS' or 'BIOS' and note the full version number including any build or revision suffixes.Affected if The firmware version shown is any version prior to 1.18, as these versions contain the vulnerable GenericSio and LegacySmmSredir SMM API implementations.
-
Confirm the system is a DGX A100Verify the hardware platform by checking the system model through BMC or physical system labeling. The DGX A100 is a specific GPU compute system from NVIDIA. This vulnerability applies only to this exact platform.Affected if The system is confirmed to be an NVIDIA DGX A100 and the SBIOS version is below 1.18.
You are affected if your NVIDIA DGX A100 system runs SBIOS firmware version lower than 1.18, which contains the vulnerable GenericSio and LegacySmmSredir SMM APIs.
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.18
Apply the NVIDIA firmware/BIOS update for DGX A100 when available. If no update exists, consider compensating controls such as restricting physical access, enabling Secure Boot, and monitoring for unauthorized firmware modifications.
DGX A100 Firmware version 1.18
- 1. Navigate to the NVIDIA Enterprise Support portal or the NVIDIA DGX support page
- 2. Locate the DGX A100 firmware downloads section
- 3. Download the DGX A100 firmware version 1.18 or later
- 4. Follow NVIDIA's standard firmware update procedure for DGX A100 systems
- 5. Verify the firmware version after update to confirm the fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0202 — 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-0202 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