CVE-2020-11487
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 DGX servers, DGX-1 with BMC firmware versions prior to 3.38.30. DGX-2 with BMC firmware versions prior to 1.06.06 and all DGX A100 Servers with all BMC firmware versions, contains a vulnerability in the AMI BMC firmware in which the use of a hard-coded RSA 1024 key with weak ciphers 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 · high confidenceThe AMI BMC firmware in NVIDIA DGX servers (DGX-1, DGX-2, and DGX A100) contains a hard-coded RSA 1024 key used with weak cryptographic ciphers. This vulnerability could allow an authenticated or man-in-the-middle attacker to recover the key or decrypt communications, resulting in information disclosure.
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< 3.38.30< 1.06.06all versionsCVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the BMC firmware versionAccess the BMC web interface or use IPMI command 'ipmitool -I lanplus -H <BMC_IP> -U <user> -P <pass> raw' to retrieve firmware version, or check via BMC firmware update utilityAffected if Version is below 3.38.30 (for DGX-1), below 1.06.06 (for DGX-2), or any version for DGX A100 prior to latest firmware
-
Confirm the server modelCheck the physical server label or run 'dmidecode -s system-product-name' to identify if the system is NVIDIA DGX-1, DGX-2, or DGX A100Affected if System is any of these DGX models with vulnerable BMC firmware version
-
Verify BMC remote management is accessibleConfirm BMC network interface is enabled and reachable via IPMI, Redfish, or web interface on the networkAffected if BMC is network-accessible, as the vulnerability requires authenticated access or man-in-the-middle position to exploit the weak ciphers and hard-coded key
A system is affected if it is a NVIDIA DGX-1, DGX-2, or DGX A100 server running Intel BMC firmware versions below 3.38.30 (DGX-1), below 1.06.06 (DGX-2), or any version prior to latest for DGX A100, with BMC remote management enabled.
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 data1.06.063.38.30
Update BMC firmware to version 3.38.30 or later for DGX-1, version 1.06.06 or later for DGX-2, or the latest available firmware for DGX A100 servers to remove the hard-coded key and enforce stronger cryptographic algorithms.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11487 — 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-2020-11487 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