dbcve.org
Dgx A100 FirmwareOperating system · Nvidia

CVE-2022-42272

HIGH · 8.8 CVSS v3.1 Published 2023-01-12
Fix available
A fix is available. Upgrade to 00.19.07 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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, which may lead to code execution, denial of service or escalation of privileges.

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 · high confidence

NVIDIA BMC contains a buffer overflow vulnerability in the IPMI handler. An authorized attacker with valid credentials can trigger the overflow, potentially achieving code execution, causing denial of service, or escalating privileges to higher levels on the system.

MitigationApply the NVIDIA firmware update for the BMC when available. Restrict access to IPMI management interfaces to authorized personnel only using network segmentation and strong authentication.

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 the system as DGX A100
    Check the system model or product name via `lshw` or `dmidecode -s system-product-name` or inspect the physical hardware labeling
    Affected if The system is not a DGX A100, as this CVE specifically affects that product line
  2. Check BMC firmware version
    Access BMC web interface or use IPMI tool: `ipmitool -I lanplus -H <bmc_ip> -U admin -P <pass> raw` or check via BMC firmware version command; compare against 00.19.07
    Affected if The installed BMC firmware version is lower than 00.19.07 on a DGX A100 system
  3. Verify IPMI service is enabled
    Check if IPMI kernel modules are loaded: `lsmod | grep ipmi` or check BMC network configuration to confirm IPMI over LAN is active
    Affected if IPMI over LAN is enabled and accessible on the network
  4. Assess IPMI network exposure
    Review network configuration or firewall rules to determine if the BMC IPMI interface (typically port 623 UDP) is exposed to untrusted networks
    Affected if IPMI interface is reachable from networks outside the trusted management network

A DGX A100 system with BMC firmware version below 00.19.07 and IPMI accessible over the network is affected by this vulnerability if an attacker obtains valid IPMI credentials.

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 NVIDIA firmware update for the BMC when available. Restrict access to IPMI management interfaces to authorized personnel only using network segmentation and strong authentication.

Recommended fix Moderate confidence

DGX A100 BMC firmware version 00.19.07

  1. Identify the current DGX A100 BMC firmware version using the BMC web interface or IPMI commands (e.g., `ipmitool -I lanplus -H <bmc_ip> -U admin -P <password> fru print` or `ipmitool -I lanplus -H <bmc_ip> -U admin -P <password> mc info`)
  2. Download the DGX A100 firmware update package version 00.19.07 or later from the NVIDIA Enterprise Support portal at nvidia.custhelp.com
  3. Review the firmware update instructions and ensure the system is powered on and BMC is accessible
  4. Upload the firmware update to the BMC via the web interface or using IPMI commands (e.g., `ipmitool -I lanplus -H <bmc_ip> -U admin -P <password> raw ...` or NVIDIA-provided update utility)
  5. Initiate the firmware update process and monitor for completion
  6. Verify the BMC firmware has been updated to version 00.19.07 or later by checking the firmware version again
  7. Reboot the BMC or host system if recommended by NVIDIA's update documentation to ensure all components are properly initialized
Caveat Firmware updates may require system downtime; ensure proper backup and maintenance window planning; 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
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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