CVE-2019-16779

unknown

Published 2019-12-16 · Modified 2026-03-13

💬 Discuss on Community ✚ Propose mitigation

CVSS v3

—

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N

CVSS v4 NEW

—

not yet in upstream

VIR risk

—

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.

Predictions

Exploit likelihood

30%

Patch ETA

—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

SUSE Affected 1 release

Version	Status	Fixed in
—	Affected	—

Debian Fixed 5 releases

Version	Status	Fixed in
trixie	Fixed	`0.60.0-2`
sid	Fixed	`0.60.0-2`
forky	Fixed	`0.60.0-2`
bullseye	Fixed	`0.60.0-2`
bookworm	Fixed	`0.60.0-2`

Package impact

Ecosystem	Package	Vulnerable	Fixed
RubyGems	excon	`<>= 0.71.0`	`>= 0.71.0`
RubyGems	excon	`<0.71.0`	`0.71.0`

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.