Bug #5443
closed
- Related to Bug #5205: FTP-data unrecognized depending on multi-threading added
Took me some time to figure out that I was needing --runmode=single to reproduce due to #5205 (fuzz target runs in single thread and so ftp-data detection goes alright)
- Status changed from New to Assigned
- Priority changed from Normal to High
My analysis :
- we have a FTP flow which expects a ftp-data flow
- we use stream.midstream=true
- the ftp-data flow has a first packet with data
- the ftp-data flow has then a second packet in same direction with RST flag (and no ACK flag)
- RST triggers the parse of all available data, even if it has never been acked
Should we process any of these data that has never been acked ?
- Target version changed from 7.0.0-beta1 to 8.0.0-beta1
- Target version changed from 8.0.0-beta1 to 7.0.0-rc1
Accident during mass retargeting, thanks for catching this.
I would disable the debug assertion if we cannot have a better fix quickly.
This would allow to have fuzzing going on and we would still have the issue to investigate...
- Status changed from Assigned to Closed
- Private changed from Yes to No
- Status changed from Closed to Assigned
The bug is still there to be fixed, so reopening
- Priority changed from High to Normal
- Target version changed from 7.0.0-rc1 to 7.0.0-rc2
- Target version changed from 7.0.0-rc2 to 7.0.0
- Priority changed from Normal to High
- Target version changed from 7.0.0 to 7.0.1
- Status changed from Assigned to In Review
- Status changed from In Review to Closed
- Priority changed from High to Normal
Also available in: Atom
PDF