Project

General

Profile

Actions

Bug #4645

closed

TCP reassembly, failed assert app_progress > last_ack_abs, both sides need to be pruned

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

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

Description

Found by oss-fuzz
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=35626

Minimized reproducer with suricata is
./src/suricata -r lolb.pcap -k none -c suricata.yaml --set stream.midstream=true

What happens is
- first packet (midstream) all ok (ack = 1)
- second packet, from the other side, ack is ok, but sequence indicates a gap from first packet ack (seq = 77)
- third packet, sequence ok, ack is increased since first packet confirming the gap (ack = 77) StreamTcpUpdateAppLayerProgress is called by AppLayerHandleTCPData at the end of if (flags & STREAM_GAP) {
- Fourth packet is in first direction (seq and ack meaningless)

At the end of third packet, the 76 gap does not get subtracted in app_progress_rel as StreamTcpPruneSession only considers the other stream


Files

lolb.pcap (984 Bytes) lolb.pcap Philippe Antoine, 06/30/2021 07:26 PM

Related issues 1 (0 open1 closed)

Copied from Suricata - Bug #4549: TCP reassembly, failed assert app_progress > last_ack_abs, both sides need to be prunedClosedVictor JulienActions
Actions

Also available in: Atom PDF