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.
The product does not properly control the allocation and maintenance of a limited resource.
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
| Link | Tags |
|---|---|
| https://github.com/puma/puma/security/advisories/GHSA-q28m-8xjw-8vr5 | third party advisory patch |
| https://gist.github.com/nateberkopec/4b3ea5676c0d70cbb37c82d54be25837 | third party advisory patch |
| https://github.com/puma/puma/security/policy | third party advisory |
| https://rubygems.org/gems/puma | product third party advisory |
| https://security.gentoo.org/glsa/202208-28 | third party advisory vendor advisory |
| https://lists.debian.org/debian-lts-announce/2022/08/msg00015.html | third party advisory mailing list |