dbcve.org
Prime InfrastructureApplication · Cisco

CVE-2016-1408

HIGH · 8.8 CVSS v3.0 Published 2016-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Cisco Prime Infrastructure 1.2 through 3.1 and Evolved Programmable Network Manager (EPNM) 1.2 and 2.0 allow remote authenticated users to execute arbitrary commands or upload files via a crafted HTTP request, aka Bug ID CSCuz01488.

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

Authenticated command injection and arbitrary file upload vulnerability in Cisco Prime Infrastructure (versions 1.2-3.1) and EPNM (1.2, 2.0). Remote attackers with valid credentials can send crafted HTTP requests to execute OS commands or upload malicious files on the affected system.

MitigationApply vendor patches for CSCuz01488; if unavailable, severely restrict network access to Cisco Prime/EPNM management interfaces and enforce strong authentication policies.

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 InfrastructureApplication
Affected:= 1.2= 1.2.0.103= 1.2.1= 1.3= 1.3.0.20= 1.4= 1.4.0.45= 1.4.1= 1.4.2= 2.0= 2.1.0= 2.2
Evolved Programmable Network ManagerApplication
Affected:= 1.2.0= 1.2.1.3= 1.2.200= 1.2.300= 1.2.400= 1.2.500

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/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 management product
    Locate and inspect the Cisco Prime Infrastructure or EPNM installation. Check for /opt/CSCOlumos or similar Cisco product directories, or query the system for installed packages matching 'prime' or 'EPNM'. Confirm whether the system runs Cisco Prime Infrastructure or Evolved Programmable Network Manager.
    Affected if The product is Cisco Prime Infrastructure or EPNM and the specific version matches or falls within the affected ranges.
  2. Determine installed version number
    For Cisco Prime Infrastructure, check the version via the web UI (typically at /webacs/about.htm) or by running 'show version' on the CLI if accessible. For EPNM, check /opt/CSCOlumos/bin/inventory -v or the about page on the web interface.
    Affected if The version matches: Cisco PI versions 1.2, 1.2.0.103, 1.2.1, 1.3, 1.3.0.20, 1.4, 1.4.0.45, 1.4.1, 1.4.2, 2.0, 2.1.0, 2.2 (or any version up to 3.1) or EPNM versions 1.2.0, 1.2.1.3, 1.2.200, 1.2.300, 1.2.400, 1.2.500.
  3. Verify web management interface accessibility
    Determine if the Cisco Prime/EPNM web interface (typically ports 80/443) is reachable from network segments other than trusted management networks. Check firewall rules, ACLs, or reverse proxy configurations that expose the management URL.
    Affected if The web management interface is accessible from untrusted networks or the internet, increasing exposure to authenticated attackers.
  4. Assess authentication posture
    Review whether default administrative accounts (admin, root) retain their factory-default passwords, and check if account lockout policies or MFA are enforced for the Prime/EPNM login portal.
    Affected if Weak or default credentials are in use, making the command injection and file upload exploitation feasible for attackers who obtain valid credentials.

You are affected if Cisco Prime Infrastructure or EPNM is installed and the version falls within the listed affected ranges AND the management interface is network-accessible to potential attackers.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for CSCuz01488; if unavailable, severely restrict network access to Cisco Prime/EPNM management interfaces and enforce strong authentication policies.

Fix this in Prime Infrastructure Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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