ModSecurity: IPmatch: bad IPv4 specification Follow

tara shinn

February 01, 2018 18:48
Updated

his error is not caused by the rule. It is caused by a buggy version of modsecurity, specifically 2.8.0. 2.8.0 has a known critical bug in its IP matching code. It can not properly use IP addresses with rules, as documented in the github bug report below:

https://github.com/SpiderLabs/ModSecurity/issues/706

Do not use 2.8.0. Users should only use the currently supported version of modsecurity documented at the URL below:

https://www.atomicorp.com/wiki/index.php/Atomic_ModSecurity_Rules#Minimum_Version_of_Modsecurity_Required_to_use_the_rule

Comments

0 comments

Please sign in to leave a comment.

ModSecurity: Multipart parsing error
Request body no files data length is larger than the configured limit
Request body (Content-Length) is larger than the configured limit
ModSecurity: SecRemoteRules: ModSecurity was not compiled with SecRemoteRules support.
Reporting False Positives when not running ASL
Failed deleting collection
module security2_module is already loaded, skipping
Syntax error on line 1 of /etc/httpd/conf.d/security2.conf: Cannot load /etc/httpd/modules/mod_security2.so into server: /etc/httpd/modules/mod_security2.so: cannot open shared object file: No such file or directory
module unique_id_module is already loaded, skipping
Installing custom modsecurity rules

Related articles

Articles in this section