dbcve.org
BmcOperating system · Nvidia

CVE-2022-42282

MEDIUM · 5.5 CVSS v3.1 Published 2023-01-13
Fix available
A fix is available. Upgrade to 00.19.07 or later.
See remediation →
57/100
Remediation priority · Elevated
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 API, where an authorized attacker can access arbitrary files, which may lead to 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 path traversal vulnerability in the SPX REST API where an authenticated attacker can use directory traversal sequences (e.g., '../') in API requests to access arbitrary files outside the intended web root, leading to sensitive information disclosure.

MitigationApply the NVIDIA BMC firmware patch when available; until then, restrict network access to the BMC management interface to trusted networks and enforce 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
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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 NVIDIA BMC firmware version
    Access the BMC web interface and navigate to the Firmware/Version information page, or run the equivalent CLI command (such as 'ipmiutil ver' or 'bmcinfo') to retrieve the installed firmware version string
    Affected if The firmware version is below 00.19.07 (for example, 00.18.05, 00.17.00, etc.)
  2. Confirm the SPX REST API is accessible
    Attempt to reach the SPX REST API endpoint on the BMC (typically at /api/spx or similar path) using a web browser or curl command: curl -k https://<bmc-ip>/api/spx
    Affected if The API responds with HTTP 200 or authentication prompts, indicating the endpoint is exposed and enabled
  3. Verify the BMC management interface network exposure
    Review BMC network configuration settings to determine if the management interface is accessible from untrusted networks. Check firewall rules, IP access control lists, or interface binding settings
    Affected if The BMC REST API is reachable from networks outside of trusted management subnets
  4. Test for directory traversal vulnerability (if authorized)
    Send an authenticated API request with directory traversal sequences to the SPX REST API, for example: curl -k -u <user>:<pass> https://<bmc-ip>/api/spx/../../../etc/passwd
    Affected if The API returns file contents from outside the intended web root directory (such as /etc/passwd or other system files)
  5. Review BMC user authentication status
    Check the list of configured BMC users and confirm whether local or remote authentication is enabled. Access user management through the web UI or BMC user command
    Affected if There exists at least one enabled BMC user account that can authenticate to the SPX REST API, as the vulnerability requires an authenticated attacker

The environment is affected if the BMC firmware version is below 00.19.07 AND the SPX REST API is accessible to an authenticated user, allowing potential path traversal attacks to read arbitrary files.

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 BMC firmware patch when available; until then, restrict network access to the BMC management interface to trusted networks and enforce strong authentication.

Recommended fix Moderate confidence

00.19.07

  1. Identify the specific NVIDIA BMC product model (e.g., SPX firmware for NVIDIA DGX systems)
  2. Access the NVIDIA BMC firmware download page or contact NVIDIA enterprise support
  3. Download the BMC firmware version 00.19.07 or later from NVIDIA's official support portal
  4. Review NVIDIA's firmware update documentation for your specific hardware platform
  5. Apply the firmware update via the BMC web interface, CLI, or IPMI, following NVIDIA's recommended procedure
  6. Verify the firmware version has been updated to 00.19.07 or later after reboot
  7. Confirm the SPX REST API no longer allows path traversal by testing with authorized credentials
Caveat BMC firmware updates may require system downtime and should be performed according to NVIDIA's documented procedures; ensure backup of configuration before upgrading

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

Fix this in Bmc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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