Prime Data Center Network ManagerApplication · Cisco
CVE-2013-5487
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 · uneditedDCNM-SAN Server in Cisco Prime Data Center Network Manager (DCNM) before 6.2(1) allows remote attackers to read arbitrary files via unspecified vectors, aka Bug ID CSCue77029.
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 confidenceThe DCNM-SAN Server component in Cisco Prime Data Center Network Manager before version 6.2(1) contains a file read vulnerability allowing remote attackers to read arbitrary files on the system via unspecified vectors, likely through path traversal or improper input validation in the web interface.
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
<= 6.1\(1b\)= 5.2\(2e\)= 6.1\(1a\)= 4.1\(2\)= 4.1\(3\)= 4.1\(4\)= 4.1\(5\)= 4.2\(1\)= 4.2\(3\)= 5.0\(2\)= 5.0\(3\)= 5.1\(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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:C/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.
-
Confirm Cisco Prime DCNM installationLook for DCNM installation directories or check running processes for 'dcnm' or 'Data Center Network Manager' related servicesAffected if The software is not installed or no DCNM processes are found, the system is not affected
-
Identify installed DCNM versionCheck the DCNM version through the web interface login page, CLI if available, or check installation logs and version files in the DCNM installation directoryAffected if The installed version matches any of these affected versions: 4.1(2), 4.1(3), 4.1(4), 4.1(5), 4.2(1), 4.2(3), 5.0(2), 5.0(3), 5.1(1), 5.2(2e), 6.1(1a), 6.1(1b), or any version prior to 6.2(1)
-
Verify DCNM-SAN Server component is activeConfirm the DCNM-SAN Server web service is running and accessible - typically on ports 8080, 8443, or the HTTPS admin port configured during installationAffected if The DCNM-SAN Server web interface is accessible and the DCNM version is below 6.2(1)
-
Check web interface exposureDetermine if the DCNM web interface is reachable from network locations - check firewall rules, ACLs, and listening services on the hostAffected if The DCNM web interface is exposed to network access and the version is vulnerable
A system is affected if Cisco Prime Data Center Network Manager is installed with DCNM-SAN Server enabled and the installed version is any release prior to version 6.2(1).
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.
From vendor dataUpgrade to DCNM version 6.2(1) or later to obtain the patch for this vulnerability.
Fix this in Prime Data Center Network Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-5487 — 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-2013-5487 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