CVE-2019-1820 json
Cisco Prime Infrastructure and Evolved Programmable Network Manager Path Traversal Vulnerability
published 2019-05-16 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-10377
- cvss
- 6.5
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 13.6%
- EPSS 13.6% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
A vulnerability in the web-based management interface of Cisco Prime Infrastructure and Cisco Evolved Programmable Network (EPN) Manager software could allow an authenticated, remote attacker to download and view files within the application that should be restricted. This vulnerability is due to improper sanitization of user-supplied input in HTTP request parameters that describe filenames. An attacker could exploit this vulnerability by using directory traversal techniques to submit a path to a desired file location. A successful exploit could allow the attacker to view application files that may contain sensitive information.
Patch / fix
- cisco evolved_programmable_network_manager 3.0.1
- cisco prime_infrastructure 3.4
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 23 mo ago
Exploit prediction
13.61% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Affected products
- Cisco Cisco Prime Infrastructure
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
tools.cisco.com
/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190515-pi-pathtrav-1820
vendor-advisory
-
securityfocus.com
/bid/108345
vdb-entry, broken-link, third-party-advisory
Sources
- CVE List CVE-2019-1820
- NVD CVE-2019-1820
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.