Project

General

Profile

Actions
Copy link

Bug #4953

closed

stream: too aggressive pruning in lossy streams

Added by Victor Julien almost 3 years ago. Updated almost 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

Pruning of StreamBufferBlocks could remove blocks that fell entirely after the target offset due to a logic error. This could lead to data being evicted that was still meant to be processed in the app-layer parsers.

Related issues 2 (0 open — 2 closed)

Copied to Suricata - Bug #4954: stream: too aggressive pruning in lossy streamsClosedShivani BhardwajActions
Copied to Suricata - Bug #4955: stream: too aggressive pruning in lossy streamsClosedJeff LucovskyActions
Actions
Copy link
 #1

Updated by Victor Julien almost 3 years ago

  • Status changed from In Progress to Closed
Actions
Copy link
 #2

Updated by Jeff Lucovsky almost 3 years ago

  • Copied to Bug #4954: stream: too aggressive pruning in lossy streams added
Actions
Copy link
 #3

Updated by Jeff Lucovsky almost 3 years ago

  • Copied to Bug #4955: stream: too aggressive pruning in lossy streams added
Actions
Copy link

Also available in: Atom PDF