GitHub Advisoryadvisory · RubyGems

GHSA-q58g-455p-8vw9 In RubyGem excon, interrupted Persistent Connections May Leak Response Data

MEDIUM Published 2019-12-16 Modified 2021-10-29 Official page ↗
Aliases
CVE-2019-16779
Ecosystem
RubyGems
Packages
excon
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N
Weaknesses
CWE-362, CWE-664
Reviewed
2019-12-16

Affected packages

• RubyGems excon: < 0.71.0 → fixed in 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: • Open an issue in excon/issues • Email us at [email protected]

Related

Alias · CVE (1)

  • CVE-2019-16779 In RubyGem excon before 0.71.0, there was a race condition around persistent connections, where a connection which is interrupted (such as… vulnerability

Weakness · CWE (2)

  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization weakness
  • CWE-664 Improper Control of a Resource Through its Lifetime weakness

References