dbcve.org
Prime Data Center Network ManagerApplication · Cisco

CVE-2013-5486

HIGH · 10.0 CVSS v2.0 Published 2013-09-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Public exploit Remotely reachable No privileges Zero-click

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
Directory traversal vulnerability in processImageSave.jsp in DCNM-SAN Server in Cisco Prime Data Center Network Manager (DCNM) before 6.2(1) allows remote attackers to write arbitrary files via the chartid parameter, aka Bug IDs CSCue77035 and CSCue77036. NOTE: this can be leveraged to execute arbitrary commands by using the JBoss autodeploy functionality.

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

Directory traversal vulnerability in processImageSave.jsp in Cisco Prime Data Center Network Manager (DCNM) allows remote attackers to write arbitrary files via the chartid parameter. The lack of proper input validation permits path traversal, enabling file write operations outside the intended directory. This can be chained with JBoss autodeploy functionality to achieve remote code execution.

MitigationUpgrade to DCNM version 6.2(1) or later to obtain the vendor patch. If immediate patching is not feasible, restrict network access to DCNM management interfaces using firewall rules or network segmentation to reduce attack surface.

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
Affected:= 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.1\(2\)= 5.1\(3u\)= 5.2\(2\)

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
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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
    Look for the DCNM installation directory. Common paths include /opt/cisco/dcm on Linux or C:\Program Files\Cisco\DCNM on Windows. Check running processes for 'dcm' or 'jboss' related to DCNM.
    Affected if DCNM software is found on the system
  2. Determine the installed DCNM version
    Check the version file in the installation directory, typically found in a version.properties or similar file, or access the DCNM web interface login page which often displays the version.
    Affected if Installed version matches any of: 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.1(2), 5.1(3u), 5.2(2)
  3. Verify the vulnerable JSP file exists
    Locate the processImageSave.jsp file in the web application directory. This is typically found under the JBoss server deploy directory, often in a path containing 'webapp' or 'dcnm' and the jsp filename processImageSave.jsp.
    Affected if The file processImageSave.jsp exists in the DCNM web application path
  4. Confirm web management interface accessibility
    Test network accessibility to the DCNM web interface ports (default HTTPS on port 443 or 8443). Attempt a local curl or browser request to the login page.
    Affected if The DCNM web interface is reachable over the network on typical management ports
  5. Check JBoss autodeploy feature status
    Inspect the JBoss configuration for the autodeploy directory feature, typically the 'deploy' or 'autodeploy' folder under the JBoss server configuration used by DCNM.
    Affected if JBoss autodeploy functionality is enabled and writable

The system is affected if Cisco DCNM versions 4.1(2) through 5.2(2) are installed, the processImageSave.jsp file exists, and the web management interface is network-accessible, as this combination enables the path traversal vulnerability to be exploited.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to DCNM version 6.2(1) or later to obtain the vendor patch. If immediate patching is not feasible, restrict network access to DCNM management interfaces using firewall rules or network segmentation to reduce attack surface.

Recommended fix High confidence

Cisco Prime Data Center Network Manager 6.2(1) or later

  1. 1. Identify the current installed version of Cisco Prime Data Center Network Manager using the command line interface or web interface
  2. 2. Create a complete backup of the DCNM configuration and database
  3. 3. Download the DCNM version 6.2(1) or later from the Cisco Software Download Center (tools.cisco.com)
  4. 4. Review Cisco DCNM 6.2(1) release notes for upgrade prerequisites and compatibility requirements
  5. 5. Stop all DCNM services before performing the upgrade
  6. 6. Run the DCNM installer to upgrade from 4.1.x to 6.2(1) or later following the official Cisco upgrade guide
  7. 7. After upgrade, verify all DCNM services start successfully
  8. 8. Validate that the processImageSave.jsp vulnerability is no longer accessible and chartid parameter is properly sanitized
Caveat Major version upgrade from 4.x to 6.x may introduce significant interface changes, require reconfiguration of certain features, and may have modified system requirements - review release notes thoroughly before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Prime Data Center Network Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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