dbcve.org
Dgx A100 FirmwareOperating system · Nvidia

CVE-2022-42271

HIGH · 7.8 CVSS v3.1 Published 2023-01-11
Fix available
A fix is available. Upgrade to 00.19.07 or later.
See remediation →
80/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 BMC contains a vulnerability in IPMI handler, where an authorized attacker can cause a buffer overflow and cause a denial of service or gain code execution

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 BMC contains a buffer overflow vulnerability in the IPMI (Intelligent Platform Management Interface) handler. An authorized attacker with IPMI access can exploit this to cause a denial of service condition or potentially execute arbitrary code on the BMC firmware.

MitigationApply the latest NVIDIA BMC firmware update when available. Restrict IPMI/remote management access to trusted networks or use strong authentication to reduce attack surface.

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

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the system is an NVIDIA DGX A100
    Check the system model via 'ipmitool mc info' or by inspecting /sys/class/dmi/id/product_name, or via the BMC web interface system information page
    Affected if The system is not a DGX A100 (different models are not affected by this specific CVE)
  2. Determine the BMC firmware version
    Run 'ipmitool -I lanplus -H <bmc_ip> -U admin -P password mc info' or use the BMC web interface to view firmware version under Server Health or System Information
    Affected if The firmware version is earlier than 00.19.07 (versions starting with 00.19.07 or higher are patched)
  3. Verify IPMI over LAN is enabled
    Run 'ipmitool -I lanplus -H <bmc_ip> -U admin -P password lan print' or check BMC settings via web interface under IPMI > Network Settings
    Affected if IPMI over LAN is enabled - this is the attack vector required to exploit the vulnerability
  4. Check IPMI user accounts and access restrictions
    Review IPMI user list with 'ipmitool -I lanplus -H <bmc_ip> -U admin -P password user list' and check network access controls in BMC network settings
    Affected if IPMI is accessible to untrusted networks or uses weak/default credentials - these conditions increase exposure to the vulnerability

The system is affected if it is an NVIDIA DGX A100 with BMC firmware version earlier than 00.19.07 and IPMI is enabled and accessible to the attacker.

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

Apply the latest NVIDIA BMC firmware update when available. Restrict IPMI/remote management access to trusted networks or use strong authentication to reduce attack surface.

Recommended fix High confidence

DGX A100 Firmware version 00.19.07 or later

  1. Obtain the DGX A100 firmware update from NVIDIA's official support portal at nvidia.custhelp.com
  2. Verify the current firmware version by accessing the BMC web interface or running the ipmi command: ipmi-fru or ipmi-dcmi
  3. Download firmware version 00.19.07 or later from NVIDIA's firmware download page
  4. Upload the firmware update through the BMC web interface under Firmware Update section, or use the BMC CLI/Redfish API
  5. Follow NVIDIA's documented firmware update procedure for DGX A100, ensuring stable power during the update process
  6. After update completes, verify the new firmware version is 00.19.07 or later
  7. Restart the BMC or host system as required by the update procedure
Caveat Firmware updates may require system downtime; ensure proper backup and maintenance window planning; verify compatibility with other system components

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

Fix this in Dgx A100 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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