Skip to content

In RubyGem excon, interrupted Persistent Connections May Leak Response Data

Moderate severity GitHub Reviewed Published Dec 16, 2019 in excon/excon • Updated May 4, 2023

Package

bundler excon (RubyGems)

Affected versions

< 0.71.0

Patched versions

0.71.0

Description

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.

Patches

The problem has been patched in 0.71.0, users should upgrade to this or a newer version (if one exists).

Workarounds

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

References

See the patch for further details.

For more information

If you have any questions or comments about this advisory:

References

@geemus geemus published to excon/excon Dec 16, 2019
Reviewed Dec 16, 2019
Published to the GitHub Advisory Database Dec 16, 2019
Published by the National Vulnerability Database Dec 16, 2019
Last updated May 4, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N

EPSS score

0.788%
(82nd percentile)

Weaknesses

CVE ID

CVE-2019-16779

GHSA ID

GHSA-q58g-455p-8vw9

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.