Skip to content

Cross-site Scripting in org.owasp.esapi:esapi

Moderate severity GitHub Reviewed Published Apr 27, 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

There is a potential for an XSS vulnerability in ESAPI caused by a incorrect regular expression for "onsiteURL" in the antisamy-esapi.xml configuration file that can cause URLs with the "javascript:" scheme to NOT be sanitized. See the reference below for full details.

Patches

Patched in ESAPI 2.3.0.0 and later. See important remediation details in the reference given below.

Workarounds

Manually edit your antisamy-esapi.xml configuration files to change the "onsiteURL" regular expression as per remediation instructions in the reference below.

References

Security Bulletin 8

For more information

If you have any questions or comments about this advisory:

References

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

Severity

Moderate

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
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS score

0.159%
(53rd percentile)

Weaknesses

CVE ID

CVE-2022-24891

GHSA ID

GHSA-q77q-vx4q-xx6q

Source code

Credits

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