In RubyGem excon, interrupted Persistent Connections May Leak Response Data
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.8epss 1.4%
exploitation probability
1.4%top 29% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N
Affected products
excon · exconReferences
http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00021.htmlhttp://lists.opensuse.org/opensuse-security-announce/2020-01/msg00062.htmlhttps://github.com/excon/excon/commit/ccb57d7a422f020dc74f1de4e8fb505ab46d8a29https://github.com/excon/excon/security/advisories/GHSA-q58g-455p-8vw9https://lists.debian.org/debian-lts-announce/2020/01/msg00015.html