Open sbraz opened 8 years ago
After a bit of research, it appears that this is caused by a change to Apache mod_unique_id
on Red Hat systems. Here are the relevant bug and the patch.
I'm not 100% sure the ID will always have a length of 27, maybe it would be safer to just assume that their size can change and just use \s([a-zA-Z0-9\-\@]+)\s
as it would always match.
With debian 6.0.5, in modsec_audit.log, the log format is as given in below format:
"domain.com 192.168.0.9 - - [10/Apr/2017:13:30:36 +051800] "POST /form.php HTTP/1.1" 403 238 "-" "-" WOs7pH8AAQEAAA0OBBgAAAAG "-" /20170410/20170410-1330/20170410-133036-WOs7pH8AAQEAAA0OBBgAAAAG 0 1765 md5:ac521dc39b114c8b39aaa2769c818fca"
1)No entry found in the mysql database. 2) Using mlog2waffle daemon 3) while running in debug mode, i see the below error "IPv6 not supported by now, sorry" What could be the issue?
My audit files do not match the format expected by waf-fle, they look like:
While they look like this on another system (Ubuntu) with version 2.7.7:
This prevents this line from matching and makes the controller return
IPv6 not supported by now, sorry
.I just changed the expected length of the ID (from 24 to 27) and I guess you should make the regex less restrictive. Here is the diff I applied locally.