CVE-2022-42287
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 IPMI handler, where an authorized attacker can upload and download arbitrary files under certain circumstances, which may lead to denial of service, escalation of privileges, 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 contains a vulnerability in the IPMI handler that allows an authorized attacker to upload and download arbitrary files. This improper file handling in the IPMI service can lead to denial of service, privilege escalation, 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify NVIDIA BMC hardwareCheck system hardware documentation or BMC web interface to confirm the system uses an NVIDIA Baseboard Management Controller (BMC). Look for NVIDIA branding in BMC firmware or hardware specs.Affected if System does not use an NVIDIA BMC, the vulnerability does not apply.
-
Check BMC firmware versionAccess the BMC web interface or use IPMI commands (e.g., ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> raw command) to retrieve the BMC firmware version. Compare the version number against 00.19.07.Affected if Firmware version is lower than 00.19.07 (e.g., 00.19.06, 00.18.x, etc.).
-
Verify IPMI service is enabledConfirm the IPMI service is active on the BMC. Use IPMI-over-LAN checks or examine BMC network settings to see if IPMI/Redfish interfaces are exposed.Affected if IPMI is disabled and not accessible, the attack surface is reduced though the vulnerable code may still exist in firmware.
-
Check IPMI access controlsReview BMC user accounts and IPMI access permissions. Determine whether anonymous or low-privilege IPMI accounts exist that could exploit the file handling flaw.Affected if IPMI allows unauthorized or weakly-authenticated access to file upload/download functions.
Environment is affected if it runs an NVIDIA BMC with firmware version below 00.19.07 and has IPMI service accessible with weak or compromised access controls.
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 BMC firmware update to patch the vulnerable IPMI handler. Review IPMI access controls and restrict network accessibility of the BMC management interface to minimize attack surface.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42287 — 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-42287 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