CWE
79
Advisory Published
CVE Published
Updated

CVE-2023-51652: OWASP.AntiSamy mXSS when preserving comments

First published: Tue Jan 02 2024(Updated: )

# 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 and also allow for certain tags at the same time. 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 OWASP AntiSamy .NET 1.2.0 and later. 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. Also it would be useful to make AntiSamy remove the `noscript` tag by adding this in your tag definitions under the `<tagrules>` node (or deleting it entirely if present): ```xml <tag name="noscript" action="remove"/> ``` 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 AntiSamy or its parser dependency (HtmlAgilityPack). 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](https://owasp.org/www-project-antisamy/) page, under "Leaders".

Credit: security-advisories@github.com

Affected SoftwareAffected VersionHow to fix
nuget/OWASP.AntiSamy<1.2.0
1.2.0
OWASP AntiSamy<1.2.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2023-51652?

    CVE-2023-51652 is a medium severity vulnerability due to its potential for exploitation via mutation XSS.

  • How do I fix CVE-2023-51652?

    To fix CVE-2023-51652, ensure the `preserveComments` directive is disabled in your policy file or upgrade to AntiSamy version 1.2.0 or later.

  • Which versions of AntiSamy are affected by CVE-2023-51652?

    CVE-2023-51652 affects AntiSamy versions prior to 1.2.0.

  • What is the nature of the vulnerability in CVE-2023-51652?

    CVE-2023-51652 involves a mutation XSS vulnerability caused by flawed HTML parsing when the `preserveComments` directive is enabled.

  • Does CVE-2023-51652 affect my application?

    If your application uses an affected version of AntiSamy and has the `preserveComments` option enabled, it may be vulnerable to CVE-2023-51652.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203