Puma's Keepalive Connections Causing Denial Of Service

CAO 7.5CVE-2021-29509 · GHSA-q28m-8xjw-8vr5 · Công bố 11/05/2021 · cập nhật 17/06/2026

Tóm tắt nhanh

CVE-2021-29509 là lỗ hổng mức CAO (CVSS 7.5) ảnh hưởng puma, puma (puma).
Xác suất bị khai thác trong 30 ngày tới (EPSS): 1.6%, cao hơn 75.8% các lỗ hổng khác.
Cách xử lý: cập nhật lên 5.3.1, 4.3.8 hoặc mới hơn.

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
puma RubyGems	`≥ 5.0.0, < 5.3.1< 4.3.8`	`5.3.14.3.8`
puma puma	`≥ 5.0.0, < 5.3.1< 4.3.8`	`5.3.14.3.8`

Mô tả

This vulnerability is related to CVE-2019-16770.

Impact

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.

Patches

This problem has been fixed in puma 4.3.8 and 5.3.1.

Workarounds

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. A git patch is available here for those using unsupported versions of Puma.

For more information

If you have any questions or comments about this advisory:

Open an issue in Puma.
To report problems with this fix or to report another vulnerability, see our security policy.

Acknowledgements

Thank you to @MSP-Greg, @wjordan and @evanphx for their review on this issue.

Thank you to @ioquatix for providing a modified fork of wrk which made debugging this issue much easier.

Mô tả của NVD

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.