CVE-2022-28200
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 contains a vulnerability in SBIOS in the BiosCfgTool, where a local user with elevated privileges can read and write beyond intended bounds in SMRAM, which may lead to code execution, escalation of privileges, denial of service, and information disclosure. The scope of impact 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 confidenceNVIDIA DGX A100 systems contain an out-of-bounds read/write vulnerability in the SBIOS component accessible via BiosCfgTool. A local privileged user can access memory beyond intended boundaries in SMRAM (System Management RAM), a protected memory region used for BIOS runtime services. This memory corruption can lead to code execution, privilege escalation, denial of service, or 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< 22.5.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm DGX A100 hardware modelCheck system inventory or run 'lshw' or 'dmidecode' to verify the system is an NVIDIA DGX A100. This vulnerability only affects DGX A100 systems.Affected if The system is not an NVIDIA DGX A100
-
Check SBIOS firmware versionUse BiosCfgTool or vendor-provided firmware query utility to retrieve the current SBIOS firmware version. Compare against the affected version range of < 22.5.5.Affected if The installed firmware version is lower than 22.5.5
-
Verify BiosCfgTool accessibilityDetermine if BiosCfgTool binary is present on the system and accessible to privileged users. Check file permissions and location (typically in BMC or system management tooling).Affected if BiosCfgTool is present and executable by privileged local users
-
Check for vulnerable SMRAM configurationInspect SMRAM configuration status via dmesg, biosdecode, or system management interfaces. Look for open or unlocked SMRAM regions that could be accessed.Affected if SMRAM is configured in an accessible state for local privileged users
The system is affected if it is an NVIDIA DGX A100 with SBIOS firmware version below 22.5.5 and BiosCfgTool is accessible to privileged local users.
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 · scoped22.5.5
Apply NVIDIA firmware/BIOS updates for DGX A100 when available; restrict physical and local console access to systems; monitor for unauthorized SBIOS configuration changes; consider disabling BiosCfgTool if not required for operations.
DGX A100 Firmware 22.5.5 or later
- Identify the current firmware version on the NVIDIA DGX A100 system
- Download the NVIDIA DGX A100 firmware version 22.5.5 or later from the NVIDIA Enterprise Support portal or nvidia.custhelp.com
- Follow NVIDIA's documented firmware update procedure for DGX A100 systems
- Verify the firmware has been successfully updated to version 22.5.5 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2022-28200 — 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-2022-28200 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