CVE-2019-16779
Published: 16 December 2019
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.
Priority
Status
| Package | Release | Status |
|---|---|---|
|
ruby-excon Launchpad, Ubuntu, Debian |
bionic |
Needs triage
|
| disco |
Ignored
(end of life)
|
|
| eoan |
Ignored
(end of life)
|
|
| focal |
Not vulnerable
(0.60.0-2)
|
|
| groovy |
Not vulnerable
(0.60.0-2)
|
|
| hirsute |
Not vulnerable
(0.60.0-2)
|
|
| impish |
Not vulnerable
(0.60.0-2)
|
|
| jammy |
Not vulnerable
(0.60.0-2)
|
|
| kinetic |
Not vulnerable
(0.60.0-2)
|
|
| lunar |
Not vulnerable
(0.60.0-2)
|
|
| mantic |
Not vulnerable
(0.60.0-2)
|
|
| trusty |
Does not exist
|
|
| upstream |
Needs triage
|
|
| xenial |
Needs triage
|
Severity score breakdown
| Parameter | Value |
|---|---|
| Base score | 5.9 |
| Attack vector | Network |
| Attack complexity | High |
| Privileges required | None |
| User interaction | None |
| Scope | Unchanged |
| Confidentiality | High |
| Integrity impact | None |
| Availability impact | None |
| Vector | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |