GHSA-x7jg-6pwg-fx5h CVE-2020-11076
HTTP Smuggling via Transfer-Encoding Header in Puma
- Severity
- 7.5 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 4.09%
- Chance of exploitation in the next 30 days. Higher than 90.72% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-444 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
- Fix
3.12.5- Upgrade puma to this version or later
Description
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
Affected versions
RubyGems
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
puma RubyGems → 3.12.5
- bundler
bundle update puma # Gemfile: gem "puma", ">= 3.12.5"
Severity breakdown
CVSS 3.1 7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
Weakness
CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
How to prevent it
- Implementation: Use a web server that employs a strict HTTP parsing procedure, such as Apache [REF-433].
- Implementation: Use only SSL communication.
- Implementation: Terminate the client session after each request.
- System Configuration: Turn all pages to non-cacheable.
References
Advisories
Packages
Other links
- github.com/puma/puma/security/advisories/GHSA-x7jg-6pwg-fx5h
- github.com/puma/puma/commit/f24d5521295a2152c286abb0a45a1e1e2bd275bd
- github.com/puma/puma/blob/master/History.md
- github.com/rubysec/ruby-advisory-db/blob/master/gems/puma/CVE-2020-11076.yml
- lists.debian.org/debian-lts-announce/2020/10/msg00009.html
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SKIY5…
- lists.opensuse.org/opensuse-security-announce/2020-07/msg00034.html
- lists.opensuse.org/opensuse-security-announce/2020-07/msg00038.html
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-2vqw-3mp8-cgmx Puma PROXY Protocol v1 Accepts Repeated Protocol Headers on Persistent Connections | High | Also affects puma |
| GHSA-qpgp-93vx-g8v8 Puma PROXY Protocol v1 Parser Allows Remote Memory Exhaustion | High | Also affects puma |
| GHSA-9hf4-67fc-4vf4 Puma's header normalization allows for client to clobber proxy set headers | Medium | Also affects puma |
| GHSA-c2f4-cvqm-65w2 Puma HTTP Request/Response Smuggling vulnerability | High | Also affects puma |
| GHSA-68xg-gqqm-vgj8 Puma HTTP Request/Response Smuggling vulnerability | Critical | Also affects puma |
| GHSA-h99w-9q5r-gjq9 Puma vulnerable to HTTP Request Smuggling | Critical | Also affects puma |
| GHSA-rmj8-8hhh-gv5h Puma used with Rails may lead to Information Exposure | High | Also affects puma |
| GHSA-48w2-rm65-62xx Puma with proxy which forwards LF characters as line endings could allow HTTP request smuggling | Low | Also affects puma |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor