Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling') in puma
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| puma | puma | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Satellite 6.11 for RHEL 7 | |||
| tfm-rubygem-puma-0:5.6.2-1.el7sat | cpe:/a:redhat:satellite:6.11::el7 | RHSA-2022:5498 | 2022-07-05T00:00:00Z |
| Red Hat Satellite 6.11 for RHEL 8 | |||
| rubygem-puma-0:5.6.2-1.el8sat | cpe:/a:redhat:satellite:6.11::el8 | RHSA-2022:5498 | 2022-07-05T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-3083-1 | puma security update |
Debian DSA |
DSA-5146-1 | puma security update |
EUVD |
EUVD-2021-2154 | Puma is a HTTP 1.1 server for Ruby/Rack applications. Prior to versions 5.5.1 and 4.3.9, using `puma` with a proxy which forwards HTTP header values which contain the LF character could allow HTTP request smugggling. A client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client. The only proxy which has this behavior, as far as the Puma team is aware of, is Apache Traffic Server. 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 vulnerability was patched in Puma 5.5.1 and 4.3.9. As a workaround, do not use Apache Traffic Server with `puma`. |
Github GHSA |
GHSA-48w2-rm65-62xx | Puma with proxy which forwards LF characters as line endings could allow HTTP request smuggling |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.2% (1.203% probability within 30 days)
Key SSVC decision points have not yet been added.