CVE-2020-11077

HTTP Smuggling via Transfer-Encoding Header in Puma

Published May 22, 2020 CVSS 3.1 · 6.8 Medium EPSS 2.9% KEV · Not listed
Description
In Puma (RubyGem) before 4.3.5 and 3.12.6, a client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client. 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 is a similar but different vulnerability from CVE-2020-11076. The problem has been fixed in Puma 3.12.6 and Puma 4.3.5.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-2398-1 puma security update
EUVD EUVD EUVD-2020-0445 In Puma (RubyGem) before 4.3.5 and 3.12.6, a client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client. 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 is a similar but different vulnerability from CVE-2020-11076. The problem has been fixed in Puma 3.12.6 and Puma 4.3.5.
Github GHSA Github GHSA GHSA-w64w-qqph-5gxm HTTP Smuggling via Transfer-Encoding Header in Puma
Ubuntu USN Ubuntu USN USN-6682-1 Puma vulnerabilities
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 4, 2024, 11:21 AM
Reserved
Mar 30, 2020, 12:00 AM
Status
Modified
Published
May 22, 2020, 3:15 PM
Modified
Jun 17, 2026, 2:49 AM
Severity
Moderate
Public date
May 21, 2020, 12:00 AM