dbcve.org
Dgx A100 FirmwareOperating system · Nvidia

CVE-2022-31603

MEDIUM · 6.7 CVSS v3.1 Published 2022-07-04
Fix available
A fix is available. Upgrade to 22.5.5 or later.
See remediation →
69/100
Remediation priority · Elevated
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 A100 contains a vulnerability in SBIOS in the IpSecDxe, where a user with high privileges and preconditioned IpSecDxe global data can exploit improper validation of an array index to cause code execution, which may lead to denial of service, data integrity impact, 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 confidence

NVIDIA DGX A100 contains an improper array index validation vulnerability in the SBIOS IpSecDxe component. A user with high privileges who has preconditioned IpSecDxe global data can exploit this to achieve code execution, potentially causing denial of service, data integrity compromise, or information disclosure.

MitigationApply the NVIDIA-provided firmware/BIOS patch for DGX A100. Restrict privileged access to systems with preconditioned IpSecDxe state and verify the SBIOS configuration after patching.

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:< 22.5.5

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 the system model
    Check if the target system is an NVIDIA DGX A100 server. This can be done via BMC/IPMI inventory data, system inventory logs, or physical system labeling.
    Affected if The system is not a DGX A100, this CVE does not apply.
  2. Check the SBIOS firmware version
    Retrieve the SBIOS firmware version from the DGX A100 BMC interface, using IPMI commands (e.g., ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> raw command) or via the NVIDIA system management interface. Compare the version number to 22.5.5.
    Affected if The installed SBIOS firmware version is below 22.5.5, indicating the system is running a vulnerable firmware version.
  3. Verify IpSecDxe component status
    Examine the SBIOS configuration or logs for the IpSecDxe component. This may be visible in the BIOS setup menu under Security or Boot settings, or accessible via BMC dump of the SBIOS configuration.
    Affected if IpSecDxe is present and enabled in the SBIOS configuration. The vulnerability requires IpSecDxe to be loaded for exploitation.
  4. Check for preconditioned IpSecDxe state
    Review system logs, SBIOS event logs, or any stored IpSecDxe configuration data for signs of prior initialization or manipulation of IpSecDxe global data. This may require BMC log extraction or direct inspection of SBIOS variable storage.
    Affected if There is evidence that IpSecDxe has been initialized with custom global data, indicating the precondition for exploitation may exist.

The system is affected if it is a DGX A100 with SBIOS firmware version below 22.5.5 and has IpSecDxe enabled in the SBIOS configuration.

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

Apply the NVIDIA-provided firmware/BIOS patch for DGX A100. Restrict privileged access to systems with preconditioned IpSecDxe state and verify the SBIOS configuration after patching.

Recommended fix High confidence

22.5.5

  1. Identify current DGX A100 firmware version using NVIDIA system management tools or BMC interface
  2. Download firmware version 22.5.5 or later from NVIDIA's official support portal (nvidia.custhelp.com)
  3. Review NVIDIA firmware update documentation for DGX A100
  4. Apply firmware update following NVIDIA's standard firmware deployment process
  5. Verify successful installation by confirming firmware version post-update
  6. Ensure proper backup of existing configuration as per NVIDIA best practices
Caveat Firmware updates may require system downtime; verify compatibility with other system components before applying

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

Fix this in Dgx A100 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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