CVE-2020-5247
rubygem-puma: attacker is able to use newline characters to insert malicious content (HTTP Response Splitting), this could lead to XSS
Overview
Description
In Puma (RubyGem) before 4.3.2 and before 3.12.3, if an application using Puma allows untrusted input in a response header, an attacker can use newline characters (i.e. CR, LF or/r, /n) to end the header and inject malicious content, such as additional headers or an entirely new response body. This vulnerability is known as HTTP Response Splitting. While not an attack in itself, response splitting is a vector for several other attacks, such as cross-site scripting (XSS). This is related to CVE-2019-16254, which fixed this vulnerability for the WEBrick Ruby web server. This has been fixed in versions 4.3.2 and 3.12.3 by checking all headers for line endings and rejecting headers with those characters.
Source: OX vulnerability database
Severity
7.5 · HIGH
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Weakness: CWE-113, CWE-74
Affected packages · 3
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| Bitnami | ruby | <2.3.1>=2.4.0, <2.4.8>=2.5.0, <2.5.7>=2.6.0, <2.6.5 | 2.3.12.4.82.5.72.6.5 |
| Bitnami | ruby-min | <2.3.1>=2.4.0, <2.4.8>=2.5.0, <2.5.7>=2.6.0, <2.6.5 | 2.3.12.4.82.5.72.6.5 |
| RubyGems | puma | <3.12.4>=4.0.0, <4.3.3 | 3.12.44.3.3~> 3.12.4 |
Open a package to see all its vulnerabilities.
Operating systems · 11 fixes
Red Hat 3 releases · 2 packages
| Release | Package | Fixed in |
|---|---|---|
| rubygem-puma +1 | wont fix | |
| 7 | rubygem-puma +1 | wont fix |
| 7 | rh-ror50-rubygem-puma +1 | wont fix |
| 8 | rubygem-puma +1 | wont fix |
debian 6 releases · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 10 | puma | 3.12.0-2+deb10u2 |
| 11 | puma | 3.12.4-1 |
| 12 | puma | 3.12.4-1 |
| 13 | puma | 3.12.4-1 |
| 14 | puma | 3.12.4-1 |
| 9 | puma | 3.6.0-1+deb9u2 |
echo 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| puma | 3.12.4-1 |
References
- access.redhat.com https://access.redhat.com/security/cve/CVE-2020-5247
- github.com https://github.com/puma/puma
- github.com https://github.com/puma/puma/commit/c36491756f68a9d6a8b3a49e7e5eb07fe6f1332f
- github.com https://github.com/puma/puma/security/advisories/GHSA-84j7-475p-hp8v
- github.com https://github.com/rubysec/ruby-advisory-db/blob/master/gems/puma/CVE-2020-5247.yml
- lists.debian.org https://lists.debian.org/debian-lts-announce/2022/05/msg00034.html
- lists.fedoraproject.org https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BMJ3CGZ3DLBJ5WUUKMI5ZFXFJQMXJZIK/
- lists.fedoraproject.org https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/DIHVO3CQMU7BZC7FCTSRJ33YDNS3GFPK/
- lists.fedoraproject.org https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/NJ3LL5F5QADB6LM46GXZETREAKZMQNRD/
- lists.fedoraproject.org https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BMJ3CGZ3DLBJ5WUUKMI5ZFXFJQMXJZIK
Show all 16 references
- lists.fedoraproject.org https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DIHVO3CQMU7BZC7FCTSRJ33YDNS3GFPK
- lists.fedoraproject.org https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NJ3LL5F5QADB6LM46GXZETREAKZMQNRD
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2020-5247
- owasp.org https://owasp.org/www-community/attacks/HTTP_Response_Splitting
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2020-5247
- www.ruby-lang.org https://www.ruby-lang.org/en/news/2019/10/01/http-response-splitting-in-webrick-cve-2019-16254
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.