New in CWP Edge-LatestFree with every CWPpro licenceWebsites up to 300x faster

CWP now includes LSPHP, LSAPI-Cache and CWP Cage at no extra cost with all CWPpro licences. The LSAPI-Cache plugin is integrated into our WordPress and other script installers, and CWP Cage gives every user complete isolation. Available now in the CWP Edge-Latest version.

Get CWPpro ›

Bug in 2.0.15

Started by muscator, Today at 12:20:36 PM

Previous topic - Next topic

muscator

In the changelog about this version it states:

"ModSecurity: switching the OWASP / Comodo rule set no longer risks taking Apache down – the new rule set is activated only after it downloads and extracts successfully, and the Apache configuration is tested with automatic rollback on any error."

As I read this means, that if a user that runs Owasp, changes to Comodo and the changes back to Owasp, CWP will then download and install the latest Owasp rules?

Been there done that.

Nothing happened.

Mod Security still runs with the obsolete Owasp CRS 3.3.2 rules and not the newest though also still obsolete 3.3.10 rules, which at least be better than the 3.3.2 rules from 2021....

It really makes no sense, to keep running these obsolete CRS 3.3.2 rules as default.....?



muscator

#1
After several updates today, this text now occurs in the changelog for 2.0.16 (Edge) and 1.30.22:

"ModSecurity

    The OWASP (latest) rule set is now a free, switchable option alongside the older OWASP set, so you can move between rule sets if one blocks your sites. Comodo cWAF remains a CWPpro feature."


After updating both versions, everything looks just like before - a slider that claims it is for "old" rules and a slider that claims to contain the "latest" rules

Using the option (looks exactly that all the previous version of CWP) it STILL uses the still obsolete CRS rules version 3.3.2 from 2021

Nothing has changed in either of the versions concerning the use of the extremely old rules 3.3.2 from 2021...