First published: Tue Oct 12 2021(Updated: )
Puma is a HTTP 1.1 server for Ruby/Rack applications. Prior to versions 5.5.1 and 4.3.9, using `puma` with a proxy which forwards HTTP header values which contain the LF character could allow HTTP request smugggling. A client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client. The only proxy which has this behavior, as far as the Puma team is aware of, is Apache Traffic Server. 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 vulnerability was patched in Puma 5.5.1 and 4.3.9. As a workaround, do not use Apache Traffic Server with `puma`.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Puma Puma | <=4.3.8 | |
Puma Puma | >=5.0.0<=5.5.0 | |
Debian Debian Linux | =10.0 | |
Debian Debian Linux | =11.0 | |
debian/puma | <=3.12.0-2+deb10u2<=4.3.8-1 | 3.12.0-2+deb10u3 4.3.8-1+deb11u2 5.6.5-3 5.6.7-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-41136 is a vulnerability in the Puma server that allows HTTP request smuggling.
The severity of CVE-2021-41136 is low.
CVE-2021-41136 affects Puma versions prior to 5.5.1 and 4.3.9.
CVE-2021-41136 can be exploited by using a proxy that forwards HTTP header values containing the LF character.
To fix CVE-2021-41136, upgrade to Puma version 5.5.1 or 4.3.9, depending on your current version.