Prime Data Center Network ManagerApplication · Cisco
CVE-2015-0666
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 · uneditedDirectory traversal vulnerability in the fmserver servlet in Cisco Prime Data Center Network Manager (DCNM) before 7.1(1) allows remote attackers to read arbitrary files via a crafted pathname, aka Bug ID CSCus00241.
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 confidenceDirectory traversal vulnerability in the fmserver servlet of Cisco Prime Data Center Network Manager allows remote attackers to read arbitrary files by using '..' sequences in crafted pathnames. This occurs due to insufficient input validation in the servlet, enabling attackers to escape the intended directory and access sensitive system files.
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
Prime Data Center Network ManagerApplication
<= 7.0\(2\)= 6.3\(1\)= 6.3\(2\)= 7.0\(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
- 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 if Cisco Prime DCNM is installed and runningCheck for running processes named 'dcm' or 'dcnm' or look for Cisco Prime DCNM installation directories (typically under /opt or C:\Program Files\Cisco\). On Linux, run 'ps -ef | grep -i dcm' or check service status. On Windows, check Services console for 'Cisco Prime DCNM' service.Affected if The product is installed and running
-
Determine the installed versionCheck the version file or about page. On Linux, common locations: /opt/CSCOdcnm/bin/version.txt or /opt/dcnm/version.properties. On Windows, check C:\Program Files\Cisco\Prime DCNM\version.txt or within the application UI under Help > About.Affected if Version matches 6.3(1), 6.3(2), 7.0(1), or any version <= 7.0(2)
-
Verify fmserver servlet is accessibleCheck if the DCNM web interface is running. The fmserver servlet typically responds at paths like /fmserver/ or /fmserver/ under the DCNM web port (default 8080 for HTTP, 8443 for HTTPS). Try accessing http://<server>:8080/fmserver/ or https://<server>:8443/fmserver/ and verify a response is received.Affected if The servlet returns an HTTP response (200, 404, or any) indicating it is reachable
-
Confirm network exposure of DCNM management interfaceReview firewall rules or network ACLs to determine if the DCNM web port (8080/8443) is exposed to untrusted networks. On the DCNM server, run 'netstat -an | grep -E '8080|8443'' to confirm listening addresses. Check if binding is to 0.0.0.0 (all interfaces) vs 127.0.0.1 (localhost only).Affected if The management interface port is listening on 0.0.0.0 or an external-facing interface
A user is affected if Cisco Prime DCNM version 6.3(1), 6.3(2), 7.0(1), or <= 7.0(2) is running with the fmserver servlet exposed to the 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.
dbcve · scopedUpgrade Cisco Prime DCNM to version 7.1(1) or later. Until patched, restrict network access to the DCNM management interface to trusted internal networks only.
Cisco Prime Data Center Network Manager 7.1(1) or later
- 1. Back up the current Cisco Prime DCNM configuration and database according to Cisco backup procedures
- 2. Download Cisco Prime Data Center Network Manager version 7.1(1) or later from the Cisco Download Software page (tools.cisco.com) using valid Cisco credentials
- 3. Review Cisco Prime DCNM installation and upgrade guides for the target version
- 4. Stop the DCNM services on the affected server
- 5. Install the upgraded DCNM 7.1(1) or later version following the official upgrade instructions
- 6. Restore the configuration from the backup after installation
- 7. Start DCNM services and verify the fmserver servlet is functioning correctly
- 8. Confirm the vulnerability is remediated by verifying that directory traversal attempts are blocked
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Prime Data Center Network Manager
Exploited in the wild — priority engagement
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0666 — 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-2015-0666 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