Project

General

Profile

Actions

Bug #4663

closed

rules: drop rules with noalert not fully dropping

Added by Victor Julien about 1 year ago. Updated 10 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
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.


Related issues 4 (0 open4 closed)

Related to Bug #4670: rules: mix of drop and pass rules issuesClosedVictor JulienActions
Related to Bug #4941: alerts: 5.0.8/6.0.4 count noalert sigs towards built-in alert limitClosedJuliana Fajardini ReichowActions
Copied to Bug #4675: rules: drop rules with noalert not fully droppingClosedVictor JulienActions
Copied to Bug #4676: rules: drop rules with noalert not fully droppingClosedVictor JulienActions
Actions #1

Updated by Victor Julien about 1 year ago

  • Status changed from In Progress to In Review
Actions #2

Updated by Victor Julien about 1 year ago

  • Related to Bug #4670: rules: mix of drop and pass rules issues added
Actions #3

Updated by Jeff Lucovsky about 1 year ago

  • Copied to Bug #4675: rules: drop rules with noalert not fully dropping added
Actions #4

Updated by Jeff Lucovsky about 1 year ago

  • Copied to Bug #4676: rules: drop rules with noalert not fully dropping added
Actions #5

Updated by Victor Julien 10 months ago

  • Status changed from In Review to Closed
Actions #6

Updated by Victor Julien 9 months ago

  • Related to Bug #4941: alerts: 5.0.8/6.0.4 count noalert sigs towards built-in alert limit added
Actions

Also available in: Atom PDF