dbcve.org
Evolved Programmable Network ManagerApplication · Cisco

CVE-2016-6443

HIGH · 8.8 CVSS v3.0 Published 2016-10-27
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
A vulnerability in the Cisco Prime Infrastructure and Evolved Programmable Network Manager SQL database interface could allow an authenticated, remote attacker to impact system confidentiality by executing a subset of arbitrary SQL queries that can cause product instability. More Information: CSCva27038, CSCva28335. Known Affected Releases: 3.1(0.128), 1.2(400), 2.0(1.0.34A).

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

SQL injection vulnerability in the SQL database interface of Cisco Prime Infrastructure and Evolved Programmable Network Manager allows an authenticated remote attacker to execute arbitrary SQL queries, impacting confidentiality and potentially causing product instability.

MitigationApply Cisco patches for the affected releases (3.1(0.128), 1.2(400), 2.0(1.0.34A)) and implement strict least-privilege database accounts to limit impact of SQL injection.

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= 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

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 product
    Access the admin console or use CLI to determine if Cisco Prime Infrastructure or Cisco Evolved Programmable Network Manager is installed. Check the product name displayed in the web interface or the system banner via SSH.
    Affected if The system is running either Prime Infrastructure or Evolved Programmable Network Manager.
  2. Determine product version
    Locate the version number in the product web interface (typically under Help > About or System > Software) or via CLI command 'show version' or 'show inventory'. Compare against the affected version list.
    Affected if The installed version matches exactly: EPNM 1.2 or 2.0; Prime Infrastructure 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.
  3. Verify SQL database interface is accessible
    Check if the SQL database interface feature is enabled and accessible via network. This is typically accessible through the web interface under Administration > Database or similar database management sections.
    Affected if The SQL database interface is accessible to authenticated users on the network.
  4. Confirm network accessibility of management interface
    Verify that the web-based management interface is exposed to network users. Check ACLs, firewall rules, or VPN configurations that control access to the product web portal.
    Affected if The management interface is reachable from network segments accessible to authenticated attackers.

You are affected if you are running Cisco Prime Infrastructure or Evolved Programmable Network Manager with any of the listed version numbers and the SQL database interface is network-accessible to authenticated users.

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 Cisco patches for the affected releases (3.1(0.128), 1.2(400), 2.0(1.0.34A)) and implement strict least-privilege database accounts to limit impact of SQL injection.

Fix this in Evolved Programmable Network Manager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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