Project

General

Profile

Actions
Copy link

Bug #4676

closed

rules: drop rules with noalert not fully dropping

Added by Jeff Lucovsky about 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Victor Julien
Target version:
5.0.8
Affected Versions:
Effort:
Difficulty:
Label:

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 1 (0 open — 1 closed)

Copied from Suricata - Bug #4663: rules: drop rules with noalert not fully droppingClosedVictor JulienActions
Actions
Copy link
 #1

Updated by Jeff Lucovsky about 3 years ago

  • Copied from Bug #4663: rules: drop rules with noalert not fully dropping added
Actions
Copy link
 #2

Updated by Victor Julien about 3 years ago

  • Status changed from Assigned to In Progress
  • Assignee changed from Jeff Lucovsky to Victor Julien
Actions
Copy link
 #3

Updated by Victor Julien about 3 years ago

  • Status changed from In Progress to Closed
Actions
Copy link

Also available in: Atom PDF