HTTP Smuggling via Transfer-Encoding Header 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 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-2398-1 | puma security update |
EUVD |
EUVD-2020-0447 | In Puma (RubyGem) before 4.3.4 and 3.12.5, an attacker could smuggle an HTTP response, by using an invalid transfer-encoding header. The problem has been fixed in Puma 3.12.5 and Puma 4.3.4. |
Github GHSA |
GHSA-x7jg-6pwg-fx5h | HTTP Smuggling via Transfer-Encoding Header in Puma |
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: 4.1% (4.088% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.