dbcve.org
Evolved Programmable Network ManagerApplication · Cisco

CVE-2017-6662

HIGH · 8.0 CVSS v3.0 Published 2017-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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 web-based user interface of Cisco Prime Infrastructure (PI) and Evolved Programmable Network Manager (EPNM) could allow an authenticated, remote attacker read and write access to information stored in the affected system as well as perform remote code execution. The attacker must have valid user credentials. The vulnerability is due to improper handling of XML External Entity (XXE) entries when parsing an XML file. An attacker could exploit this vulnerability by convincing the administrator of an affected system to import a crafted XML file with malicious entries which could allow the attacker to read and write files and execute remote code within the application, aka XML Injection. Cisco Prime Infrastructure software releases 1.1 through 3.1.6 are vulnerable. Cisco EPNM software releases 1.2, 2.0, and 2.1 are vulnerable. Cisco Bug IDs: CSCvc23894 CSCvc49561.

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

XML External Entity (XXE) injection vulnerability in Cisco Prime Infrastructure and Evolved Programmable Network Manager allows authenticated attackers to read/write files on the underlying system and achieve remote code execution by importing specially crafted XML files through the web interface.

MitigationApply Cisco security updates to upgrade beyond vulnerable versions (PI 1.1-3.1.6, EPNM 1.2/2.0/2.1); until patched, disable or restrict XML file import functionality and validate all XML input.

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= 1.2.400= 1.2.500= 2.0\(4.0.45d\)= 2.0.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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/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 and version
    Access the web interface and navigate to the About or Version page (typically /webui/about.html or similar), or use the CLI command 'show version' if you have console access
    Affected if The displayed version matches one of the affected versions: PI 1.2 through 2.2, or EPNM 1.2.0 through 2.0(4.0.45d) or 2.0.0
  2. Check for XML import functionality access
    Log into the web interface and look for XML file import options in the GUI, typically under device/template import features or configuration management sections
    Affected if The XML import feature is present and accessible to authenticated users
  3. Verify XML parser configuration
    If you have administrative access, check the application configuration or XML parser settings for whether external entity processing is enabled (often found in application server config files or XML-related settings)
    Affected if The XML parser is configured to allow external entity processing (this would be the vulnerable state)
  4. Confirm authentication access level
    Determine if any authenticated user account (not necessarily admin) can access the XML import functionality
    Affected if Any authenticated user with access to XML import functionality exists in the system

You are affected if you are running any of the listed versions of Cisco Prime Infrastructure (1.2 through 2.2) or EPNM (1.2.0 through 2.0) and the XML file import feature via the web interface is 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 security updates to upgrade beyond vulnerable versions (PI 1.1-3.1.6, EPNM 1.2/2.0/2.1); until patched, disable or restrict XML file import functionality and validate all XML input.

Fix this in Evolved Programmable Network Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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