Project

General

Profile

Actions
Copy link

Bug #4663

closed

rules: drop rules with noalert not fully dropping

Added by Victor Julien over 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Victor Julien
Target version:
7.0.0-beta1
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 open — 4 closed)

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

Also available in: Atom PDF