CVE-2020-11077: HTTP Smuggling via Transfer-Encoding Header in Puma

Published May 22, 2020
·
Updated

Impact This is a similar but different vulnerability to the one patched in 3.12.5 and 4.3.4.

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.

Patches

The problem has been fixed in Puma 3.12.6 and Puma 4.3.5.

For more information

If you have any questions or comments about this advisory:

Open an issue in Puma See our security policy

Other sources

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.

Ubuntu

Affected Software

10 affected componentsFixes available
rubygems/puma>=4.0.0<4.3.5
4.3.5
rubygems/puma<3.12.6
3.12.6
debian/puma
3.12.0-2+deb10u23.12.0-2+deb10u34.3.8-14.3.8-1+deb11u25.6.5-36.4.2-4
ubuntu/puma<3.12.4-1ubuntu2+
3.12.4-1ubuntu2+
Puma Puma Ruby>=3.0.0<3.12.6
Puma Puma Ruby>=4.0.0<4.3.5
Fedoraproject Fedora=33
Debian Debian Linux=9.0
openSUSE Leap=15.1
openSUSE Leap=15.2

Event History

May 22, 2020
CVE Published
via Ubuntu·12:00 AM
Advisory Published
02:55 PM
CVE Published
via MITRE·02:55 PM
Data Sourced
via MITRE·02:55 PM
DescriptionSeverityWeakness
Mar 7, 2024
Data Sourced
via Launchpad·04:38 PM
Description

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the impact of CVE-2020-11077?

This vulnerability allows a client to smuggle a request through a proxy, causing the proxy to send a response back to another unknown client.

2

Which versions of Puma are affected by CVE-2020-11077?

Puma versions 4.0.0 to 4.3.5 and versions 3.12.6 and below are affected.

3

What is the severity of CVE-2020-11077?

The severity of this vulnerability is rated as medium with a CVSS score of 6.8.

4

How can I fix CVE-2020-11077?

To fix this vulnerability, update Puma to version 4.3.5 or version 3.12.6.

5

Where can I find more information about CVE-2020-11077?

More information about CVE-2020-11077 can be found at the following references: [GitHub Advisory](https://github.com/puma/puma/security/advisories/GHSA-w64w-qqph-5gxm), [Puma History](https://github.com/puma/puma/blob/master/History.md#434435-and-31253126--2020-05-22), and [NVD](https://nvd.nist.gov/vuln/detail/CVE-2020-11077).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203