Data Center Network ManagerApplication · Cisco

CVE-2020-3114

HIGH · 8.8 CVSS v3.1 Published 2020-02-19
Fix available
A fix is available. Upgrade to 11.3 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 web-based management interface of Cisco Data Center Network Manager (DCNM) could allow an unauthenticated, remote attacker to conduct a cross-site request forgery (CSRF) attack on an affected system. The vulnerability is due to insufficient CSRF protections for the web-based management interface on an affected device. An attacker could exploit this vulnerability by persuading a user of the interface to follow a malicious link while having an active session on an affected device. A successful exploit could allow the attacker to perform arbitrary actions with the privilege level of the targeted user.

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 confidence

Cisco Data Center Network Manager (DCNM) web interface lacks proper CSRF token validation, allowing attackers to craft malicious links that force authenticated users to perform unintended actions. The vulnerability is exploitable remotely without authentication by tricking users with active sessions into clicking malicious URLs.

MitigationApply Cisco's vendor patches for CVE-2020-3114. Until patched, users should avoid clicking untrusted links and should log out of DCNM sessions when not in use.

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.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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Confirm DCNM is installed
    Check if Cisco Data Center Network Manager is running in your environment by accessing the web interface URL (typically https://<dcnm-host>) or checking for the dcnm service process on the host.
    Affected if DCNM is accessible and running in your environment.
  2. Identify installed DCNM version
    Log into the DCNM web interface and navigate to the About or Administration > System > Inventory page to view the installed version number. Alternatively, check the version via CLI if you have direct access to the DCNM server.
    Affected if The installed version is displayed as anything lower than 11.3(1).
  3. Verify web interface is enabled
    Confirm the DCNM web interface (HTTP/HTTPS) is enabled and accessible by attempting to reach the login page.
    Affected if The web interface is accessible and accepts user authentication sessions.
  4. Check for active user sessions
    Review active authenticated sessions on DCNM by checking the Sessions or Active Users panel in the web interface Administration section.
    Affected if Users have active authenticated sessions logged into DCNM.

You are affected if DCNM is running with a web interface version lower than 11.3(1) and users have active authenticated sessions, as the CSRF protection gap can be exploited via malicious links.

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.

From vendor data
Upgrade available Upgrade to 11.3 or later
Fixed in 11.3
Interim mitigation

Apply Cisco's vendor patches for CVE-2020-3114. Until patched, users should avoid clicking untrusted links and should log out of DCNM sessions when not in use.

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 the upgrade done

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-3114 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-3114 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