CVE-2024-21647

rubygem-puma: This update for rubygem-puma fixes the following issues: Update to version 5.6.9. - CVE-2024-45614: improper header...

CVE-2024-21647 is fixed in 2 products on 1 platform, first by puma 3.12.4-1ubuntu2+esm1, released January 8, 2024. It is not reported as exploited. Patch Radar priority: High.

High
CVSS
7.5
high
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0096
61st percentile

This update for rubygem-puma fixes the following issues: Update to version 5.6.9. - CVE-2024-45614: improper header normalization allows for clients to clobber proxy set headers, which can lead to information leaks (bsc#1230848, fixed in an earlier update). - CVE-2024-21647: unbounded resource consumption due to invalid parsing of chunked encoding in HTTP/1.1 can lead to denial-of-service attacks (bsc#1218638, fixed in an earlier update) - CVE-2023-40175: incorrect behavior when parsing chunked transfer encoding bodies and zero-length Content-Length headers can lead to HTTP request smuggling attacks (bsc#1214425, fixed in an earlier update).

Where it's fixed

ProductFixed inFixReleased
Linux
puma · Debian 11.6 (bullseye) 4.3.8-1+deb11u3 DLA-3947-1 Nov 6, 2024
puma · Debian 12.15 (bookworm) 5.6.5-3+deb12u1 DEBIAN-CVE-2024-21647 Jan 8, 2024
puma · Debian 13.5 (trixie) 6.4.2-1 DEBIAN-CVE-2024-21647 Jan 8, 2024
puma · Debian 14 6.4.2-1 DEBIAN-CVE-2024-21647 Jan 8, 2024
puma · Ubuntu 20.04 LTS (focal) 3.12.4-1ubuntu2+esm1 puma 3.12.4-1ubuntu2+esm1 Jan 8, 2024
puma · Ubuntu 22.04.1 LTS (jammy) 5.5.2-2ubuntu2+esm1 puma 5.5.2-2ubuntu2+esm1 Jan 8, 2024
rubygem-puma · opensuse-leap 15.6 5.6.9-150600.18.3.1 SUSE-SU-2025:03467-1 Oct 7, 2025
rubygem-puma · sles 15.6 5.6.9-150600.18.3.1 SUSE-SU-2025:03467-1 Oct 7, 2025
rubygem-puma · sles 15.7 5.6.9-150600.18.3.1 SUSE-SU-2025:03467-1 Oct 7, 2025

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.