An update for rubygem-puma is now available for openEuler-20.03-LTS-SP1 Security Advisory openeuler-security@openeuler.org openEuler security committee openEuler-SA-2021-1169 Final 1.0 1.0 2021-05-06 Initial 2021-05-06 2021-05-06 openEuler SA Tool V1.0 2021-05-06 rubygem-puma security update An update for rubygem-puma is now available for openEuler-20.03-LTS-SP1. Security Fix(es): 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) 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) An update for rubygem-puma is now available for openEuler-20.03-LTS-SP1. openEuler Security has rated this update as having a security impact of high. A Common Vunlnerability Scoring System(CVSS)base score,which gives a detailed severity rating, is available for each vulnerability from the CVElink(s) in the References section. High rubygem-puma https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1169 https://openeuler.org/en/security/cve/detail.html?id=CVE-2020-11076 https://openeuler.org/en/security/cve/detail.html?id=CVE-2020-11077 https://nvd.nist.gov/vuln/detail/CVE-2020-11076 https://nvd.nist.gov/vuln/detail/CVE-2020-11077 openEuler-20.03-LTS-SP1 rubygem-puma-debuginfo-3.12.6-1.oe1.aarch64.rpm rubygem-puma-3.12.6-1.oe1.aarch64.rpm rubygem-puma-debugsource-3.12.6-1.oe1.aarch64.rpm rubygem-puma-doc-3.12.6-1.oe1.noarch.rpm rubygem-puma-3.12.6-1.oe1.src.rpm rubygem-puma-debugsource-3.12.6-1.oe1.x86_64.rpm rubygem-puma-3.12.6-1.oe1.x86_64.rpm rubygem-puma-debuginfo-3.12.6-1.oe1.x86_64.rpm 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. 2021-05-06 CVE-2020-11076 openEuler-20.03-LTS-SP1 High 7.5 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N rubygem-puma security update 2021-05-06 https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1169 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. 2021-05-06 CVE-2020-11077 openEuler-20.03-LTS-SP1 High 7.5 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N rubygem-puma security update 2021-05-06 https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1169