First published: Mon Dec 16 2019(Updated: )
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.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Excon | <0.71.0 | |
openSUSE Backports | =15.0-sp1 | |
openSUSE | =15.1 | |
Debian GNU/Linux | =8.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-16779 has a medium severity due to the potential for unintended data leakage from race conditions.
To fix CVE-2019-16779, update Excon to version 0.71.0 or later.
Excon versions prior to 0.71.0 are affected by CVE-2019-16779.
CVE-2019-16779 impacts multiple platforms including Debian 8.0, openSUSE Leap 15.1, and openSUSE Backports SLE 15.0 SP1.
Failing to address CVE-2019-16779 could result in sensitive information being unintentionally exposed through incorrect socket data.