# CVE-2017-6662: XML external entity in Cisco Prime Infrastructure and Evolved Programmable Network Manager

> Authenticated attackers can achieve remote code execution and file access by tricking administrators into importing malicious XML files in Cisco Prime Infrastructure and EPNM.

- **Severity:** High 8.0 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9h75-c39j-rxjx

## What is CVE-2017-6662?

CVE-2017-6662 is a high-severity vulnerability in Cisco Evolved Programmable Network Manager, published on 26 Jun 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2017-6662?

It affects 2 products.


Products: Cisco Evolved Programmable Network Manager, Cisco Prime Infrastructure.

## How do I fix CVE-2017-6662?

No fix has been published for CVE-2017-6662 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-6662 being exploited?

There is no known exploitation of CVE-2017-6662 in the wild and no public exploit code.

## Other vulnerabilities in Cisco Evolved Programmable Network Manager

- [CVE-2016-1289](https://insights.sbomify.com/CVE-2016-1289/): Code injection in n/a (critical 9.8)
- [CVE-2016-1291](https://insights.sbomify.com/CVE-2016-1291/): Deserialization in n/a (critical 9.8)
- [CVE-2021-1487](https://insights.sbomify.com/CVE-2021-1487/): Cisco Prime Infrastructure and Cisco Evolved Programmable Network Manager Command Injection Vulnerability (high 8.8)
- [CVE-2019-1821](https://insights.sbomify.com/CVE-2019-1821/): Cisco Prime Infrastructure and Evolved Programmable Network Manager Remote Code Execution Vulnerabilities (high 8.8)
- [CVE-2019-1822](https://insights.sbomify.com/CVE-2019-1822/): Cisco Prime Infrastructure and Evolved Programmable Network Manager Remote Code Execution Vulnerabilities (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6662 and fix it if it is affected.

What it is: CVE-2017-6662 is a high-severity vulnerability in Cisco Evolved Programmable Network Manager, published on 26 Jun 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-6662 in the wild and no public exploit code.

Affected product: Cisco Evolved Programmable Network Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-6662/ (Markdown: https://insights.sbomify.com/CVE-2017-6662/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-6662
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-6662
- OSV: https://osv.dev/vulnerability/CVE-2017-6662

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-6662/
Summaries are generated and may contain mistakes; the official description above is the record.