dbcve.org
BmcOperating system · Nvidia

CVE-2022-42280

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 SPX REST auth handler, where an un-authorized attacker can exploit a path traversal, which may lead to authentication bypass.

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 firmware contains a path traversal vulnerability in the SPX REST authentication handler. An unauthenticated remote attacker can manipulate file path references to bypass authentication mechanisms and gain unauthorized access to protected resources or administrative functions.

MitigationApply the vendor-supplied firmware patch for the SPX BMC platform. If patch unavailable, restrict network access to the BMC management interface and disable unnecessary REST API endpoints.

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. Confirm NVIDIA SPX BMC platform
    Identify the BMC hardware platform. For NVIDIA systems, this is typically shown in the BMC web interface under 'System Information' or can be queried via IPMI: `ipmitool -I lanplus -H <BMC_IP> -U admin -P <password> raw` or check the physical label/model number.
    Affected if Device is not an NVIDIA SPX BMC platform - different hardware is not affected by this specific vulnerability.
  2. Retrieve BMC firmware version
    Access the BMC web interface and navigate to ' firmware version' or 'System Information' page. Alternatively, use IPMI: `ipmitool -I lanplus -H <BMC_IP> -U admin -P <password> raw 0x06 0x01` or check the BIOS/UEFI boot screen for BMC firmware version.
    Affected if Unable to retrieve firmware version - version must be confirmed to assess exposure.
  3. Compare firmware version against affected range
    Compare your installed BMC firmware version to the affected versions. The vulnerability affects versions before 00.19.07. Version format is typically MAJOR.MINOR.PATCH (e.g., 00.18.05).
    Affected if Firmware version is below 00.19.07 (for example, 00.18.05, 00.17.00, etc.) - the system is running a vulnerable version.
  4. Verify REST API endpoint accessibility
    Test if the SPX REST API is accessible on the BMC. Try accessing a known REST endpoint via curl or browser: `curl -k https://<BMC_IP>/api/` or check if port 443/HTTPS is open on the BMC management interface.
    Affected if REST API endpoints are exposed and accessible from a network where untrusted actors exist - the vulnerability requires the REST handler to be reachable.
  5. Check network exposure of BMC management interface
    Review firewall rules, VLAN configuration, and access control lists to determine if the BMC HTTPS management port (typically 443) is reachable from untrusted networks or the wider internet.
    Affected if BMC management interface is directly exposed to untrusted networks or the internet without proper access controls - increases likelihood of exploitation.

System is affected if it is an NVIDIA SPX BMC running firmware version below 00.19.07 with accessible REST API endpoints exposed to untrusted networks.

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.

From vendor data
Upgrade available Upgrade to 00.19.07 or later
Fixed in 00.19.07
Interim mitigation

Apply the vendor-supplied firmware patch for the SPX BMC platform. If patch unavailable, restrict network access to the BMC management interface and disable unnecessary REST API endpoints.

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-42280 — 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-42280 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