Поиск уязвимостей
Количество 27
Количество 27
CVE-2019-16789
In Waitress through version 1.4.0, if a proxy server is used in front of waitress, an invalid request may be sent by an attacker that bypasses the front-end and is parsed differently by waitress leading to a potential for HTTP request smuggling. Specially crafted requests containing special whitespace characters in the Transfer-Encoding header would get parsed by Waitress as being a chunked request, but a front-end server would use the Content-Length instead as the Transfer-Encoding header is considered invalid due to containing invalid characters. If a front-end server does HTTP pipelining to a backend Waitress server this could lead to HTTP request splitting which may lead to potential cache poisoning or unexpected information disclosure. This issue is fixed in Waitress 1.4.1 through more strict HTTP field validation.
CVE-2019-16789
In Waitress through version 1.4.0, if a proxy server is used in front of waitress, an invalid request may be sent by an attacker that bypasses the front-end and is parsed differently by waitress leading to a potential for HTTP request smuggling. Specially crafted requests containing special whitespace characters in the Transfer-Encoding header would get parsed by Waitress as being a chunked request, but a front-end server would use the Content-Length instead as the Transfer-Encoding header is considered invalid due to containing invalid characters. If a front-end server does HTTP pipelining to a backend Waitress server this could lead to HTTP request splitting which may lead to potential cache poisoning or unexpected information disclosure. This issue is fixed in Waitress 1.4.1 through more strict HTTP field validation.
CVE-2019-16789
In Waitress through version 1.4.0, if a proxy server is used in front ...
GHSA-4ppp-gpcr-7qf6
HTTP Request Smuggling: Content-Length Sent Twice in Waitress
BDU:2022-05828
Уязвимость WSGI сервера для python Waitress, связанная с недостатками обработки HTTP-запросов, позволяющая нарушителю оказать воздействие на целостность данных
GHSA-968f-66r5-5v74
HTTP Request Smuggling in Waitress: Invalid whitespace characters in headers (Follow-up)
BDU:2022-05832
Уязвимость WSGI сервера для python Waitress, связанная с недостатками обработки HTTP-запросов, позволяющая нарушителю получить доступ к конфиденциальным данным и нарушить их целостность
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
 | CVE-2019-16789 In Waitress through version 1.4.0, if a proxy server is used in front of waitress, an invalid request may be sent by an attacker that bypasses the front-end and is parsed differently by waitress leading to a potential for HTTP request smuggling. Specially crafted requests containing special whitespace characters in the Transfer-Encoding header would get parsed by Waitress as being a chunked request, but a front-end server would use the Content-Length instead as the Transfer-Encoding header is considered invalid due to containing invalid characters. If a front-end server does HTTP pipelining to a backend Waitress server this could lead to HTTP request splitting which may lead to potential cache poisoning or unexpected information disclosure. This issue is fixed in Waitress 1.4.1 through more strict HTTP field validation. | CVSS3: 8.2 | 3% Низкий | почти 7 лет назад |
 | CVE-2019-16789 In Waitress through version 1.4.0, if a proxy server is used in front of waitress, an invalid request may be sent by an attacker that bypasses the front-end and is parsed differently by waitress leading to a potential for HTTP request smuggling. Specially crafted requests containing special whitespace characters in the Transfer-Encoding header would get parsed by Waitress as being a chunked request, but a front-end server would use the Content-Length instead as the Transfer-Encoding header is considered invalid due to containing invalid characters. If a front-end server does HTTP pipelining to a backend Waitress server this could lead to HTTP request splitting which may lead to potential cache poisoning or unexpected information disclosure. This issue is fixed in Waitress 1.4.1 through more strict HTTP field validation. | CVSS3: 8.2 | 3% Низкий | почти 7 лет назад |
| CVE-2019-16789 In Waitress through version 1.4.0, if a proxy server is used in front ... | CVSS3: 8.2 | 3% Низкий | почти 7 лет назад |
| GHSA-4ppp-gpcr-7qf6 HTTP Request Smuggling: Content-Length Sent Twice in Waitress | 2% Низкий | почти 7 лет назад | |
 | BDU:2022-05828 Уязвимость WSGI сервера для python Waitress, связанная с недостатками обработки HTTP-запросов, позволяющая нарушителю оказать воздействие на целостность данных | CVSS3: 7.5 | 2% Низкий | почти 7 лет назад |
| GHSA-968f-66r5-5v74 HTTP Request Smuggling in Waitress: Invalid whitespace characters in headers (Follow-up) | CVSS3: 7.1 | 3% Низкий | почти 7 лет назад |
| BDU:2022-05832 Уязвимость WSGI сервера для python Waitress, связанная с недостатками обработки HTTP-запросов, позволяющая нарушителю получить доступ к конфиденциальным данным и нарушить их целостность | CVSS3: 8.2 | 3% Низкий | почти 7 лет назад |
Уязвимостей на страницу