dbcve.org
Data Center Network ManagerApplication · Cisco

CVE-2017-12344

MEDIUM · 6.1 CVSS v3.0 Published 2017-11-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Multiple vulnerabilities in Cisco Data Center Network Manager (DCNM) Software could allow a remote attacker to inject arbitrary values into DCNM configuration parameters, redirect a user to a malicious website, inject malicious content into a DCNM client interface, or conduct a cross-site scripting (XSS) attack against a user of the affected software. Cisco Bug IDs: CSCvf40477, CSCvf63150, CSCvf68218, CSCvf68235, CSCvf68247.

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

Multiple web-based vulnerabilities in Cisco Data Center Network Manager allow remote unauthenticated attackers to inject arbitrary values into configuration parameters, redirect users to malicious sites, inject malicious content into the client interface, and conduct cross-site scripting (XSS) attacks against users. These are client-side injection flaws affecting the DCNM web interface.

MitigationApply Cisco security patches for the identified bug IDs (CSCvf40477, CSCvf63150, CSCvf68218, CSCvf68235, CSCvf68247) or upgrade to a patched DCNM version. As a compensating control, restrict network access to DCNM management interfaces and implement WAF rules for XSS and injection prevention.

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:= 10.2\(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.0/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 DCNM installation version
    Access the DCNM web interface and navigate to Help > About, or run 'dcnm-installer -v' or 'show version' via the CLI to determine the installed Cisco Data Center Network Manager version.
    Affected if The installed version is exactly 10.2(1)
  2. Confirm web interface accessibility
    Verify whether the DCNM web management interface (typically ports 80, 443, or 8080) is reachable from network segments. Check firewall rules and access control lists governing DCNM management ports.
    Affected if The DCNM web interface is exposed to untrusted networks or the internet
  3. Examine web server logs for injection attempts
    Review DCNM web server logs (typically located in /opt/dcnm/glassfish/domains/domain1/logs or similar paths under the DCNM installation directory) for patterns matching XSS payloads, arbitrary parameter injection, or suspicious redirect patterns.
    Affected if Logs contain unauthenticated XSS attempts, parameter injection strings, or anomalous redirect patterns targeting the DCNM web interface
  4. Inspect browser for malicious content injection
    Use a browser developer tool to examine the DCNM web interface source code and cookies for unexpected scripts, iframes, or modified content that may indicate past XSS exploitation.
    Affected if Unexpected JavaScript tags, iframes, or modified DOM elements are present in the DCNM web interface

A user is affected if their DCNM installation is version 10.2(1) and the web interface is accessible, as this version contains the client-side injection vulnerabilities described in the CVE.

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

Apply Cisco security patches for the identified bug IDs (CSCvf40477, CSCvf63150, CSCvf68218, CSCvf68235, CSCvf68247) or upgrade to a patched DCNM version. As a compensating control, restrict network access to DCNM management interfaces and implement WAF rules for XSS and injection prevention.

Fix this in Data Center Network Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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