In RubyGem excon, interrupted Persistent Connections May Leak Response Data
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| excon | excon | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
No data.
No data available yet.
Vendor Workaround
Users can workaround the problem by disabling persistent connections, though this may cause performance implications.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-2070-1 | ruby-excon security update |
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 |
GHSA-q58g-455p-8vw9 | In RubyGem excon, interrupted Persistent Connections May Leak Response Data |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.7% (1.662% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.