-
Notifications
You must be signed in to change notification settings - Fork 1.7k
rules with multiMatch may omit 'tag' information in audit log output #2754
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hello @chenjinlei , First, just to be precise, although you refer to 'rule message or log data', the rule 942100 log line does include expected information for both 'msg' and 'data'. You have correctly noted that the expected 'tag' information is not present for 942100 (although it is present for the other two rules). What is causing that effect with rule 942100 is the 'multiMatch' action. If you were to remove that action, then the 'tag' information would appear whenever there is a detection, along with the rest of the audit log information. (Of course, that doesn't mean it would be advisable to remove it; presumably it has been assessed by the rule writers as desirable to include multiMatch for that rule). This is not intentional behaviour and it can appropriately be classified as a bug. It does, however, appear to be a longstanding bug in ModSecurity and not new to any recent release. |
Oh, thanks, @martinhsv ! and yes, it would be insecure to remove 'mulitMatch' action for this rule:
I think the target needs to be check before and after "t:none,t:utf8toUnicode,t:urlDecodeUni,t:removeNulls,", this transformation... Do you have any idea when this would be fixed? or is it easy to fix? maybe I can help to do some work... |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I wrote a simple program and detect the potential attacks, and I find that rule message(or log data) I get from callback differs.
These logs came from a attack pcap. The one triggered SQLi does not contain any TAGs, and looked up to the rule 942100 does have TAGs. Could anyone have any idea how this happened? Thanks ahead.
The text was updated successfully, but these errors were encountered: