CVE-2022-42279
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 · uneditedNVIDIA BMC contains a vulnerability in SPX REST API, where an authorized attacker can inject arbitrary shell commands, which may lead to code execution, denial of service, information disclosure and data tampering.
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 confidenceNVIDIA BMC firmware contains a command injection vulnerability in the SPX REST API where an authenticated attacker can inject arbitrary shell commands through unsanitized input. This allows complete system compromise including code execution, denial of service, information disclosure, and data tampering.
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< 00.19.07CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the system modelCheck if the system is an NVIDIA DGX A100 by reviewing system inventory, BMC web interface, or hardware labelingAffected if System is not a DGX A100 - this CVE does not apply to other NVIDIA products
-
Check BMC firmware versionAccess the BMC (Baseboard Management Controller) web interface or use IPMI commands to retrieve the firmware version. Compare against the affected range: versions prior to 00.19.07 on DGX A100 are vulnerableAffected if Firmware version is lower than 00.19.07 on a DGX A100 system
-
Verify SPX REST API accessibilityDetermine if the SPX REST API endpoint is exposed and accessible on the BMC. This is typically accessible via HTTPS on the BMC management network interfaceAffected if SPX REST API is enabled and accessible from untrusted networks increases exposure risk, but the vulnerability still requires authentication
-
Review BMC user accounts and access logsExamine BMC user accounts for unauthorized or unexpected accounts, and review access logs for suspicious API calls or command patternsAffected if Unexpected user accounts or anomalous REST API calls are detected, this may indicate exploitation attempts
-
Check for unexpected external network exposureReview network configuration to determine if the BMC management interface is accessible from untrusted networks or the internetAffected if BMC REST API is exposed to untrusted networks - while authentication is required for exploitation, exposure increases attack surface
A defender is affected if they have an NVIDIA DGX A100 system with BMC firmware version below 00.19.07, regardless of API exposure since the vulnerability exists in the firmware itself when the SPX REST API feature is present.
Generated from the published advisory. Verify against your own configuration.
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 data00.19.07
Apply NVIDIA's firmware patch for this vulnerability and ensure REST API input validation is properly implemented to prevent shell command injection.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42279 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-42279 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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