# CVE-2019-1821: Cisco Prime Infrastructure and Evolved Programmable Network Manager Remote Code Execution Vulnerabilities

> Authenticated attackers can upload malicious files to Cisco Prime Infrastructure or EPN Manager to execute code with root privileges.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 16 May 2019
- **Updated:** 20 Nov 2024
- **Also known as:** GHSA-4mx6-fjqc-4rhr

## What is CVE-2019-1821?

CVE-2019-1821 is a high-severity vulnerability in Cisco Evolved Programmable Network Manager, published on 16 May 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in the web-based management interface of Cisco Prime Infrastructure (PI) and Cisco Evolved Programmable Network (EPN) Manager could allow an authenticated, remote attacker to execute code with root-level privileges on the underlying operating system. This vulnerability exist because the software improperly validates user-supplied input. An attacker could exploit this vulnerability by uploading a malicious file to the administrative web interface. A successful exploit could allow the attacker to execute code with root-level privileges on the underlying operating system.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2019-1821?

It affects 3 products.


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

## How do I fix CVE-2019-1821?

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

## Is CVE-2019-1821 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-1821 exists.

Public exploit code:

- Cisco Exploit  (CVE-2019-1821 Cisco Prime Infrastructure Remote Code Execution/CVE-2019-1653/Cisco SNMP RCE/Dump Cisco RV320 Password) (github_poc): https://github.com/k8gege/CiscoExploit
- Cisco Prime Infrastructure Health Monitor TarArchive Directory Traversal Vulnerability (metasploit)
- Cisco Prime Infrastructure Health Monitor HA TarArchive - Directory Traversal / Remote Code Execution (exploitdb)
- Cisco Prime Infrastructure Health Monitor - TarArchive Directory Traversal (Metasploit) (exploitdb)
- Cisco Prime Infrastructure and Cisco Evolved Programmable Network Manager - Remote Code Execution (nuclei): http/cves/2019/CVE-2019-1821.yaml

## 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-1822](https://insights.sbomify.com/CVE-2019-1822/): Cisco Prime Infrastructure and Evolved Programmable Network Manager Remote Code Execution Vulnerabilities (high 8.8)
- [CVE-2019-1823](https://insights.sbomify.com/CVE-2019-1823/): 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-2019-1821 and fix it if it is affected.

What it is: CVE-2019-1821 is a high-severity vulnerability in Cisco Evolved Programmable Network Manager, published on 16 May 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-1821 exists.

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-2019-1821/ (Markdown: https://insights.sbomify.com/CVE-2019-1821/index.md)
```

## Sources

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

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