VYPR

PyPI package

waitress

pkg:pypi/waitress

Vulnerabilities (9)

  • CVE-2024-49769HigOct 29, 2024
    affected < 3.0.1fixed 3.0.1

    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

  • CVE-2024-49768CriOct 29, 2024
    affected >= 2.0.0, < 3.0.1fixed 3.0.1

    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

  • CVE-2022-31015MedMay 31, 2022
    affected >= 2.1.0, < 2.1.2fixed 2.1.2

    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

  • CVE-2022-24761HigMar 17, 2022
    affected < 2.1.1fixed 2.1.1

    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

  • CVE-2020-5236MedFeb 4, 2020
    affected >= 1.4.2, < 1.4.3fixed 1.4.3

    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%

  • CVE-2019-16792HigJan 22, 2020
    affected < 1.4.0fixed 1.4.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.

  • CVE-2019-16789HigDec 26, 2019
    affected < 1.4.2fixed 1.4.2

    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

  • CVE-2019-16786HigDec 20, 2019
    affected < 1.4.0fixed 1.4.0

    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

  • CVE-2019-16785HigDec 20, 2019
    affected < 1.4.0fixed 1.4.0

    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