Yes, it is the ruleset causing the issues AFAIK, previously no problems at all.Hi,
Do you use OWASP CRS?
Yes, it is the ruleset causing the issues AFAIK, previously no problems at all.Hi,
Do you use OWASP CRS?
Check which rule is causing the problem.Yes, it is the ruleset causing the issues AFAIK
Yup, thanks, we are aware of the importance of 949110. Our hosts aren't though and they turned it off and asked us to ignore the warnings - we reinstated and have been working back to identify the actual triggers.949100 ( absolutely must not be deactivated, it counts the anomalous score of the various rules)
You need to disable only the individual rules that are creating the problem
920600 This rule restricts these to familiar charsets. (OK)
modsec-vue
crsdoc.digitalwave.hu
Hi,Same problems with paypal and opayo. Tracked the various triggers and had the following list:
920600
920420
980130
Added these as global exemptions. Did not work.
We have to add exemptions for 949110 for the 2 call back scripts which I understand to be very bad.
I would appreciate a solution that does not involve disabling 949110
As I mentioned in my original post. These were the rules that were showing in the hitlist but disabling them and not 949110 did not work. I have tried again today and it does not work.Hi,
If only those 3 rules are the problem, once disabled, they should no longer trigger 949110.
Maybe there is some other rule to disable, but not 949110 and 980130 (these exclude the detection of many other rules)
Support – OWASP ModSecurity Core Rule Set
coreruleset.org
You could report the problem here
![]()
Issues · coreruleset/coreruleset
OWASP ModSecurity Core Rule Set (Official Repository) - Issues · coreruleset/corerulesetgithub.com
These are the hits that occurred when I added the 3 rules to the exclusion of the script. You can see the top one is what happened when I removed the rules and added 949110 back.As I mentioned in my original post. These were the rules that were showing in the hitlist but disabling them and not 949110 did not work. I have tried again today and it does not work.
The story is old, and it looks like it is over: Is this project dead?So the Comodo ruleset for Litespeed has stopped working for good? Or is it temporary?
Thread starter | Similar threads | Forum | Replies | Date |
---|---|---|---|---|
![]() |
Allowing HTTP methods PATCH and DELETE in modsecurity | Security | 3 | |
K | HTTP ERROR 500 - security2:error - ModSecurity | Security | 2 | |
![]() |
ModSecurity Tools not logging all hits | Security | 17 | |
C | Modsecurity 2.9.7 is coming soon | Security | 1 | |
![]() |
ModSecurity: Transformation Caching Unstable, Fixed, But Deprecated | Security | 2 |