debian/waitress vulnerabilities

Latest debian/waitress CVEs

Newest publication first

1. DLA-3955-1 waitress - security update

   Published 2024-11-16

   Unknown

2. CVE-2024-49768 Waitress has request processing race condition in HTTP pipelining with invalid first request

   Published 2024-10-29

   Medium·CVSS 4.8 EPSS 0.49%

   Waitress is a Web Server Gateway Interface server for Python 2 and 3. A remote client may send a request that is exactly recv_bytes (defaults to 8192) long, followed by a secondary request using HTTP pipelining. When request lookahead is disabled (default) we won't read any more...

3. CVE-2024-49769 Waitress has a denial of service leading to high CPU usage/resource exhaustion

   Published 2024-10-29

   High·CVSS 7.5 EPSS 1.4%

   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 sock...

4. CVE-2022-31015 Uncaught Exception (due to a data race) leads to process termination in Waitress

   Published 2022-05-31

   Medium·CVSS 5.9 EPSS 1.5%

   Waitress is a Web Server Gateway Interface server for Python 2 and 3. Waitress versions 2.1.0 and 2.1.1 may terminate early due to a thread closing a socket while the main thread is about to call select(). This will lead to the main thread raising an exception that is not handled...

5. DSA-5138-1 waitress - security update

   Published 2022-05-17

   Unknown

6. DLA-3000-1 waitress - security update

   Published 2022-05-12

   Unknown

7. CVE-2022-24761 HTTP Request Smuggling in waitress

   Published 2022-03-17

   High·CVSS 7.5 EPSS 1.8%

   Waitress is a Web Server Gateway Interface server for Python 2 and 3. When using Waitress versions 2.1.0 and prior behind a proxy that does not properly validate the incoming HTTP request matches the RFC7230 standard, Waitress and the frontend proxy may disagree on where one requ...

8. CVE-2020-5236 Catastrophic backtracking in regex allows Denial of Service in Waitress

   Published 2020-02-04

   Medium·CVSS 6.5 EPSS 2.4%

   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%...

9. CVE-2019-16792 HTTP Request Smuggling: Content-Length Sent Twice in Waitress

   Published 2020-01-22

   High·CVSS 7.5 EPSS 2.0%

   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....

10. DLA-2056-1 waitress - security update

    Published 2020-01-01

    Unknown

11. CVE-2019-16789 HTTP Request Smuggling in Waitress: Invalid whitespace characters in headers

    Published 2019-12-26

    High·CVSS 8.2 EPSS 2.6%

    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 contain...

12. CVE-2019-16785 HTTP Request Smuggling: LF vs CRLF handling in Waitress

    Published 2019-12-20

    High·CVSS 7.5 EPSS 2.5%

    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...

13. CVE-2019-16786 HTTP Request Smuggling: Invalid Transfer-Encoding in Waitress

    Published 2019-12-20

    High·CVSS 7.5 EPSS 2.4%

    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 separ...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.