First published: Tue May 11 2021(Updated: )
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.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Puma Puma | <4.3.8 | |
Puma Puma | >=5.0.0<5.3.1 | |
Debian Debian Linux | =10.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-29509 is a vulnerability in the Puma HTTP server that allows greedy persistent connections to saturate all threads in the same process, resulting in denial-of-service (DoS) conditions.
The severity of CVE-2021-29509 is high, with a CVSS score of 7.5.
CVE-2021-29509 affects Puma versions up to and excluding 4.3.8 and versions up to and excluding 5.3.1.
To fix CVE-2021-29509, update your Puma installation to version 4.3.8 or higher for versions below 5.0.0, or version 5.3.1 or higher for versions between 5.0.0 and 5.3.1.
You can find more information about CVE-2021-29509 on the Red Hat Security Advisory page: https://access.redhat.com/security/cve/CVE-2019-16770