| Affected_by_vulnerabilities |
| 0 |
| url |
VCID-2tuq-pc83-cqe8 |
| vulnerability_id |
VCID-2tuq-pc83-cqe8 |
| summary |
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. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2019-16786, GHSA-g2xc-35jw-c63p, PYSEC-2019-137
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-2tuq-pc83-cqe8 |
|
| 1 |
| url |
VCID-3664-qefb-hkct |
| vulnerability_id |
VCID-3664-qefb-hkct |
| summary |
Waitress through version 1.3.1 allows request smuggling by sending the Content-Length header twice. Waitress would header fold a double Content-Length header and due to being unable to cast the now comma separated value to an integer would set the Content-Length to 0 internally. If two Content-Length headers are sent in a single request, Waitress would treat the request as having no body, thereby treating the body of the request as a new request in HTTP pipelining. This issue is fixed in Waitress 1.4.0. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2019-16792, GHSA-4ppp-gpcr-7qf6, GHSA-j7j6-7hfx-5522, PYSEC-2020-178
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-3664-qefb-hkct |
|
| 2 |
| url |
VCID-5g9e-fz5j-5fg6 |
| vulnerability_id |
VCID-5g9e-fz5j-5fg6 |
| summary |
Waitress version 1.4.2 allows a DOS attack When waitress receives a header that contains invalid characters. When a header like "Bad-header: xxxxxxxxxxxxxxx\x10" is received, it will cause the regular expression engine to catastrophically backtrack causing the process to use 100% CPU time and blocking any other interactions. This allows an attacker to send a single request with an invalid header and take the service offline. This issue was introduced in version 1.4.2 when the regular expression was updated to attempt to match the behaviour required by errata associated with RFC7230. The regular expression that is used to validate incoming headers has been updated in version 1.4.3, it is recommended that people upgrade to the new version of Waitress as soon as possible. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2020-5236, GHSA-73m2-3pwg-5fgc, PYSEC-2020-155
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-5g9e-fz5j-5fg6 |
|
| 3 |
| url |
VCID-9gra-5w8b-mfa2 |
| vulnerability_id |
VCID-9gra-5w8b-mfa2 |
| summary |
Waitress through version 1.3.1 implemented a "MAY" part of the RFC7230 which states: "Although the line terminator for the start-line and header fields is the sequence CRLF, a recipient MAY recognize a single LF as a line terminator and ignore any preceding CR." Unfortunately if a front-end server does not parse header fields with an LF the same way as it does those with a CRLF it can lead to the front-end and the back-end server parsing the same HTTP message in two different ways. This can lead to a potential for HTTP request smuggling/splitting whereby Waitress may see two requests while the front-end server only sees a single HTTP message. This issue is fixed in Waitress 1.4.0. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2019-16785, GHSA-pg36-wpm5-g57p, PYSEC-2019-136
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-9gra-5w8b-mfa2 |
|
| 4 |
|
| 5 |
| url |
VCID-ujpr-gc5n-s3bc |
| vulnerability_id |
VCID-ujpr-gc5n-s3bc |
| summary |
Waitress is a Web Server Gateway Interface server for Python 2 and 3. When a remote client closes the connection before waitress has had the opportunity to call getpeername() waitress won't correctly clean up the connection leading to the main thread attempting to write to a socket that no longer exists, but not removing it from the list of sockets to attempt to process. This leads to a busy-loop calling the write function. A remote attacker could run waitress out of available sockets with very little resources required. Waitress 3.0.1 contains fixes that remove the race condition. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2024-49769, GHSA-3f84-rpwh-47g6, PYSEC-2024-211
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-ujpr-gc5n-s3bc |
|
| 6 |
| url |
VCID-zd7n-85nm-93cm |
| vulnerability_id |
VCID-zd7n-85nm-93cm |
| summary |
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. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2019-16789, GHSA-968f-66r5-5v74, PYSEC-2019-138
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-zd7n-85nm-93cm |
|
|
|---|