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
2.88% (87th 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-4403621
  • published26 Mar 2023
  • disclosed21 May 2020
Report a new vulnerability Found a mistake?

Introduced: 21 May 2020

CVE-2020-11077  (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.

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.