mirror of https://github.com/OISF/suricata
stream: improve TCP CLOSED handling
Trigger app layer reassembly in both directions as soon as we've set the TCP state to closed. In IDS mode, if a toserver packet would close the state, the app layer would not get updated until the next toclient packet. However, in detection, the raw stream inspection would already use all available stream data in detection and move the 'raw stream progress' tracker forward. When in later (a) packet(s) the app layer was updated and inspection ran on the app layer, the stream progress was already moved too far forward. This would lead to signatures that matched on both stream and app layer to not match. By triggering the app layer reassembly as soon as the TCP state is set to closed, the inspection as both the stream and app layer data available at the same time so these rules can match. Bug: #2570 Bug: #2554pull/3449/head
parent
ee1d207454
commit
2629ca423a
Loading…
Reference in New Issue