-
Notifications
You must be signed in to change notification settings - Fork 759
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
Suricata rules with "flowbits:noalert" are blocked (false positive) #3386
Comments
|
Just to be very sure, when changing this rule to alert you're not receiving events? If it only happens on drops, we could probably just filter those out and leave them default. |
|
6de0048 should leave the noalert flowbits as is, to test: And download again. |
|
Looks good, with the patch everything works as expected. Thank you for the fast fix and the great support! |
|
@xiic thanks for confirming |
|
When we chose change action from alert to drop, would i see the alert on the Alert page ? |
|
This patch only applies to rules containing Real dropped actions still trigger an alert on my system. |
I've enabled the Suricata rule "emerging-trojan" and enabled "Change all alerts to drop actions".
This triggers a lot of false positives. It looks like I'm not the only one with this problem (https://forum.opnsense.org/index.php?topic=10198).
The offending rule is for example ID 2022317:
https://doc.emergingthreats.net/bin/view/Main/2022317
The rule specifies "flowbits:noalert". If I understand the folks at PT Research/EmergingThreats correctly, a rule with flowbits:nolert should not trigger an alert and should not be blocked (ptresearch/AttackDetection#7).
The Suricata docs suggest the same:
https://suricata.readthedocs.io/en/suricata-4.1.2/rules/flow-keywords.html
Expected behavior
No alert or block should be triggered if flowbits:noalert is set.
Environment
OPNsense 19.1.4-amd64
FreeBSD 11.2-RELEASE-p9-HBSD
Suricata version 4.1.3 RELEASE
The text was updated successfully, but these errors were encountered: