Project

General

Profile

Actions

Bug #4954

closed

stream: too aggressive pruning in lossy streams

Added by Jeff Lucovsky over 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Normal
Target version:
Affected Versions:
Effort:
Difficulty:
Label:

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 1 (0 open1 closed)

Copied from Suricata - Bug #4953: stream: too aggressive pruning in lossy streamsClosedVictor JulienActions
Actions #1

Updated by Jeff Lucovsky over 2 years ago

  • Copied from Bug #4953: stream: too aggressive pruning in lossy streams added
Actions #2

Updated by Shivani Bhardwaj over 2 years ago

  • Status changed from Assigned to In Progress
Actions #3

Updated by Shivani Bhardwaj over 2 years ago

  • Status changed from In Progress to In Review
Actions #4

Updated by Shivani Bhardwaj about 2 years ago

  • Status changed from In Review to Closed
Actions

Also available in: Atom PDF