CVE intelligence and bounded remediation
CVE-2017-6662 — Cisco Evolved Programmable Network Manager security vulnerability
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.
- Severity
- High
- CVSS
- 8 (3.0)
- Published
- 2017-06-26
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-20, CWE-611
Affected products
- cisco / evolved_programmable_network_manager / 1.2.0
- cisco / evolved_programmable_network_manager / 1.2.1.3
- cisco / evolved_programmable_network_manager / 1.2.200
- cisco / evolved_programmable_network_manager / 1.2.300
- cisco / evolved_programmable_network_manager / 1.2.400
- cisco / evolved_programmable_network_manager / 1.2.500
Matched remediation archetype
XML external entity and unsafe XML processing
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Inventory XML parsers used by APIs, file imports, office or image formats, identity protocols, feeds, and background jobs.
- Determine whether document type declarations, external entities, XInclude, schemas, or network resolvers are enabled.
- Map parser filesystem and network access and the sensitivity of documents it processes.
Remediate safely
- Configure each parser to reject document type declarations and disable external entity, XInclude, and network resolution features.
- Prefer a data format or hardened parser that does not support external resolution, and apply input size and depth limits.
- Update affected XML libraries and centralize secure parser construction so callers cannot silently override it.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.