Candidate: CVE-2019-16779
PublicDate: 2019-12-16 20:15:00 UTC
References:
 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16779
 https://github.com/excon/excon/security/advisories/GHSA-q58g-455p-8vw9
 https://github.com/excon/excon/commit/ccb57d7a422f020dc74f1de4e8fb505ab46d8a29
Description:
 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.
Ubuntu-Description:
Notes:
Mitigation:
Bugs:
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946904
Priority: medium
Discovered-by:
Assigned-to:
CVSS:
 nvd: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N [5.9 MEDIUM]


Patches_ruby-excon:
upstream_ruby-excon: needs-triage
precise/esm_ruby-excon: DNE
trusty_ruby-excon: ignored (out of standard support)
trusty/esm_ruby-excon: DNE
xenial_ruby-excon: ignored (end of standard support, was needs-triage)
bionic_ruby-excon: needs-triage
disco_ruby-excon: ignored (reached end-of-life)
eoan_ruby-excon: ignored (reached end-of-life)
focal_ruby-excon: not-affected (0.60.0-2)
groovy_ruby-excon: not-affected (0.60.0-2)
hirsute_ruby-excon: not-affected (0.60.0-2)
impish_ruby-excon: not-affected (0.60.0-2)
jammy_ruby-excon: not-affected (0.60.0-2)
devel_ruby-excon: not-affected (0.60.0-2)