Path Traversal in ESAPI
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 2.8%
exploitation probability
2.8%top 14% of all CVEs
observed exploitation
nono source reports it
ESAPI (The OWASP Enterprise Security API) is a free, open source, web application security control library. Prior to version 2.3.0.0, the default implementation of `Validator.getValidDirectoryPath(String, String, File, boolean)` may incorrectly treat the tested input string as a child of the specified parent directory. This potentially could allow control-flow bypass checks to be defeated if an attack can specify the entire string representing the 'input' path. This vulnerability is patched in release 2.3.0.0 of ESAPI. As a workaround, it is possible to write one's own implementation of the Validator interface. However, maintainers do not recommend this.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected products
OWASP ESAPI · org.owasp.esapi:esapiReferences
https://github.com/ESAPI/esapi-java-legacy/blob/develop/documentation/esapi4java-core-2.3.0.0-release-notes.txthttps://github.com/ESAPI/esapi-java-legacy/security/advisories/GHSA-8m5h-hrqm-pxm2https://lists.debian.org/debian-lts-announce/2025/07/msg00010.htmlhttps://securitylab.github.com/advisories/GHSL-2022-008_The_OWASP_Enterprise_Security_API/https://security.netapp.com/advisory/ntap-20230127-0014/https://www.oracle.com/security-alerts/cpujul2022.html