Количество 9
Количество 9
CVE-2019-16786
Waitress through version 1.3.1 would parse the Transfer-Encoding header and only look for a single string value, if that value was not chunked it would fall through and use the Content-Length header instead. According to the HTTP standard Transfer-Encoding should be a comma separated list, with the inner-most encoding first, followed by any further transfer codings, ending with chunked. Requests sent with: "Transfer-Encoding: gzip, chunked" would incorrectly get ignored, and the request would use a Content-Length header instead to determine the body size of the HTTP message. This could allow for Waitress to treat a single request as multiple requests in the case of HTTP pipelining. This issue is fixed in Waitress 1.4.0.
CVE-2019-16786
Waitress through version 1.3.1 would parse the Transfer-Encoding header and only look for a single string value, if that value was not chunked it would fall through and use the Content-Length header instead. According to the HTTP standard Transfer-Encoding should be a comma separated list, with the inner-most encoding first, followed by any further transfer codings, ending with chunked. Requests sent with: "Transfer-Encoding: gzip, chunked" would incorrectly get ignored, and the request would use a Content-Length header instead to determine the body size of the HTTP message. This could allow for Waitress to treat a single request as multiple requests in the case of HTTP pipelining. This issue is fixed in Waitress 1.4.0.
CVE-2019-16786
Waitress through version 1.3.1 would parse the Transfer-Encoding header and only look for a single string value, if that value was not chunked it would fall through and use the Content-Length header instead. According to the HTTP standard Transfer-Encoding should be a comma separated list, with the inner-most encoding first, followed by any further transfer codings, ending with chunked. Requests sent with: "Transfer-Encoding: gzip, chunked" would incorrectly get ignored, and the request would use a Content-Length header instead to determine the body size of the HTTP message. This could allow for Waitress to treat a single request as multiple requests in the case of HTTP pipelining. This issue is fixed in Waitress 1.4.0.
CVE-2019-16786
Waitress through version 1.3.1 would parse the Transfer-Encoding heade ...
GHSA-g2xc-35jw-c63p
HTTP Request Smuggling: Invalid Transfer-Encoding in Waitress
BDU:2022-05688
Уязвимость WSGI сервера для python Waitress, позволяющая нарушителю оказать воздействие на целостность данных
openSUSE-SU-2020:1922-1
Security update for python-waitress
openSUSE-SU-2020:1911-1
Security update for python-waitress
SUSE-SU-2020:3269-1
Security update for python-waitress
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
 | CVE-2019-16786 Waitress through version 1.3.1 would parse the Transfer-Encoding header and only look for a single string value, if that value was not chunked it would fall through and use the Content-Length header instead. According to the HTTP standard Transfer-Encoding should be a comma separated list, with the inner-most encoding first, followed by any further transfer codings, ending with chunked. Requests sent with: "Transfer-Encoding: gzip, chunked" would incorrectly get ignored, and the request would use a Content-Length header instead to determine the body size of the HTTP message. This could allow for Waitress to treat a single request as multiple requests in the case of HTTP pipelining. This issue is fixed in Waitress 1.4.0. | CVSS3: 7.1 | 1% Низкий | около 6 лет назад |
 | CVE-2019-16786 Waitress through version 1.3.1 would parse the Transfer-Encoding header and only look for a single string value, if that value was not chunked it would fall through and use the Content-Length header instead. According to the HTTP standard Transfer-Encoding should be a comma separated list, with the inner-most encoding first, followed by any further transfer codings, ending with chunked. Requests sent with: "Transfer-Encoding: gzip, chunked" would incorrectly get ignored, and the request would use a Content-Length header instead to determine the body size of the HTTP message. This could allow for Waitress to treat a single request as multiple requests in the case of HTTP pipelining. This issue is fixed in Waitress 1.4.0. | CVSS3: 7.1 | 1% Низкий | около 6 лет назад |
 | CVE-2019-16786 Waitress through version 1.3.1 would parse the Transfer-Encoding header and only look for a single string value, if that value was not chunked it would fall through and use the Content-Length header instead. According to the HTTP standard Transfer-Encoding should be a comma separated list, with the inner-most encoding first, followed by any further transfer codings, ending with chunked. Requests sent with: "Transfer-Encoding: gzip, chunked" would incorrectly get ignored, and the request would use a Content-Length header instead to determine the body size of the HTTP message. This could allow for Waitress to treat a single request as multiple requests in the case of HTTP pipelining. This issue is fixed in Waitress 1.4.0. | CVSS3: 7.1 | 1% Низкий | около 6 лет назад |
| CVE-2019-16786 Waitress through version 1.3.1 would parse the Transfer-Encoding heade ... | CVSS3: 7.1 | 1% Низкий | около 6 лет назад |
| GHSA-g2xc-35jw-c63p HTTP Request Smuggling: Invalid Transfer-Encoding in Waitress | CVSS3: 7.1 | 1% Низкий | около 6 лет назад |
 | BDU:2022-05688 Уязвимость WSGI сервера для python Waitress, позволяющая нарушителю оказать воздействие на целостность данных | CVSS3: 7.5 | 1% Низкий | около 6 лет назад |
 | openSUSE-SU-2020:1922-1 Security update for python-waitress | около 5 лет назад | ||
| openSUSE-SU-2020:1911-1 Security update for python-waitress | около 5 лет назад | ||
| SUSE-SU-2020:3269-1 Security update for python-waitress | около 5 лет назад |
Уязвимостей на страницу