CVE-2020-110776.8MediumCWE-444

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

puma

Fixed in 4.3.5 · Affected: puma before 4.3.5 · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

2.9%probability of exploitation in the next 30 days

87th percentile

050100

Higher than 87% of scored CVEs

6.8MediumCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

puma · puma< 3.12.6; >= 4.0.0, < 4.3.5

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Inconsistent Interpretation of HTTP Requests · Injection and Smuggling
Vendor: puma
Published: May 2020
Band: Possible (1 to 10%), May 2020

CoverageNo articles yet

No CyberSIXT article names CVE-2020-11077 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.