Security update for rubygem-puma SUSE Patch security@suse.de SUSE Security Team SUSE-SU-2020:2060-1 Final 1 1 2020-07-28T15:54:20Z current 2020-07-28T15:54:20Z 2020-07-28T15:54:20Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z Security update for rubygem-puma This update for rubygem-puma fixes the following issues: - Add patches for disabling TLSv1.0 and TLSv1.1 (jsc#SLE-6965): - Add CVE-2020-11077.patch (bsc#1172175, CVE-2020-11077) - Add CVE-2020-11076.patch (bsc#1172176, CVE-2020-11076) - Add CVE-2020-5247.patch (bsc#1165402) 'Fixes a problem where we were not splitting newlines in headers according to Rack spec' The patch is reduced compared to the upstream version, which was patching also the parts that are not implemented in our old Puma version. This applies to unit test as well. - Add CVE-2019-16770.patch (bsc#1158675, SOC-10999, CVE-2019-16770) This patch fixes a DoS vulnerability a malicious client could use to block a large amount of threads. The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). SUSE-2020-2060,SUSE-OpenStack-Cloud-6-LTSS-2020-2060 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://www.suse.com/support/update/announcement/2020/suse-su-20202060-1/ Link for SUSE-SU-2020:2060-1 https://lists.suse.com/pipermail/sle-security-updates/2020-July/007189.html E-Mail link for SUSE-SU-2020:2060-1 https://www.suse.com/support/security/rating/ SUSE Security Ratings https://bugzilla.suse.com/1158675 SUSE Bug 1158675 https://bugzilla.suse.com/1165402 SUSE Bug 1165402 https://bugzilla.suse.com/1172175 SUSE Bug 1172175 https://bugzilla.suse.com/1172176 SUSE Bug 1172176 https://www.suse.com/security/cve/CVE-2019-16770/ SUSE CVE CVE-2019-16770 page https://www.suse.com/security/cve/CVE-2020-11076/ SUSE CVE CVE-2020-11076 page https://www.suse.com/security/cve/CVE-2020-11077/ SUSE CVE CVE-2020-11077 page https://www.suse.com/security/cve/CVE-2020-5247/ SUSE CVE CVE-2020-5247 page SUSE OpenStack Cloud 6-LTSS ruby2.1-rubygem-puma-2.16.0-4.3.1 ruby2.1-rubygem-puma-doc-2.16.0-4.3.1 ruby2.1-rubygem-puma-2.16.0-4.3.1 as a component of SUSE OpenStack Cloud 6-LTSS In Puma before versions 3.12.2 and 4.3.1, a poorly-behaved client could use keepalive requests to monopolize Puma's reactor and create a denial of service attack. If more keepalive connections to Puma are opened than there are threads available, additional connections will wait permanently if the attacker sends requests frequently enough. This vulnerability is patched in Puma 4.3.1 and 3.12.2. CVE-2019-16770 SUSE OpenStack Cloud 6-LTSS:ruby2.1-rubygem-puma-2.16.0-4.3.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2020/suse-su-20202060-1/ https://www.suse.com/security/cve/CVE-2019-16770.html CVE-2019-16770 https://bugzilla.suse.com/1158675 SUSE Bug 1158675 https://bugzilla.suse.com/1188527 SUSE Bug 1188527 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. CVE-2020-11076 SUSE OpenStack Cloud 6-LTSS:ruby2.1-rubygem-puma-2.16.0-4.3.1 moderate To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2020/suse-su-20202060-1/ https://www.suse.com/security/cve/CVE-2020-11076.html CVE-2020-11076 https://bugzilla.suse.com/1172175 SUSE Bug 1172175 https://bugzilla.suse.com/1172176 SUSE Bug 1172176 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. CVE-2020-11077 SUSE OpenStack Cloud 6-LTSS:ruby2.1-rubygem-puma-2.16.0-4.3.1 moderate To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2020/suse-su-20202060-1/ https://www.suse.com/security/cve/CVE-2020-11077.html CVE-2020-11077 https://bugzilla.suse.com/1172175 SUSE Bug 1172175 https://bugzilla.suse.com/1172176 SUSE Bug 1172176 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. CVE-2020-5247 SUSE OpenStack Cloud 6-LTSS:ruby2.1-rubygem-puma-2.16.0-4.3.1 moderate To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2020/suse-su-20202060-1/ https://www.suse.com/security/cve/CVE-2020-5247.html CVE-2020-5247 https://bugzilla.suse.com/1165402 SUSE Bug 1165402 https://bugzilla.suse.com/1165524 SUSE Bug 1165524