ModSecurity: Rule processing failed
-
- Forum User
- Posts: 70
- Joined: Fri Oct 20, 2006 8:30 pm
ModSecurity: Rule processing failed
Geting a problem with modsecurity and seeing lots of messages 'ModSecurity: Rule processing failed' in log files, have the latest version from atomic repos
Energylevel
- mikeshinn
- Atomicorp Staff - Site Admin
- Posts: 4155
- Joined: Thu Feb 07, 2008 7:49 pm
- Location: Chantilly, VA
Re: ModSecurity: Rule processing failed
What version are you using, and which rules?
Michael Shinn
Atomicorp - Security For Everyone
Atomicorp - Security For Everyone
-
- Forum User
- Posts: 70
- Joined: Fri Oct 20, 2006 8:30 pm
Re: ModSecurity: Rule processing failed
Modsecurity 2.5.13 from atomic repos ... rules:
05_asl_exclude.conf
05_asl_scanner.conf
05_asl_user_exclude.conf
10_asl_antimalware.conf
10_asl_rules.conf
20_asl_useragents.conf
30_asl_antispam.conf
40_asl_apache2-rules.conf
50_asl_rootkits.conf
60_asl_recons.conf
99_asl_jitp.conf
05_asl_exclude.conf
05_asl_scanner.conf
05_asl_user_exclude.conf
10_asl_antimalware.conf
10_asl_rules.conf
20_asl_useragents.conf
30_asl_antispam.conf
40_asl_apache2-rules.conf
50_asl_rootkits.conf
60_asl_recons.conf
99_asl_jitp.conf
Energylevel
- mikeshinn
- Atomicorp Staff - Site Admin
- Posts: 4155
- Joined: Thu Feb 07, 2008 7:49 pm
- Location: Chantilly, VA
Re: ModSecurity: Rule processing failed
Are you using the real time or delayed rules? And what version of either are you using?
Also, what does your audit_log entry look like? We definitely need the full payload to know whats triggering and why.
Also, what does your audit_log entry look like? We definitely need the full payload to know whats triggering and why.
Michael Shinn
Atomicorp - Security For Everyone
Atomicorp - Security For Everyone
-
- Forum User
- Posts: 70
- Joined: Fri Oct 20, 2006 8:30 pm
Re: ModSecurity: Rule processing failed
Delayed rules, example audit log:
--e017171a-A--
[19/Dec/2010:22:35:10 +0000] BB2Rb38AAAEAABR17DAAAAAK 11.111.11.253 56020 11.111.11.16 80
--e017171a-B--
GET / HTTP/1.0
User-Agent: check_http/v1991 (nagios-plugins 1.4.12)
Connection: close
Host: 11.111.11.16:80
--e017171a-F--
HTTP/1.1 200 OK
Last-Modified: Wed, 27 Dec 2006 02:00:23 GMT
ETag: "39d8090-33f-64c31bc0"
Accept-Ranges: bytes
Content-Length: 831
Connection: close
Content-Type: text/html
--e017171a-H--
Message: Rule processing failed.
Stopwatch: 1292798110044527 112479 (32361 36463 94655)
WAF: ModSecurity for Apache/2.5.13 (http://www.modsecurity.org/); 201001071602.
Server: Apache/2.0.52 (CentOS)
--e017171a-Z--
--e017171a-A--
[19/Dec/2010:22:35:10 +0000] BB2Rb38AAAEAABR17DAAAAAK 11.111.11.253 56020 11.111.11.16 80
--e017171a-B--
GET / HTTP/1.0
User-Agent: check_http/v1991 (nagios-plugins 1.4.12)
Connection: close
Host: 11.111.11.16:80
--e017171a-F--
HTTP/1.1 200 OK
Last-Modified: Wed, 27 Dec 2006 02:00:23 GMT
ETag: "39d8090-33f-64c31bc0"
Accept-Ranges: bytes
Content-Length: 831
Connection: close
Content-Type: text/html
--e017171a-H--
Message: Rule processing failed.
Stopwatch: 1292798110044527 112479 (32361 36463 94655)
WAF: ModSecurity for Apache/2.5.13 (http://www.modsecurity.org/); 201001071602.
Server: Apache/2.0.52 (CentOS)
--e017171a-Z--
Energylevel
- mikeshinn
- Atomicorp Staff - Site Admin
- Posts: 4155
- Joined: Thu Feb 07, 2008 7:49 pm
- Location: Chantilly, VA
Re: ModSecurity: Rule processing failed
Are you running anyone elses rules, and how do you have modsecurity configured?
Michael Shinn
Atomicorp - Security For Everyone
Atomicorp - Security For Everyone
-
- Forum User
- Posts: 70
- Joined: Fri Oct 20, 2006 8:30 pm
Re: ModSecurity: Rule processing failed
No other rules, checked config file exactly as per your Wiki article....
Energylevel
- mikeshinn
- Atomicorp Staff - Site Admin
- Posts: 4155
- Joined: Thu Feb 07, 2008 7:49 pm
- Location: Chantilly, VA
Re: ModSecurity: Rule processing failed
Which version of the rpm do you have installed, which Linux distro are you running and are you missing any updates to apache? I wonder if this is a bug in apache or mod_sec on your platform - thats not a rule error, thats an engine error and I havent seen that error in years. So it sounds like a bug in either the module, or a total blow out in apache itself - either way its not the rules. Can you send the full rpm -qa for mod_security so we can make sure its not a point release or build error for your distro OS (and dont forget to tell us what distro you are using).
It shouldnt make much of a difference, but make sure you running the latest version of the free/unsupported rules.
It shouldnt make much of a difference, but make sure you running the latest version of the free/unsupported rules.
Michael Shinn
Atomicorp - Security For Everyone
Atomicorp - Security For Everyone