CVE-2019-16779

In RubyGem excon, interrupted Persistent Connections May Leak Response Data

Published Dec 16, 2019 CVSS 3.1 · 5.8 Medium EPSS 1.7% KEV · Not listed
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.

Remediation

Vendor Workaround

Users can workaround the problem by disabling persistent connections, though this may cause performance implications.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-2070-1 ruby-excon security update
EUVD EUVD 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.
Github GHSA Github GHSA GHSA-q58g-455p-8vw9 In RubyGem excon, interrupted Persistent Connections May Leak Response Data
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 5, 2024, 1:24 AM
Reserved
Sep 24, 2019, 12:00 AM
Status
Analyzed
Published
Dec 16, 2019, 8:15 PM
Modified
Jul 28, 2026, 6:16 PM