The Enterprise Security API (ESAPI) project is an OWASP project
to create simple strong security controls for every web platform.
Security controls are not simple to build. You can read about the
hundreds of pitfalls for unwary developers on the OWASP web site. By
providing developers with a set of strong controls, we aim to
eliminate some of the complexity of creating secure web applications.
This can result in significant cost savings across the SDLC.
Path to dependency file: /foxtrot-translator/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/owasp/esapi/esapi/2.1.0/esapi-2.1.0.jar,/home/wss-scanner/.m2/repository/org/owasp/esapi/esapi/2.1.0/esapi-2.1.0.jar,/home/wss-scanner/.m2/repository/org/owasp/esapi/esapi/2.1.0/esapi-2.1.0.jar,/home/wss-scanner/.m2/repository/org/owasp/esapi/esapi/2.1.0/esapi-2.1.0.jar
The Validator.isValidSafeHTML method can result in false negatives where it reports some input as safe (i.e., returns true), but really isn't, and using that same input as-is can in certain circumstances result in XSS vulnerabilities. Because this method cannot be fixed, it is being deprecated and will be removed in one years time from when this advisory is published.
Note that all versions of ESAPI, that have this method (which dates back to at least the ESAPI 1.3 release more than 15 years ago) have this issue and it will continue to exist until these two methods are removed in a future ESAPI release.
WS-2023-0429 - Medium Severity Vulnerability
The Enterprise Security API (ESAPI) project is an OWASP project to create simple strong security controls for every web platform. Security controls are not simple to build. You can read about the hundreds of pitfalls for unwary developers on the OWASP web site. By providing developers with a set of strong controls, we aim to eliminate some of the complexity of creating secure web applications. This can result in significant cost savings across the SDLC.
Path to dependency file: /foxtrot-translator/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/owasp/esapi/esapi/2.1.0/esapi-2.1.0.jar,/home/wss-scanner/.m2/repository/org/owasp/esapi/esapi/2.1.0/esapi-2.1.0.jar,/home/wss-scanner/.m2/repository/org/owasp/esapi/esapi/2.1.0/esapi-2.1.0.jar,/home/wss-scanner/.m2/repository/org/owasp/esapi/esapi/2.1.0/esapi-2.1.0.jar
Dependency Hierarchy: - hbase-server-1.2.1.jar (Root Library) - :x: **esapi-2.1.0.jar** (Vulnerable Library)
Found in HEAD commit: ffb8a6014463ce8aac1bf6e7dc9a23fc4a2a8adc
Found in base branch: master
The Validator.isValidSafeHTML method can result in false negatives where it reports some input as safe (i.e., returns true), but really isn't, and using that same input as-is can in certain circumstances result in XSS vulnerabilities. Because this method cannot be fixed, it is being deprecated and will be removed in one years time from when this advisory is published. Note that all versions of ESAPI, that have this method (which dates back to at least the ESAPI 1.3 release more than 15 years ago) have this issue and it will continue to exist until these two methods are removed in a future ESAPI release.
Publish Date: 2023-11-24
URL: WS-2023-0429
Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None
For more information on CVSS3 Scores, click here.