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 [-]
|
Configuration 3 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Gluster Storage 3.5 for RHEL 7 | |||
| rubygem-puma-0:4.3.12-1.el7rhgs | cpe:/a:redhat:storage:3.5:wa:el7 | RHSA-2023:1486 | 2023-03-28T00:00:00Z |
| Red Hat Satellite 6.9 for RHEL 7 | |||
| tfm-rubygem-puma-0:4.3.12-1.el7sat | cpe:/a:redhat:satellite:6.9::el7 | RHSA-2022:8532 | 2022-11-17T00: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-2022-1439 | Puma is a simple, fast, multi-threaded, parallel HTTP 1.1 server for Ruby/Rack applications. When using Puma behind a proxy that does not properly validate that the incoming HTTP request matches the RFC7230 standard, Puma and the frontend proxy may disagree on where a request starts and ends. This would allow requests to be smuggled via the front-end proxy to Puma. The vulnerability has been fixed in 5.6.4 and 4.3.12. Users are advised to upgrade as soon as possible. Workaround: when deploying a proxy in front of Puma, turning on any and all functionality to make sure that the request matches the RFC7230 standard. |
Github GHSA |
GHSA-h99w-9q5r-gjq9 | Puma vulnerable to HTTP Request Smuggling |
Ubuntu USN |
USN-6682-1 | Puma vulnerabilities |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 2.2% (2.191% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|