# CVE-2022-20657: Cisco Prime Infrastructure and Cisco Evolved Programmable Network Manager Cross-Site Scripting Vulnerability

> Unauthenticated remote attackers can execute arbitrary script code or access sensitive browser-based information via crafted links in Cisco Prime Infrastructure and EPNM.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Nov 2024
- **Updated:** 15 Nov 2024
- **Also known as:** GHSA-gg8c-67xr-mxhv

## What is CVE-2022-20657?

CVE-2022-20657 is a medium-severity cross-site scripting vulnerability in Cisco Evolved Programmable Network Manager, published on 15 Nov 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the web-based management interface of Cisco PI and Cisco EPNM could allow an unauthenticated, remote attacker to conduct an XSS attack against a user of the interface of an affected device.
This vulnerability exists because the web-based management interface does not properly validate user-supplied input. An attacker could exploit this vulnerability by persuading a user of an affected interface to click a crafted link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected interface or access sensitive, browser-based information.Cisco has released software updates that address these vulnerabilities. There are no workarounds that address these vulnerabilities.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2022-20657?

It affects 2 products.


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

## How do I fix CVE-2022-20657?

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

## Is CVE-2022-20657 being exploited?

There is no known exploitation of CVE-2022-20657 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-2022-20657 and fix it if it is affected.

What it is: CVE-2022-20657 is a medium-severity cross-site scripting vulnerability in Cisco Evolved Programmable Network Manager, published on 15 Nov 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-20657 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-2022-20657/ (Markdown: https://insights.sbomify.com/CVE-2022-20657/index.md)
```

## Sources

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

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