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

Published May 22, 2020
·
Updated

Impact

By using an invalid transfer-encoding header, an attacker could smuggle an HTTP response.

Originally reported by @ZeddYu, who has our thanks for the detailed report.

Patches

The problem has been fixed in Puma 3.12.5 and Puma 4.3.4.

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.4 and 3.12.5, an attacker could smuggle an HTTP response, by using an invalid transfer-encoding header. The problem has been fixed in Puma 3.12.5 and Puma 4.3.4.

Ubuntu

Affected Software

8 affected componentsFixes available
rubygems/puma>=4.0.0<4.3.4
4.3.4
rubygems/puma<3.12.5
3.12.5
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

Event History

May 22, 2020
CVE Published
via Ubuntu·12:00 AM
CVE Published
via MITRE·02:50 PM
Data Sourced
via MITRE·02:50 PM
DescriptionSeverityWeakness
Advisory Published
02:55 PM
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 vulnerability ID?

The vulnerability ID is CVE-2020-11076.

2

What is the severity of CVE-2020-11076?

The severity of CVE-2020-11076 is high, with a severity value of 7.5.

3

How can an attacker exploit CVE-2020-11076?

An attacker can exploit CVE-2020-11076 by using an invalid transfer-encoding header to smuggle an HTTP response.

4

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

Puma versions 3.0.0 to 3.12.5 and 4.0.0 to 4.3.4 are affected by CVE-2020-11076.

5

How can I fix CVE-2020-11076?

You can fix CVE-2020-11076 by updating Puma to version 3.12.5 or 4.3.4, depending on the version you are currently using.

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