The OWASP ModSecurity Core Rule Set team is proud to announce the general availability of release candidate 2 for the upcoming CRS v3.2.0. The new release is available at
This release represents a very big step forward in terms of both capabilities and protections including:
- Improved compatibility with ModSecurity 3.x
- Improved CRS docker container that is fully configureable at creation
- Expanded Java RCE blacklist
- Expanded unix shell RCE blacklist
- Improved PHP RCE detection
- Expanded LFI blacklists
- Added XenForo rule exclusion profile
- Fixes for many false positives and bypasses
- Detection of more security scanners
- Regexp performance improvements preventing ReDoS in most cases
Please see the CHANGES document with around 150 entries for a detailed list of new features and improvements.
Note how this RC2 is the first public release candidate for 3.2.0. RC1 was not formally released.
Our desire is to see the Core Rule Set project used as a baseline security feature, effectively protecting from OWASP TOP 10 risks with few side effects. As such we attempt to cut down on false positives as much as possible in the default install. This RC2 therefore offers an opportunity for individuals to provide feedback and to report any issue they face with this release. We will then try and fix them for the upcoming full release.
Please use the CRS GitHub (https://github.com/SpiderLabs/owasp-modsecurity-crs), our slack channel (#coreruleset on owasp.slack.com), or the Core Rule Set mailing list to tell us about your experiences, including false positives or other issues with this release candidate.
Our current timeline is to seek public feedback on RC2 for the next two weeks, followed by an RC3 (if needed) and subsequently a release on September 24. We look forward to hearing your feedback!
Walter Hop, release manager, on behalf of the Core Rule Set development team