dbcve.org
Evolved Programmable Network ManagerApplication · Cisco

CVE-2016-1290

HIGH · 8.1 CVSS v3.0 Published 2016-04-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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 web API in Cisco Prime Infrastructure 1.2.0 through 2.2(2) and Cisco Evolved Programmable Network Manager (EPNM) 1.2 allows remote authenticated users to bypass intended RBAC restrictions and gain privileges via an HTTP request that is inconsistent with a pattern filter, aka Bug ID CSCuy10227.

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 web API in Cisco Prime Infrastructure (versions 1.2.0 through 2.2(2)) and Cisco Evolved Programmable Network Manager (EPNM) 1.2 contains an RBAC bypass vulnerability. Authenticated users can craft HTTP requests that circumvent pattern filter restrictions to elevate privileges beyond their assigned role. This is a privilege escalation flaw in the API's access control logic.

MitigationApply the vendor-supplied patches from Cisco for this vulnerability. If patches are unavailable, restrict API access to trusted users and implement additional monitoring for anomalous API requests that may indicate privilege escalation attempts.

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
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
OpensolarisOperating system
Affected:= snv_124

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
None

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

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 network management product
    Check for presence of Cisco Prime Infrastructure or Cisco Evolved Programmable Network Manager (EPNM) on the system. Look for installation directories, running services, or check the product-specific management interfaces.
    Affected if Either Cisco Prime Infrastructure or Cisco EPNM is installed
  2. Check product version
    Access the product's admin interface or use command line tools to query the installed version. For Prime Infrastructure, typically found in the About or Diagnostics section of the web UI, or via 'show version' command in CLI.
    Affected if Version matches: Cisco EPNM = 1.2.0 OR Cisco Prime Infrastructure = 1.2 through 2.2(2) inclusive (specifically 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)
  3. Verify web API is accessible
    Confirm the product's web API endpoint is reachable. This is typically exposed on port 443 or 8080. Test connectivity to the API URLs such as /webacs/api/v1 or similar API endpoints.
    Affected if Web API is exposed and accessible from network
  4. Confirm authentication is required for API access
    Test API endpoints without valid credentials to confirm authentication is enforced. Check if the API allows unauthenticated requests or if proper auth is required.
    Affected if API accepts requests without proper authentication or allows privilege escalation through crafted requests
  5. Review API access logs for anomalous requests
    Examine API access logs for patterns indicating privilege escalation attempts, such as unusual role modifications or access to administrative functions by non-admin users.
    Affected if Logs show API requests that circumvent RBAC restrictions or elevate privileges beyond assigned roles

Environment is affected if Cisco Prime Infrastructure (versions 1.2 through 2.2(2)) or Cisco EPNM 1.2.0 is installed with the web API accessible and no additional access controls preventing the RBAC bypass.

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 the vendor-supplied patches from Cisco for this vulnerability. If patches are unavailable, restrict API access to trusted users and implement additional monitoring for anomalous API requests that may indicate privilege escalation attempts.

Fix this in Evolved Programmable Network Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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