dbcve.org
BmcOperating system · Nvidia

CVE-2022-42283

HIGH · 7.8 CVSS v3.1 Published 2023-01-13
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 firmware contains a buffer overflow vulnerability in the IPMI (Intelligent Platform Management Interface) handler. An authenticated attacker with authorized access to the BMC can trigger the buffer overflow, potentially leading to denial of service or arbitrary code execution with elevated privileges on the BMC system.

MitigationApply NVIDIA's firmware update for affected BMC versions. If no update is available, restrict BMC network access to trusted networks and limit IPMI user privileges to the minimum required.

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
BmcOperating 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 NVIDIA BMC firmware presence
    Check if the system has NVIDIA Baseboard Management Controller firmware by querying the BMC via IPMI command: `ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> mc info` or access the BMC web interface to view system information
    Affected if The system does not have NVIDIA BMC firmware - this CVE does not apply
  2. Determine BMC firmware version
    Retrieve the BMC firmware version using IPMI: `ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> mc info` or via the BMC web interface under Firmware/Software Information
    Affected if The installed firmware version is below 00.19.07 (for example, 00.19.00, 00.18.x, or earlier)
  3. Verify IPMI handler is accessible
    Confirm IPMI is enabled and reachable on the BMC by attempting to connect via IPMI over LAN: `ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> chassis status` or check BMC network settings
    Affected if IPMI over LAN is enabled and accessible from the network - the attack surface exists
  4. Check IPMI user privileges
    List IPMI users and their privilege levels using: `ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> user list` or via BMC web interface user management
    Affected if There are IPMI users with Administrator or high privilege levels - an authenticated attacker could exploit this vulnerability

The environment is affected if the NVIDIA BMC firmware version is below 00.19.07 and IPMI is accessible with authenticated user accounts.

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 NVIDIA's firmware update for affected BMC versions. If no update is available, restrict BMC network access to trusted networks and limit IPMI user privileges to the minimum required.

Recommended fix Moderate confidence

BMC firmware version 00.19.07 or later

  1. Identify the current BMC firmware version running on the affected NVIDIA hardware
  2. Download the latest BMC firmware version 00.19.07 or later from NVIDIA's support portal at nvidia.custhelp.com
  3. Review NVIDIA's firmware update instructions and ensure proper power backup during the update process
  4. Apply the BMC firmware upgrade following NVIDIA's documented procedure
  5. Verify the BMC firmware has been successfully updated to version 00.19.07 or later
Caveat BMC firmware upgrades may require system downtime and should be performed according to NVIDIA's official update procedures

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

Fix this in Bmc 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-42283 — 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-42283 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