همهٔ گزارش‌ها
متوسط

HTTP Smuggling via Transfer-Encoding Header in Puma

متن اصلی

نسخه‌های متأثر

نسخه‌های متأثر
نامشخص
نسخهٔ اصلاح‌شده
اعلام نشده
نسخه‌های متأثر
نامشخص
نسخهٔ اصلاح‌شده
اعلام نشده
RubyGemspuma
نسخه‌های متأثر
< 3.12.6
نسخهٔ اصلاح‌شده
3.12.6
RubyGemspuma
نسخه‌های متأثر
>= 4.0.0, < 4.3.5
نسخهٔ اصلاح‌شده
4.3.5

بهره‌برداری

CVE-2020-11077

احتمال بهره‌برداری در ۳۰ روز آینده: 2.88%

FIRST EPSS · ۱۴۰۵/۰۸/۲۷

شرح آسیب‌پذیری

Impact

This is a similar but different vulnerability to the one patched in 3.12.5 and 4.3.4.

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.

Patches

The problem has been fixed in Puma 3.12.6 and Puma 4.3.5.

For more information

If you have any questions or comments about this advisory:

پیوندها