CVE-2013-5487 cisco prime data center network manager
cisco prime data center network manager: no CVSS score yet. EPSS 2.1% estimated probability of exploitation activity in the next 30 days.
On this page
DCNM-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.
- EPSS
- 2.1% (unchanged from 2.1% a week ago; 2.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 82nd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Fix and patched versions
- Vendor advisory: http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20130918-dcnm
Ask an AI about this CVE
Show the prompt
Explain CVE-2013-5487 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2013-5487?via=ask-ai-copy and https://cve.bz/cve/CVE-2013-5487?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2013-5487 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| cisco:prime_data_center_network_manager | through 6.1\(1b\) |
| cisco:prime_data_center_network_manager | 5.2(2e) |
| cisco:prime_data_center_network_manager | 6.1(1a) |
| cisco:prime_data_center_network_manager | 4.1(2) |
| cisco:prime_data_center_network_manager | 4.1(3) |
| cisco:prime_data_center_network_manager | 4.1(4) |
| cisco:prime_data_center_network_manager | 4.1(5) |
| cisco:prime_data_center_network_manager | 4.2(1) |
| cisco:prime_data_center_network_manager | 4.2(3) |
| cisco:prime_data_center_network_manager | 5.0(2) |
| cisco:prime_data_center_network_manager | 5.0(3) |
| cisco:prime_data_center_network_manager | 5.1(1) |
| cisco:prime_data_center_network_manager | 5.1(2) |
| cisco:prime_data_center_network_manager | 5.1(3u) |
| cisco:prime_data_center_network_manager | 5.2(2) |
| cisco:prime_data_center_network_manager | 5.2(2a) |
| cisco:prime_data_center_network_manager | 5.2(2b) |
| cisco:prime_data_center_network_manager | 5.2(2c) |
| cisco:prime_data_center_network_manager | 6.1(1b) |
Attack patterns (CAPEC)
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).