Homepage

HTTP Request Smuggling The advisory has been revoked - it doesn't affect any version of package rubygem-puma-debugsource  (opens in a new tab)

Threat Intelligence

EPSS
1.2% (66th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-RUBYGEMPUMADEBUGSOURCE-4416611
  • published26 Mar 2023
  • disclosed12 Oct 2021
Report a new vulnerability Found a mistake?

Introduced: 12 Oct 2021

CVE-2021-41136  (opens in a new tab)
CWE-444  (opens in a new tab)

Amendment

The Red Hat security team deemed this advisory irrelevant for RHEL:8.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rubygem-puma-debugsource package and not the rubygem-puma-debugsource package as distributed by RHEL.

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.