In RubyGem excon before 0.71.0, 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.
Metrics
Affected Vendors & Products
Advisories
Source | ID | Title |
---|---|---|
![]() |
DLA-2070-1 | ruby-excon security update |
![]() |
EUVD-2019-0799 | In RubyGem excon before 0.71.0, 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. |
![]() |
GHSA-q58g-455p-8vw9 | In RubyGem excon, interrupted Persistent Connections May Leak Response Data |
Fixes
Solution
No solution given by the vendor.
Workaround
Users can workaround the problem by disabling persistent connections, though this may cause performance implications.
References
History
No history.

Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2024-08-05T01:24:48.572Z
Reserved: 2019-09-24T00:00:00
Link: CVE-2019-16779

No data.

Status : Modified
Published: 2019-12-16T20:15:15.540
Modified: 2024-11-21T04:31:10.503
Link: CVE-2019-16779

No data.

No data.