Skip to content

Path traversal in the OWASP Enterprise Security API

High severity GitHub Reviewed Published Apr 23, 2022 in ESAPI/esapi-java-legacy • Updated Jan 27, 2023

Package

maven org.owasp.esapi:esapi (Maven)

Affected versions

<= 2.2.3.1

Patched versions

2.3.0.0

Description

Impact

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.

Patches

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.

Workarounds

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.

For more information

If you have any questions or comments about this advisory:

References

@kwwall kwwall published to ESAPI/esapi-java-legacy Apr 23, 2022
Published by the National Vulnerability Database Apr 25, 2022
Published to the GitHub Advisory Database Apr 27, 2022
Reviewed Apr 27, 2022
Last updated Jan 27, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.294%
(70th percentile)

Weaknesses

CVE ID

CVE-2022-23457

GHSA ID

GHSA-8m5h-hrqm-pxm2

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.