Data Center Network ManagerApplication · Cisco

CVE-2020-3460

MEDIUM · 6.1 CVSS v3.1 Published 2020-07-31
Fix available
A fix is available. Upgrade to 11.4 or later.
See remediation →
68/100
Remediation priority · Elevated
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 scripting (XSS) attack against a user of the interface. The vulnerability exists because the web-based management interface does not properly validate user-supplied input. An attacker could exploit this vulnerability by intercepting a request from a user and injecting malicious data into an HTTP header. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected interface or access sensitive browser-based information.

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

A reflected cross-site scripting (XSS) vulnerability in Cisco Data Center Network Manager (DCNM) allows unauthenticated remote attackers to inject malicious script into HTTP headers. The web-based management interface fails to properly validate user-supplied input, causing the injected payload to be reflected back to users, enabling arbitrary code execution in the context of the affected interface or theft of sensitive browser-based information.

MitigationApply the vendor patch from Cisco for CVE-2020-3460. If immediate patching is not feasible, restrict network access to the DCNM web management interface to trusted sources only.

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.4\(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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

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

  1. Identify if Cisco DCNM is installed
    Check for DCNM installation directories (e.g., /opt/dcnm, /usr/local/cisco/dcnm) or look for the 'dcnm' service using 'systemctl list-units --type=service | grep -i dcnm' or 'ps aux | grep -i dcnm'
    Affected if DCNM software is present on the system
  2. Determine the installed DCNM version
    Check the DCNM version file if it exists (commonly found in the installation directory as 'version' or 'dcnm_version'), or access the web interface and look for version information in the login page or About section, or run 'dcnm歌唱 -v' if the command-line tool is available
    Affected if The installed version is lower than 11.4(1)
  3. Verify the DCNM web management interface is accessible
    Check if the web service is running by inspecting listening ports (e.g., 'netstat -tulpn | grep -E "(80|443|8080|8443)"' or 'ss -tulpn'), and confirm DCNM web interface responds to HTTP/HTTPS requests
    Affected if The web management interface is exposed and responsive

A system is affected if Cisco DCNM is installed with a version lower than 11.4(1) and the web-based management interface is accessible, as the reflected XSS vulnerability exists in that configuration.

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.4 or later
Fixed in 11.4
Interim mitigation

Apply the vendor patch from Cisco for CVE-2020-3460. If immediate patching is not feasible, restrict network access to the DCNM web management interface to trusted sources only.

Fix this in Data Center Network Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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