A simple, fast, threaded, and highly concurrent HTTP 1.1 server for Ruby/Rack applications.
Security Fix(es):
Puma is a concurrent HTTP 1.1 server for Ruby/Rack applications. The fix for CVE-2019-16770 was incomplete. The original fix only protected existing connections that had already been accepted from having their requests starved by greedy persistent-connections saturating all threads in the same process. However, new connections may still be starved by greedy persistent-connections saturating all threads in all processes in the cluster. A puma server which received more concurrent keep-alive connections than the server had threads in its threadpool would service only a subset of connections, denying service to the unserved connections. This problem has been fixed in puma 4.3.8 and 5.3.1. Setting queue_requests False also fixes the issue. This is not advised when using puma without a reverse proxy, such as nginx or apache, because you will open yourself to slow client attacks (e.g. slowloris). The fix is very small and a git patch is available for those using unsupported versions of Puma.(CVE-2021-29509)
{
"severity": "High"
}{
"x86_64": [
"rubygem-puma-debugsource-3.12.6-2.oe1.x86_64.rpm",
"rubygem-puma-3.12.6-2.oe1.x86_64.rpm",
"rubygem-puma-debuginfo-3.12.6-2.oe1.x86_64.rpm"
],
"aarch64": [
"rubygem-puma-3.12.6-2.oe1.aarch64.rpm",
"rubygem-puma-debugsource-3.12.6-2.oe1.aarch64.rpm",
"rubygem-puma-debuginfo-3.12.6-2.oe1.aarch64.rpm"
],
"src": [
"rubygem-puma-3.12.6-2.oe1.src.rpm"
],
"noarch": [
"rubygem-puma-doc-3.12.6-2.oe1.noarch.rpm"
]
}