CVE-2020-11489
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, all DGX-1 with BMC firmware versions prior to 3.38.30 and all DGX-2 with BMC firmware versions prior to 1.06.06, contain a vulnerability in the AMI BMC firmware in which default SNMP community strings are used, 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 · high confidenceThe AMI Baseboard Management Controller (BMC) firmware in NVIDIA DGX-1 (versions prior to 3.38.30) and DGX-2 (versions prior to 1.06.06) servers ships with hardcoded default SNMP community strings. These well-known default strings allow remote attackers with network access to the BMC to query SNMP and retrieve sensitive system information including hardware inventory, sensor readings, and configuration data.
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.06CVSS 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 BMC firmware versionAccess the BMC web interface or use IPMI command 'ipmiutil ver' or 'ipmitool -c fru list' to retrieve the firmware version. Compare against affected ranges: DGX-1 < 3.38.30, DGX-2 < 1.06.06Affected if Firmware version is below 3.38.30 for DGX-1 or below 1.06.06 for DGX-2
-
Verify SNMP service status on BMCLog into BMC web interface and navigate to SNMP settings, or use IPMI command 'ipmiutil getevent -c' or check SNMP configuration via BMC IPMI/Redfish APIAffected if SNMP service is enabled and accessible on the BMC network interface
-
Examine SNMP community string configurationView SNMP community string settings in BMC web UI under SNMP configuration section, or retrieve via IPMI 'ipmiutil snmp -c' or Redfish API at /redfish/v1/Managers/1/NetworkProtocolAffected if Community string is set to default well-known values such as 'public', 'private', 'community', or other manufacturer defaults
-
Check BMC network accessibilityAttempt to ping BMC IP address and test SNMP port (UDP 161) connectivity from an untrusted network segmentAffected if BMC SNMP port is reachable from untrusted or management-untrusted networks
You are affected if your BMC firmware version is below 3.38.30 (DGX-1) or 1.06.06 (DGX-2), SNMP is enabled, and the community strings remain at default well-known values accessible from your network.
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, and 1.06.06 or later for DGX-2. Additionally, change default SNMP community strings to unique values and restrict network access to the BMC to trusted management networks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11489 — 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-11489 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