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.
The problem has been patched in 0.71.0, users should upgrade to this or a newer version (if one exists).
Users can workaround the problem by disabling persistent connections, though this may cause performance implications.
See the patch for further details.
If you have any questions or comments about this advisory: * Open an issue in excon/issues * Email us at geemus+github@gmail.com
{ "nvd_published_at": "2019-12-16T20:15:00Z", "cwe_ids": [ "CWE-362", "CWE-664" ], "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2019-12-16T19:28:10Z" }