ID CVE-2020-11077
Summary 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.
References
Vulnerable Configurations
  • cpe:2.3:a:puma:puma:3.0.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.0.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.0.0:rc1:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.0.0:rc1:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.0.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.0.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.0.2:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.0.2:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.1.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.1.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.1.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.1.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.2.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.2.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.3.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.3.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.4.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.4.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.5.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.5.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.5.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.5.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.5.2:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.5.2:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.6.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.6.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.6.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.6.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.6.2:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.6.2:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.7.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.7.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.7.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.7.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.8.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.8.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.8.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.8.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.8.2:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.8.2:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.9.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.9.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.9.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.9.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.10.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.10.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.11.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.11.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.11.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.11.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.11.2:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.11.2:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.11.3:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.11.3:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.11.4:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.11.4:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.12.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.12.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.12.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.12.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.12.2:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.12.2:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.12.3:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.12.3:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.12.4:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.12.4:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:3.12.5:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:3.12.5:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:4.0.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:4.0.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:4.0.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:4.0.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:4.1.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:4.1.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:4.1.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:4.1.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:4.2.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:4.2.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:4.2.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:4.2.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:4.3.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:4.3.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:4.3.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:4.3.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:4.3.2:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:4.3.2:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:4.3.3:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:4.3.3:*:*:*:*:ruby:*:*
  • cpe:2.3:a:puma:puma:4.3.4:*:*:*:*:ruby:*:*
    cpe:2.3:a:puma:puma:4.3.4:*:*:*:*:ruby:*:*
CVSS
Base: 5.0 (as of 07-10-2020 - 13:15)
Impact:
Exploitability:
CWE CWE-444
CAPEC
  • HTTP Request Splitting
    HTTP Request Splitting (also known as HTTP Request Smuggling) is an attack pattern where an attacker attempts to insert additional HTTP requests in the body of the original (enveloping) HTTP request in such a way that the browser interprets it as one request but the web server interprets it as two. There are several ways to perform HTTP request splitting attacks. One way is to include double Content-Length headers in the request to exploit the fact that the devices parsing the request may each use a different header. Another way is to submit an HTTP request with a "Transfer Encoding: chunked" in the request header set with setRequestHeader to allow a payload in the HTTP Request that can be considered as another HTTP Request by a subsequent parsing entity. A third way is to use the "Double CR in an HTTP header" technique. There are also a few less general techniques targeting specific parsing vulnerabilities in certain web servers.
  • HTTP Request Smuggling
    HTTP Request Smuggling results from the discrepancies in parsing HTTP requests between HTTP entities such as web caching proxies or application firewalls. Entities such as web servers, web caching proxies, application firewalls or simple proxies often parse HTTP requests in slightly different ways. Under specific situations where there are two or more such entities in the path of the HTTP request, a specially crafted request is seen by two attacked entities as two different sets of requests. This allows certain requests to be smuggled through to a second entity without the first one realizing it.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
NONE PARTIAL NONE
cvss-vector via4 AV:N/AC:L/Au:N/C:N/I:P/A:N
refmap via4
confirm https://github.com/puma/puma/security/advisories/GHSA-w64w-qqph-5gxm
fedora FEDORA-2020-fe354f24e8
misc https://github.com/puma/puma/blob/master/History.md#434435-and-31253126--2020-05-22
suse
  • openSUSE-SU-2020:0990
  • openSUSE-SU-2020:1001
Last major update 07-10-2020 - 13:15
Published 22-05-2020 - 15:15
Last modified 07-10-2020 - 13:15
Back to Top