org.owasp.esapi:esapi: Improper Limitation of a Pathname to a Restricted Directory
CVE-2022-23457 is a critical-severity improper limitation of a pathname to a restricted directory vulnerability in org.owasp.esapi:esapi from OWASP ESAPI, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 2.3.0.0 as the first without the flaw, so updating org.owasp.esapi:esapi to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 2.85% chance of exploitation within 30 days, higher than 87% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update org.owasp.esapi:esapi to 2.3.0.0 or a later version.
- Update Enterprise Security API to 2.3.0.0 or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| OWASP ESAPI | org.owasp.esapi:esapi | 2.3.0.0 up to, but not including, 2.3.0.0 | 2.3.0.0 |
| Owasp | Enterprise Security API | before 2.3.0.0 | 2.3.0.0 |
| Oracle | Weblogic Server | 12.2.1.3.0; 12.2.1.4.0; 14.1.1.0.0 | Not stated |
| NetApp | Active Iq Unified Manager | Not specified in the record | Not stated |
| NetApp | Oncommand Workflow Automation | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (github.com) |
| CVSS 3.1 | 9.8 | Critical | NVD |
| CVSS 2.0 | 7.5 | High | NVD |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/ESAPI/esapi-java-legacy/security/advisories/GHSA-8m5h-hrqm-pxm2Third Party Advisory
Patches and release notes
Third-party and government advisories
- security.netapp.com/advisory/ntap-20230127-0014/Third Party Advisory
Technical write-ups (may include proof of concept)
- securitylab.github.com/advisories/GHSL-2022-008_The_OWASP_Enterprise_Security_API/Exploit, Third Party Advisory
Other references
Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 7.5 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 7.5 High severity
- 7.2 High severity
- 7.5 High severity
Spotted an error? Tell us.