CVE-2019-16789 (https://nvd.nist.gov/vuln/detail/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-16786 (https://nvd.nist.gov/vuln/detail/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-16785 (https://nvd.nist.gov/vuln/detail/CVE-2019-16785): 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.
CVE-2020-5236 (https://nvd.nist.gov/vuln/detail/CVE-2020-5236): 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.
@maintainer(s), ready for stabilisation?
arm stable
ppc stable
ppc64 stable
s390 stable
sparc stable
amd64 stable
* arm64 stable * ALLARCHES => x86, hppa stable --- @maintainer(s), please cleanup
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=96c5ad38d3d1e1c0e054d2924aad09d4fed212bd commit 96c5ad38d3d1e1c0e054d2924aad09d4fed212bd Author: Aaron Bauman <bman@gentoo.org> AuthorDate: 2020-06-20 01:34:54 +0000 Commit: Aaron Bauman <bman@gentoo.org> CommitDate: 2020-06-20 01:34:54 +0000 dev-python/waitress: drop vulnerable Bug: https://bugs.gentoo.org/717966 Signed-off-by: Aaron Bauman <bman@gentoo.org> dev-python/waitress/Manifest | 1 - dev-python/waitress/waitress-1.3.1.ebuild | 21 --------------------- 2 files changed, 22 deletions(-)
