Malicious input can provoke XSS when preserving comments
Impact
There is a potential for a mutation XSS (mXSS) vulnerability in AntiSamy caused by flawed parsing of the HTML being sanitized. To be subject to this vulnerability the preserveComments directive must be enabled in your policy file. As a result, certain crafty inputs can result in elements in comment tags being interpreted as executable when using AntiSamy's sanitized output.
Patches
Patched in AntiSamy 1.7.5 and later. This is due to parsing behavior in the neko-htmlunit dependency, just by updating to a newer version the issue was solved. See important remediation details in the reference given below.
Workarounds
If you cannot upgrade to a fixed version of the library, the following mitigation can be applied until you can upgrade: Manually edit your AntiSamy policy file (e.g., antisamy.xml) by deleting the preserveComments directive or setting its value to false, if present.
As the previously mentioned policy settings are preconditions for the mXSS attack to work, changing them as recommended should be sufficient to protect you against this vulnerability when using a vulnerable version of this library. However, the existing bug would still be present in the parser dependency (neko-htmlunit) and therefore in AntiSamy. The safety of this workaround relies on configurations that may change in the future and don't address the root cause of the vulnerability. As such, it is strongly recommended to upgrade to a fixed version of AntiSamy.
For more information
If you have any questions or comments about this advisory:
Email one of the project co-leaders, listed on the OWASP AntiSamy project page, under "Leaders".
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Java / Kotlin (Maven) | org.owasp.antisamy:antisamy | < 1.7.5 | 1.7.5 |
References
- https://github.com/nahsra/antisamy/security/advisories/GHSA-2mrq-w8pv-5pvq
- https://nvd.nist.gov/vuln/detail/CVE-2024-23635
- https://github.com/nahsra/antisamy/commit/12a2e31d3855430c119480655c2bbbbb79a66ecd
- https://github.com/nahsra/antisamy/commit/3e84410ed06ab67f0a4cc3183c67528210f4847d
- https://github.com/nahsra/antisamy
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N- Weakness (CWE)
CWE-79- Platform
- Java / Kotlin (Maven)
- Package
org.owasp.antisamy:antisamy- Disclosed
- 02.02.2024
- Updated
- 11.10.2026 13:20
Sources and licenses
OSV / GitHub Advisory Database - GHSA-2mrq-w8pv-5pvq - CC BY 4.0
Vulnerability history: org.owasp.antisamy:antisamy
All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 7
- First → latest
- 10.2018 02.2024
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Medium 7
Disclosures per year
- 2018: 2
- 2019: 0
- 2020: 0
- 2021: 1
- 2022: 2
- 2023: 1
- 2024: 1
- 2025: 0
- 2026: 0
-
Malicious input can provoke XSS when preserving comments this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.