dbcve.org
Dgx A100 FirmwareOperating system · Nvidia

CVE-2022-42288

MEDIUM · 5.3 CVSS v3.1 Published 2023-01-13
Fix available
A fix is available. Upgrade to 00.19.07 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 unauthorized attacker can use certain oracles to guess a valid BMC username, which may lead to an 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 BMC contains a vulnerability in the IPMI handler where an unauthorized attacker can leverage certain oracles to perform username enumeration, allowing them to guess valid BMC usernames. This is an information disclosure vulnerability in the IPMI protocol implementation.

MitigationApply the NVIDIA firmware patch when available, and implement network segmentation to restrict access to the BMC/IPMI interface to only authorized management networks.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 DGX A100 BMC firmware version
    Use IPMI command 'ipmitool -I lanplus -H <BMC_IP> -U admin -P <password> raw' or access the BMC web interface to view firmware version information. Alternatively, use NVIDIA's hardware management tools or check the BMC firmware version through the system BIOS/UEFI interface.
    Affected if The installed BMC firmware version is lower than 00.19.07 (for example, 00.18.xx or earlier)
  2. Confirm IPMI interface is enabled and accessible
    Run 'ipmitool -I lanplus -H <BMC_IP> mc info' to verify the BMC responds to IPMI commands. Check if IPMI over LAN is enabled via 'ipmitool -I lanplus -H <BMC_IP> -U admin -P <password> raw 0x30 0x70 0x0c 0' or through the BMC web interface under IPMI settings.
    Affected if IPMI over LAN or IPMI service is enabled and reachable from a network perspective
  3. Check IPMI authentication configuration
    Review IPMI authentication settings by examining the BMC network configuration or running 'ipmitool -I lanplus -H <BMC_IP> -U admin -P <password> channel getauth 1' to see authentication parameters. Verify whether null username or default credentials can be probed.
    Affected if IPMI accepts connections and authentication attempts can be made without network segmentation restricting access

You are affected if your DGX A100 BMC firmware version is below 00.19.07 AND the IPMI interface is enabled and accessible on your network.

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 patch when available, and implement network segmentation to restrict access to the BMC/IPMI interface to only authorized management networks.

Recommended fix Moderate confidence

DGX A100 Firmware version 00.19.07 or later

  1. 1. Identify the current DGX A100 BMC firmware version using BMC web interface or IPMI command: `ipmi-fru` or `ipmi-dcmi get asset info`
  2. 2. Navigate to NVIDIA's official support portal at nvidia.custhelp.com to download the firmware update package
  3. 3. Follow NVIDIA's documented firmware update procedure for DGX A100 systems, which typically involves using the BMC web interface or BMC firmware update utility
  4. 4. Verify the firmware has been updated to version 00.19.07 or later
  5. 5. Confirm the vulnerability is remediated by verifying BMC user enumeration is no longer possible through timing-based attacks
Caveat Review NVIDIA's DGX A100 firmware release notes for any changes to BMC functionality or compatibility requirements before applying the update

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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