Impact
There was a race condition around persistent connections, where a connection which is interrupted (such as by a timeout) would leave data on the socket. Subsequent requests would then read this data, returning content from the previous response. The race condition window appears to be short, and it would be difficult to purposefully exploit this.
Patches
The problem has been patched in 0.71.0, users should upgrade to this or a newer version (if one exists).
Workarounds
Users can workaround the problem by disabling persistent connections, though this may cause performance implications.
References
See the patch for further details.
For more information
If you have any questions or comments about this advisory:
References
Impact
There was a race condition around persistent connections, where a connection which is interrupted (such as by a timeout) would leave data on the socket. Subsequent requests would then read this data, returning content from the previous response. The race condition window appears to be short, and it would be difficult to purposefully exploit this.
Patches
The problem has been patched in 0.71.0, users should upgrade to this or a newer version (if one exists).
Workarounds
Users can workaround the problem by disabling persistent connections, though this may cause performance implications.
References
See the patch for further details.
For more information
If you have any questions or comments about this advisory:
References