← Back to results
Vulnerability record · public intelligence
CVE-2019-16779
MEDIUM

In RubyGem excon, interrupted Persistent Connections May Leak Response Data

Published Dec 16, 2019 · Updated Nov 3, 2026

Severity · CVSSMEDIUM · Not scored
Known exploitationNot listed
EPSS / likelihood1.66%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Nov 3, 2026

In RubyGem excon, interrupted Persistent Connections May Leak Response Data

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

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.

Potential impact

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.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

FIRST-EPSSCVE-LIST-V5
SSVC priority
LOW
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Patch commit ↗
  3. openSUSE-SU-2020:0036 ↗
  4. [debian-lts-announce] 20200119 [SECURITY] [DLA 2070-1] ruby-excon security update ↗
  5. openSUSE-SU-2020:0139 ↗

Record history

Published Dec 16, 2019 · Last refreshed Nov 3, 2026