dbcve.org
Data Center Network ManagerApplication · Cisco

CVE-2020-3376

CRITICAL · 9.8 CVSS v3.1 Published 2020-07-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
A vulnerability in the Device Manager application of Cisco Data Center Network Manager (DCNM) could allow an unauthenticated, remote attacker to bypass authentication and execute arbitrary actions on an affected device. The vulnerability is due to a failure in the software to perform proper authentication. An attacker could exploit this vulnerability by browsing to one of the hosted URLs in Cisco DCNM. A successful exploit could allow the attacker to interact with and use certain functions within the Cisco DCNM.

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

An authentication bypass vulnerability in the Device Manager web application of Cisco Data Center Network Manager allows unauthenticated remote attackers to access certain hosted URLs and execute arbitrary actions on affected devices due to missing or improper authentication validation checks.

MitigationApply the relevant Cisco security patch or upgrade to a patched version of DCNM as specified in Cisco's official security advisory for this vulnerability.

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
Data Center Network ManagerApplication
Affected:= 11.0\(1\)= 11.1\(1\)= 11.2\(1\)= 11.3\(1\)

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Cisco DCNM is installed
    Check for Cisco DCNM installation directories or running services. Common locations include /opt/cisco/dcm or check for processes named 'dcm' or 'dcnm'. On Windows, check Program Files for Cisco DCNM installations.
    Affected if Cisco Data Center Network Manager software is present on the system
  2. Determine the installed DCNM version
    Access the DCNM web interface and navigate to the Help > About page, or check the installation directory for version files. Alternatively, run 'dcnm -version' from the command line if available.
    Affected if The installed version matches 11.0(1), 11.1(1), 11.2(1), or 11.3(1)
  3. Verify Device Manager web application is accessible
    Attempt to access the Device Manager URLs on the DCNM server. Common endpoints include /fm/deviceManager or similar paths under the main DCNM web interface. Check if port 8443 or 443 is listening for DCNM web services.
    Affected if The Device Manager web interface is reachable and responds to requests
  4. Check if DCNM web services are exposed to network
    Use network scanning tools (such as netstat, nmap, or similar) to verify if the DCNM web application ports (typically 8443 for HTTPS or 80 for HTTP) are listening and accessible from network locations.
    Affected if DCNM web services are exposed to untrusted networks or the internet

A system is affected if it runs Cisco Data Center Network Manager version 11.0(1), 11.1(1), 11.2(1), or 11.3(1) with the Device Manager web interface accessible over the network.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant Cisco security patch or upgrade to a patched version of DCNM as specified in Cisco's official security advisory for this vulnerability.

Recommended fix High confidence

DCNM 11.3(2) or later stable release

  1. 1. Identify the current Cisco DCNM version installed in your environment
  2. 2. Access the Cisco Software Checker at tools.cisco.com to search for CVE-2020-3376
  3. 3. Download and apply the recommended fixed release for your 11.x version (11.3(2) or later for the 11.3 branch)
  4. 4. Verify the upgrade was successful by confirming the DCNM web interface is accessible
  5. 5. Test critical functionality to ensure the patch did not disrupt normal operations
  6. 6. Review Cisco release notes for any additional post-upgrade configuration requirements
Caveat Review Cisco release notes - some upgrades may require database migration or reinstallation; test in staging first

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

Fix this in Data Center Network Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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