Bug #7687: flow: non-TCP protocol timeout handling leads to missing flows - Suricata - Open Information Security Foundation

Actions

Copy link

Bug #7687

closed

flow: non-TCP protocol timeout handling leads to missing flows

Added by Victor Julien 2 months ago. Updated 4 days ago.

Status:

Closed

Priority:

Normal

Assignee:

Victor Julien

Target version:

8.0.0-rc1

Affected Versions:

Effort:

Difficulty:

Label:

Description

By using the global time tracking threads can get out of sync and enforce timeouts that are "in the future" for a packet thread. This would lead to flows getting timed out. This was solved for TCP by tracking the "owning" thread in the flow, but this was not implemented for UDP and other non-TCP protocols.

Subtasks 1 (0 open — 1 closed)