Last Modified: Sep 13, 2023
Known Affected Versions:
12.1.0, 12.1.1, 12.1.2
Opened: Jul 20, 2017 Severity: 3-Major
in case a connection was congested and FPS tries to send additional egress (modifying the response, e.g. injections) the order of the response sending might break if this send is successful (i.e congestion just ended). instead of sending the buffered data first (response part that was buffered due to congestion), FPS tries to send the new data first and only than will send the buffered data.
response is corrupted - order of data has erroneously changed
- congested connection - FPS sends modified response (e.g. injections) - sending egress succeeded (congestion ended)
FPS will handle this case correctly, first sending buffered data then sending the new egress.