CVE-2020-11076
CVE-2020-11076 — HTTP Smuggling via Transfer-Encoding Header in Puma
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.
Published Updated Sources: cvelistV5, GitHub_M
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Exploit code
public exploit, none observed
EPSS
4%
chance of exploitation in 30 days
CVSS base
7.5
HIGH
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.1 | HIGH | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-444
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Indexed by
References
7 on the record
- github.com/puma/puma/security/advisories/GHSA-x7jg-6pwg-fx5h
x_refsource_CONFIRM
- github.com/puma/puma/blob/master/History.md#434435-and-31253126--2020-05-22
x_refsource_MISC
- github.com/puma/puma/commit/f24d5521295a2152c286abb0a45a1e1e2bd275bd
x_refsource_MISC
- lists.opensuse.org/opensuse-security-announce/2020-07/msg00034.html
vendor-advisory, x_refsource_SUSE
- lists.opensuse.org/opensuse-security-announce/2020-07/msg00038.html
vendor-advisory, x_refsource_SUSE
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SKIY5H67GJIGJL6SMFWFLUQQQR3EMVPR/
vendor-advisory, x_refsource_FEDORA
- lists.debian.org/debian-lts-announce/2020/10/msg00009.html
mailing-list, x_refsource_MLIST
Elsewhere on this site
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.