Project

General

Profile

Actions
Copy link

Bug #4230

closed

tcp/async: incorrect flagging of ACK values as invalid

Added by Victor Julien about 4 years ago. Updated almost 4 years ago.

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

Description

In an async session where we only see the toclient side, the `next_win` is not properly initialized leading to invalid ack events for correct ACKs.

Related issues 1 (0 open — 1 closed)

Copied from Suricata - Bug #4228: tcp/async: incorrect flagging of ACK values as invalidClosedVictor JulienActions
Actions
Copy link

Also available in: Atom PDF