CVE-2020-11077
Published: 22 May 2020
In Puma (RubyGem) before 4.3.5 and 3.12.6, a client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client. If the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request's body. Puma, however, would see it as two requests, and when processing the second request, send back a response that the proxy does not expect. If the proxy has reused the persistent connection to Puma to send another request for a different client, the second response from the first client will be sent to the second client. This is a similar but different vulnerability from CVE-2020-11076. The problem has been fixed in Puma 3.12.6 and Puma 4.3.5.
Priority
Status
| Package | Release | Status |
|---|---|---|
|
puma Launchpad, Ubuntu, Debian |
bionic |
Does not exist
|
| eoan |
Ignored
(end of life)
|
|
| focal |
Released
(3.12.4-1ubuntu2+esm1)
Available with Ubuntu Pro |
|
| groovy |
Ignored
(end of life)
|
|
| hirsute |
Ignored
(end of life)
|
|
| impish |
Ignored
(end of life)
|
|
| jammy |
Not vulnerable
(5.5.2-2ubuntu2)
|
|
| kinetic |
Not vulnerable
(5.5.2-2ubuntu2)
|
|
| lunar |
Not vulnerable
(5.6.5-3ubuntu1)
|
|
| mantic |
Not vulnerable
(5.6.5-3ubuntu1)
|
|
| noble |
Not vulnerable
(5.6.5-3ubuntu1)
|
|
| trusty |
Does not exist
|
|
| upstream |
Needs triage
|
|
| xenial |
Does not exist
|
Severity score breakdown
| Parameter | Value |
|---|---|
| Base score | 7.5 |
| Attack vector | Network |
| Attack complexity | Low |
| Privileges required | None |
| User interaction | None |
| Scope | Unchanged |
| Confidentiality | None |
| Integrity impact | High |
| Availability impact | None |
| Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |