dbcve.org
Dgx A100 FirmwareOperating system · Nvidia

CVE-2022-42273

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 libwebsocket, 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 Baseboard Management Controller (BMC) firmware contains a buffer overflow vulnerability in the libwebsocket library. An authenticated attacker can trigger the overflow by sending specially crafted WebSocket data, potentially causing denial of service or achieving arbitrary code execution on the BMC.

MitigationApply the vendor-supplied BMC firmware update that patches the vulnerable libwebsocket library version. Restrict BMC network access to trusted management networks and monitor for unauthorized access attempts.

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 if the system is an NVIDIA DGX A100
    Check the system hardware inventory or BMC web interface for the model name. On the BMC web UI, this is typically visible on the dashboard or system information page.
    Affected if The system is an NVIDIA DGX A100 server
  2. Check the BMC firmware version
    Access the BMC web interface and navigate to the Firmware or System Information page to view the current BMC firmware version. Alternatively, use IPMI or Redfish commands: `ipmitool -I lanplus -H <bmc-ip> -U <user> -P <pass> mc info` or query the BMC via Redfish endpoint `/redfish/v1/Managers/Self`
    Affected if The firmware version is below 00.19.07 (for example, 00.18.x or earlier)
  3. Determine if WebSocket functionality is accessible on the BMC
    Check the BMC web interface for enabled services or examine the exposed network services on the BMC IP. WebSocket endpoints are typically accessed over HTTP/HTTPS on the BMC web port. Attempt a test WebSocket connection to the BMC if you have access: `wss://<bmc-ip>/<websocket-endpoint>`
    Affected if WebSocket functionality is exposed and accessible on the BMC network interface
  4. Verify BMC network exposure
    Review network configuration to determine if the BMC is accessible from untrusted networks. Check if the BMC IP is on a dedicated management network or if it is exposed to broader network segments.
    Affected if The BMC is accessible from untrusted or public network segments rather than isolated management networks

The environment is affected if it runs an NVIDIA DGX A100 with BMC firmware version prior to 00.19.07 and the BMC WebSocket interface is network-accessible.

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 vendor-supplied BMC firmware update that patches the vulnerable libwebsocket library version. Restrict BMC network access to trusted management networks and monitor for unauthorized access attempts.

Recommended fix High confidence

DGX A100 BMC Firmware version 00.19.07 or later

  1. 1. Identify the current DGX A100 BMC firmware version via the BMC web interface or IPMI commands
  2. 2. Download the NVIDIA DGX A100 firmware update package version 00.19.07 or later from the official NVIDIA download portal
  3. 3. Verify the integrity of the downloaded firmware package using the provided checksums
  4. 4. Apply the firmware update through the BMC web interface or using NVIDIA's firmware update utilities
  5. 5. Confirm the update was successful by verifying the new BMC firmware version displays 00.19.07 or later
  6. 6. Reboot the BMC if required and verify system stability
Caveat Firmware updates may require system downtime; ensure proper backup and maintenance window planning

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 / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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