dbcve.org
Evolved Programmable Network ManagerApplication · Cisco

CVE-2016-1406

HIGH · 8.8 CVSS v3.0 Published 2016-05-25
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
The API web interface in Cisco Prime Infrastructure before 3.1 and Cisco Evolved Programmable Network Manager before 1.2.4 allows remote authenticated users to bypass intended RBAC restrictions and obtain sensitive information, and consequently gain privileges, via crafted JSON data, aka Bug ID CSCuy12409.

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

This is an RBAC (Role-Based Access Control) bypass vulnerability in the API web interface of Cisco Prime Infrastructure and Cisco Evolved Programmable Network Manager. Authenticated users can send crafted JSON data to bypass intended role restrictions, allowing them to access sensitive information and gain privileges beyond what their assigned role permits.

MitigationUpgrade Cisco Prime Infrastructure to version 3.1 or later, and Cisco Evolved Programmable Network Manager to version 1.2.4 or later to patch this RBAC bypass vulnerability.

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
Evolved Programmable Network ManagerApplication
Affected:= 1.2.0= 1.2.1.3= 1.2.200= 1.2.300
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

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 Cisco Prime Infrastructure version
    Access the Prime Infrastructure web interface and navigate to the Administration > Settings > Software Updates section, or use the CLI command 'show version' to retrieve the installed software version
    Affected if The installed version matches any of these: 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, or 2.2
  2. Identify Cisco Evolved Programmable Network Manager version
    Access the EPNM web interface and check the About or System Information page, or use the CLI to retrieve the installed version
    Affected if The installed version matches any of these: 1.2.0, 1.2.1.3, 1.2.200, or 1.2.300
  3. Verify API web interface is enabled
    Check the Prime Infrastructure or EPNM administrative console for API or REST API service status, typically found under Administration > Settings or Services configuration
    Affected if The API web interface service is enabled and accessible to authenticated users
  4. Review access logs for privilege escalation attempts
    Examine web server and application logs for API requests containing unusual JSON payloads or requests to resources outside the assigned role permissions
    Affected if Logs show API requests from standard users accessing administrative data or functions

You are affected if your installed version of Cisco Prime Infrastructure is 2.2 or earlier, or Cisco EPNM is 1.2.300 or earlier, and the API web interface is enabled allowing authenticated users to submit custom JSON requests.

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

Upgrade Cisco Prime Infrastructure to version 3.1 or later, and Cisco Evolved Programmable Network Manager to version 1.2.4 or later to patch this RBAC bypass vulnerability.

Fix this in Evolved Programmable Network Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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