| Package | Affected versions | Patched versions |
|---|---|---|
| org.owasp.esapi:esapi | < 2.3.0.0 | 2.3.0.0 |
| weblogic server | = 12.2.1.3.0= 12.2.1.4.0= 14.1.1.0.0 | |
| enterprise security api | < 2.3.0.0 | 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. 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:
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free