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. See https://github.com/ESAPI/esapi-java-legacy/releases/tag/esapi-2.3.0.0 for details.
Yes; in theory, one could write the own implementation of the Validator interface. This would most easily be done by sub-classing a version of the affected DefaultValidator
class and then overriding the affected getValidDirectoryPath()
to correct the issue. However, this is not recommended.
If you have any questions or comments about this advisory:
github.com/ESAPI/esapi-java-legacy
github.com/ESAPI/esapi-java-legacy/blob/develop/documentation/esapi4java-core-2.3.0.0-release-notes.txt
github.com/ESAPI/esapi-java-legacy/blob/develop/documentation/GHSL-2022-008_The_OWASP_Enterprise_Security_API.md
github.com/ESAPI/esapi-java-legacy/commit/a0d67b75593878b1b6e39e2acc1773b3effedb2a
github.com/ESAPI/esapi-java-legacy/security/advisories/GHSA-8m5h-hrqm-pxm2
nvd.nist.gov/vuln/detail/CVE-2022-23457
security.netapp.com/advisory/ntap-20230127-0014
securitylab.github.com/advisories/GHSL-2022-008_The_OWASP_Enterprise_Security_API
www.oracle.com/security-alerts/cpujul2022.html