<rss version="2.0"><channel><title>Libmodsecurity3 Cve-2023-38285 on CRS Project</title><link>https://0d2d0d50.website-1u6.pages.dev/tags/libmodsecurity3-cve-2023-38285/</link><description>Recent content in CRS Project</description><item><title>libmodsecurity3 CVE-2023-38285 affecting CRS users</title><link>https://0d2d0d50.website-1u6.pages.dev/20230802/libmodsecurity3-cve-2023-38285-affecting-crs-users/</link><pubDate>Wed, 02 Aug 2023 15:45:05 +0200</pubDate><description>&lt;p&gt;Many CRS users have probably read Trustwave&amp;rsquo;s recent announcement about the new version of libmodsecurity3 (aka ModSecurity v3) and the reason for the release:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/modsecurity-v3-dos-vulnerability-in-four-transformations-cve-2023-38285/"&gt;https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/modsecurity-v3-dos-vulnerability-in-four-transformations-cve-2023-38285/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The new version of the WAF library fixes a CVE described issue, namely: &amp;ldquo;DoS Vulnerability in Four Transformations&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;We would like to draw the attention of all CRS users who also use libmodsecurity3 &lt;strong&gt;to update the library as soon as possible&lt;/strong&gt;. CRS uses one of the mentioned transformations (&lt;code&gt;removeNull&lt;/code&gt;) in several rules. Unfortunately, after analyzing the patch that fixes the bug, we were able to construct a payload that overloaded the libmodsecurity3 engine which many people use with CRS.&lt;/p&gt;</description></item></channel></rss>