Project

General

Profile

Actions
Copy link

Bug #4228

closed

tcp/async: incorrect flagging of ACK values as invalid

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

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

Copied to Suricata - Bug #4229: tcp/async: incorrect flagging of ACK values as invalidClosedVictor JulienActions
Copied to Suricata - Bug #4230: tcp/async: incorrect flagging of ACK values as invalidClosedVictor JulienActions
Actions
Copy link
 #2

Updated by Victor Julien about 4 years ago

  • Copied to Bug #4229: tcp/async: incorrect flagging of ACK values as invalid added
Actions
Copy link
 #3

Updated by Victor Julien about 4 years ago

  • Copied to Bug #4230: tcp/async: incorrect flagging of ACK values as invalid added
Actions
Copy link
 #5

Updated by Victor Julien about 4 years ago

  • Status changed from In Review to Closed
  • Label deleted (Needs backport to 5.0, Needs backport to 6.0)
Actions
Copy link

Also available in: Atom PDF