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.
References
Link | Resource |
---|---|
https://github.com/excon/excon/security/advisories/GHSA-q58g-455p-8vw9 | Third Party Advisory |
https://github.com/excon/excon/commit/ccb57d7a422f020dc74f1de4e8fb505ab46d8a29 | Patch Third Party Advisory |
http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00021.html | Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2020/01/msg00015.html | Mailing List Third Party Advisory |
http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00062.html | Third Party Advisory |
Information
Published : 2019-12-16 12:15
Updated : 2021-10-28 06:38
NVD link : CVE-2019-16779
Mitre link : CVE-2019-16779
JSON object : View
CWE
CWE-362
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Products Affected
excon_project
- excon
debian
- debian_linux
opensuse
- backports_sle
- leap