dbcve.org
Prime Data Center Network ManagerApplication · Cisco

CVE-2018-0258

CRITICAL · 9.8 CVSS v3.0 Published 2018-05-02
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
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
A vulnerability in the Cisco Prime File Upload servlet affecting multiple Cisco products could allow a remote attacker to upload arbitrary files to any directory of a vulnerable device (aka Path Traversal) and execute those files. This vulnerability affects the following products: Cisco Prime Data Center Network Manager (DCNM) Version 10.0 and later, and Cisco Prime Infrastructure (PI) All versions. Cisco Bug IDs: CSCvf32411, CSCvf81727.

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

The vulnerability exists in the Cisco Prime File Upload servlet, allowing remote attackers to perform path traversal attacks and upload arbitrary files to any directory on the affected device, then execute those files. This affects Cisco Prime Data Center Network Manager (DCNM) versions 10.0+ and all versions of Cisco Prime Infrastructure.

MitigationApply vendor-provided patches for CSCvf32411 and CSCvf81727, or if patches are unavailable, restrict network access to the file upload servlet and consider disabling the affected service until remediation is possible.

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:= 10.0\(1\)= 10.2\(1\)
Prime InfrastructureApplication
Affected:= 3.3\(0.0\)

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 installed Cisco Prime product
    Determine if Cisco Prime Data Center Network Manager (DCNM) or Cisco Prime Infrastructure is deployed in the environment. Check for running processes or installed applications matching these product names.
    Affected if Either Cisco Prime DCNM or Cisco Prime Infrastructure is installed
  2. Check Cisco Prime DCNM version
    Locate the installed version of Cisco Prime DCNM. Consult the application's about page, installation directory, or version registry entry. Compare the version to the affected releases 10.0(1) and 10.2(1).
    Affected if The installed version is 10.0(1) or 10.2(1)
  3. Check Cisco Prime Infrastructure version
    Locate the installed version of Cisco Prime Infrastructure. Consult the application's about page, installation directory, or version registry entry. Compare the version to the affected release 3.3(0.0).
    Affected if The installed version is 3.3(0.0)
  4. Verify file upload servlet exposure
    Identify if the Cisco Prime File Upload servlet (typically accessible via web interface) is exposed to network access. Check firewall rules and access control lists for inbound access to the application's upload endpoints.
    Affected if The file upload servlet is accessible from untrusted network segments or the internet

A user is affected if they have Cisco Prime DCNM versions 10.0(1) or 10.2(1), or Cisco Prime Infrastructure version 3.3(0.0), with the file upload servlet exposed to network access.

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

Apply vendor-provided patches for CSCvf32411 and CSCvf81727, or if patches are unavailable, restrict network access to the file upload servlet and consider disabling the affected service until remediation is possible.

Recommended fix Moderate confidence

DCNM 10.3(1) or later; PI 3.4 or later (or apply respective security patches)

  1. 1. Identify the exact Cisco Prime product and version running using 'show version' or the web interface
  2. 2. For Cisco Prime Data Center Network Manager (DCNM): Upgrade to DCNM version 10.3(1) or later which contains the fix for CSCvf32411
  3. 3. For Cisco Prime Infrastructure (PI): Apply the applicable security patch for CSCvf81727 or upgrade to PI version 3.4 or later
  4. 4. After upgrade, verify the File Upload servlet is no longer accessible without authentication
  5. 5. Review Cisco PSIRT advisory for this CVE for complete patch documentation
Caveat Review Cisco release notes for upgrade prerequisites and compatibility requirements before proceeding

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-2018-0258 — 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-2018-0258 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