ChainpumaRubyGems:puma
puma: successive fixes (2020–2024)
7 CVEs over 5 generations, 28 Feb 2020 to 8 Jan 2024.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2020-524728 Feb 2020 First in the chain
- CVE-2020-52492 Mar 2020 related to CVE-2020-5247
- CVE-2020-1107622 May 2020 next fix after CVE-2020-5249
- CVE-2021-4113612 Oct 2021 No direct link to an earlier CVE
- CVE-2022-2479030 Mar 2022 related to CVE-2020-5247related to CVE-2020-5249and 2 more
- CVE-2023-4017518 Aug 2023 related to CVE-2022-24790related to CVE-2020-11076
- CVE-2024-216478 Jan 2024 related to CVE-2023-40175related to CVE-2022-24790
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
CVEs in this family
Table view of the tree| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2020-5247 | 28 Feb 2020 | HTTP Response Splitting in Puma · fixed in 4.3.3 | First in chain | 21.6 |
| CVE-2020-5249 | 2 Mar 2020 | HTTP Response Splitting (Early Hints) in Puma · fixed in 4.3.3 | CVE-2020-5247 · related · High | 19.6 |
| CVE-2020-11076 | 22 May 2020 | HTTP Smuggling via Transfer-Encoding Header in Puma · fixed in 4.3.4 | CVE-2020-5249 · Next fix in the same package · Low | 28.4 |
| CVE-2021-41136 | 12 Oct 2021 | Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling') in puma · fixed in 5.5.1 | First in chain | 16.2 |
| CVE-2022-24790 | 30 Mar 2022 | HTTP Request Smuggling in puma · fixed in 5.6.4 | CVE-2020-5247 · related · Medium | 22.9 |
| CVE-2023-40175 | 18 Aug 2023 | Inconsistent Interpretation of HTTP Requests in puma · fixed in 6.3.1 | CVE-2022-24790 · related · High | 16.7 |
| CVE-2024-21647 | 8 Jan 2024 | HTTP Request/Response Smuggling in puma · fixed in 6.4.2 | CVE-2023-40175 · related · High | 16.4 |