WaratekVRT Sign in

Medium Antisamy Project CVEs

7 CVEs, 4 protected by Waratek

Reset
More filters (1)
Columns
Vendor antisamy project✕
Overview 7 matches · 4 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
7matches 4protected57.1% 0exploited0.0% 0CISA KEV0.0% 0public PoC0.0% 0EPSS ≥ 0.50.0%
Protected by Waratek 4 57.1% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 3 42.9%
Critical 0 0.0% High 0 0.0% Medium 7 100.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 4 57.1% partly blocked 0 0.0% not blocked 3 42.9% not established 0 0.0% unrecorded 0 0.0%
Exploited 0 0.0% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 7 100.0%
split by peak 2 / year
No exploit published: 3Protected by Waratek: 4 Medium: 7 not blocked: 3blocked by ARMR today: 4 No public exploit: 7
20161 No exploit published1 Medium1 not blocked1 No public exploit1 20171 Protected by Waratek1 Medium1 blocked by ARMR today1 No public exploit1 20180 20190 20200 20211 No exploit published1 Medium1 not blocked1 No public exploit1 20222 Protected by Waratek2 Medium2 blocked by ARMR today2 No public exploit2 20231 Protected by Waratek1 Medium1 blocked by ARMR today1 No public exploit1 20241 No exploit published1 Medium1 not blocked1 No public exploit1
201620172018201920202021202220232024
7 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2024-23635 Medium 2024-02-02 No exploit published No public exploit AntiSamy is a library for performing fast, configurable cleansing of HTML coming from untrusted sources. Prior to 1.7.5, 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. Patched in AntiSamy 1.7.5 and later.
CVE-2023-43643 Medium 2023-10-09 Protected by Waratek No public exploit AntiSamy is a library for performing fast, configurable cleansing of HTML coming from untrusted sources. Prior to version 1.7.4, 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. This issue has been patched in AntiSamy 1.7.4 and later.
CVE-2022-29577 Medium 2022-04-21 Protected by Waratek No public exploit OWASP AntiSamy before 1.6.7 allows XSS via HTML tag smuggling on STYLE content with crafted input. The output serializer does not properly encode the supposed Cascading Style Sheets (CSS) content. NOTE: this issue exists because of an incomplete fix for CVE-2022-28367.
CVE-2022-28367 Medium 2022-04-21 Protected by Waratek No public exploit OWASP AntiSamy before 1.6.6 allows XSS via HTML tag smuggling on STYLE content with crafted input. The output serializer does not properly encode the supposed Cascading Style Sheets (CSS) content.
CVE-2021-35043 Medium 2021-07-19 No exploit published No public exploit OWASP AntiSamy before 1.6.4 allows XSS via HTML attributes when using the HTML output serializer (XHTML is not affected). This was demonstrated by a javascript: URL with &#00058 as the replacement for the : character.
CVE-2017-14735 Medium 2017-09-25 Protected by Waratek No public exploit OWASP AntiSamy before 1.5.7 allows XSS via HTML5 entities, as demonstrated by use of : to construct a javascript: URL.
CVE-2016-10006 Medium 2016-12-24 No exploit published No public exploit In OWASP AntiSamy before 1.5.5, by submitting a specially crafted input (a tag that supports style with active content), you could bypass the library protections and supply executable code. The impact is XSS.