Actions
Bug #4663
closedrules: drop rules with noalert not fully dropping
Affected Versions:
Effort:
Difficulty:
Label:
Needs backport to 5.0, Needs backport to 6.0
Description
A simple drop rules like drop tcp any any -> any any (noalert; sid:1; rev:1;) fails to drop packets beyond the first in each direction of the flow.
The cause is that the rule is just evaluated once per flow direction, by the "IP-only" detection path. In this case the 'noalert' presence causes the drop not to be applied to the flow.
Updated by Victor Julien over 3 years ago
- Status changed from In Progress to In Review
Updated by Victor Julien over 3 years ago
- Related to Bug #4670: rules: mix of drop and pass rules issues added
Updated by Jeff Lucovsky over 3 years ago
- Copied to Bug #4675: rules: drop rules with noalert not fully dropping added
Updated by Jeff Lucovsky over 3 years ago
- Copied to Bug #4676: rules: drop rules with noalert not fully dropping added
Updated by Victor Julien about 3 years ago
- Status changed from In Review to Closed
Updated by Victor Julien almost 3 years ago
- Related to Bug #4941: alerts: 5.0.8/6.0.4 count noalert sigs towards built-in alert limit added
Actions