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.
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
| Link | Tags |
|---|---|
| https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/GVDHR2DNKCNQ7YQXISJ45NT4IQDX3LJ7/ | vendor advisory |
| https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LYEOTGWJZVKPRXX2HBNVIYWCX73QYPM5/ | vendor advisory |
| https://access.redhat.com/errata/RHSA-2020:0720 | third party advisory vendor advisory |
| https://www.oracle.com/security-alerts/cpuapr2022.html | third party advisory patch |
| https://docs.pylonsproject.org/projects/waitress/en/latest/#security-fixes | release notes vendor advisory |
| https://github.com/Pylons/waitress/security/advisories/GHSA-g2xc-35jw-c63p | third party advisory |
| https://github.com/Pylons/waitress/commit/f11093a6b3240fc26830b6111e826128af7771c3 | third party advisory patch |
| https://lists.debian.org/debian-lts-announce/2022/05/msg00011.html | third party advisory mailing list |