Security readout for executives and security teams
Plain-English summary
CVE-2022-23457 affects OWASP ESAPI, a Java security library. In vulnerable versions before 2.3.0.0, a directory path validation check can misjudge whether a supplied path is inside an allowed parent directory. If exposed through application logic, this can undermine file-path safety checks and risk unauthorized file access or modification.
Executive priority
Treat as a high-priority dependency and product exposure check, especially for Java systems handling uploaded files, generated reports, document storage, or user-selected paths. No source here proves active exploitation, so urgency should focus on finding real usage and applying available patched versions or vendor updates.
Technical view
The flaw is CWE-22 path traversal in ESAPI's default Validator.getValidDirectoryPath(String, String, File, boolean). When an attacker can control the full input path, the method may incorrectly treat it as a child of the configured parent directory, bypassing intended validation. ESAPI 2.3.0.0 patches the issue.
Likely exposure
Most exposure is in Java applications or vendor products that include org.owasp.esapi:esapi before 2.3.0.0 and use the affected directory validation method on attacker-influenced full paths. Oracle, NetApp, and Debian references indicate downstream ecosystem impact, but each environment needs product-specific confirmation.
Exploitation context
The CVSS vector shows network reachability, low privileges, no user interaction, and high impact, but high attack complexity. The provided sources do not show CISA KEV listing or confirmed active exploitation. Practical exploitability depends on whether application code passes attacker-controlled complete path strings into the affected ESAPI validator.
Researcher notes
The key research question is not only version presence, but reachable use of the affected validator with attacker-controlled complete path strings. The source bundle identifies the patched ESAPI release and downstream advisories, but does not provide enough evidence to claim universal exploitability across all ESAPI consumers.
Mitigation direction
- Upgrade OWASP ESAPI to version 2.3.0.0 or later.
- Apply vendor updates for affected Oracle, NetApp, or Debian-distributed products.
- Avoid relying on the custom Validator workaround unless vendor guidance requires it.
- Reduce attacker control over full filesystem path inputs where possible.
- Check vendor advisories before changing packaged or embedded ESAPI dependencies.
Validation and detection
- Inventory Java dependencies for org.owasp.esapi:esapi versions before 2.3.0.0.
- Search application code for Validator.getValidDirectoryPath usage.
- Confirm whether external input can control the full path argument.
- Verify deployed artifacts include the patched ESAPI version.
- Review Oracle, NetApp, and Debian advisories for affected packaged products.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-23457 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H1.65.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://securitylab.github.com/advisories/GHSL-2022-008_The_OWASP_Enterprise_Security_API/CVE reference
- https://github.com/ESAPI/esapi-java-legacy/security/advisories/GHSA-8m5h-hrqm-pxm2CVE reference
- https://github.com/ESAPI/esapi-java-legacy/blob/develop/documentation/esapi4java-core-2.3.0.0-release-notes.txtCVE reference
- https://www.oracle.com/security-alerts/cpujul2022.htmlCVE reference
- https://security.netapp.com/advisory/ntap-20230127-0014/CVE reference
- https://lists.debian.org/debian-lts-announce/2025/07/msg00010.htmlCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.