CVE-2023-20127
Cisco Prime Infrastructure ≤ 3.7
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-20127 is a medium-severity Path Traversal: 'dir/../../filename' (CWE-27) vulnerability in Cisco Prime Infrastructure. Its CVSS base score is 6.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Application Window Discovery (T1010); ranked in the top 41% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-24306
Vulnerability Data
Multiple vulnerabilities in the web-based management interface of Cisco Prime Infrastructure and Cisco Evolved Programmable Network Manager (EPNM) could allow a remote attacker to obtain privileged information and conduct cross-site scripting (XSS) and cross-site request forgery (CSRF) attacks. For more…
more
information about these vulnerabilities, see the Details section of this advisory.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Vulnerability identification processes will discover path traversal weaknesses during code or configuration review.
Least-privilege file permissions and access enforcement can limit the damage from a successful traversal.
Secure SDLC practices directly require input validation and path sanitization that prevent directory traversal flaws.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure development lifecycle mandates input validation and path sanitization that directly prevents directory traversal.
A.8.26 only requires that security requirements (including resilience against SQLi or buffer overflows) be identified and specified during development or acquisition; it does not itself neutralize path traversal sequences or stop exploitation of CWE-27.
Secure architecture principles discourage unsafe path construction but do not prescribe the specific coding fix.
Secure coding standards require neutralizing '../' sequences and using safe file APIs, eliminating this exact weakness.
Security testing in development catches path-traversal flaws before release but does not itself implement the control.