HTTP Request Smuggling: Invalid Transfer-Encoding in Waitress
Published 20 Dec 2019 · Updated 8 Jul 2026
Is your project on an affected waitress?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <1.4.0
- Fixed in
- 1.4.0
pip install 'waitress>=1.4.0'Details
Impact
Waitress 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.
Patches
This issue is fixed in Waitress 1.4.0. This brings a range of changes to harden Waitress against potential HTTP request confusions, and may change the behaviour of Waitress behind non-conformist proxies.
Waitress will now return a 501 Not Implemented error if the Transfer-Encoding is not chunked or contains multiple elements. Waitress does not support any transfer codings such as gzip or deflate.
The Pylons Project recommends upgrading as soon as possible, while validating that the changes in Waitress don't cause any changes in behavior.
Workarounds
Various reverse proxies may have protections against sending potentially bad HTTP requests to the backend, and or hardening against potential issues like this. If the reverse proxy doesn't use HTTP/1.1 for connecting to the backend issues are also somewhat mitigated, as HTTP pipelining does not exist in HTTP/1.0 and Waitress will close the connection after every single request (unless the Keep Alive header is explicitly sent... so this is not a fool proof security method).
Issues/more security issues:
- open an issue at https://github.com/Pylons/waitress/issues (if not sensitive or security related)
- email the Pylons Security mailing list: pylons-project-security@googlegroups.com (if security related)
Is GHSA-g2xc-35jw-c63p in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected waitress, and gives you the command that fixes it.
More advisories for waitress
- CriticalCVE-2024-49768Waitress has request processing race condition in HTTP pipelining with invalid first request · 29 Oct 2024
- HighCVE-2024-49769Waitress vulnerable to DoS leading to high CPU usage/resource exhaustion · 29 Oct 2024
- HighCVE-2022-31015Uncaught Exception (due to a data race) leads to process termination in Waitress · 2 Jun 2022
- HighCVE-2022-24761HTTP Request Smuggling in waitress · 18 Mar 2022
- MediumCVE-2020-5236Catastrophic backtracking in regex allows Denial of Service in Waitress · 4 Feb 2020
- MediumCVE-2019-16789HTTP Request Smuggling in Waitress: Invalid whitespace characters in headers (Follow-up) · 6 Jan 2020
References
- Linkgithub.com/Pylons/waitress/security/advisories/GHSA-g2xc-35jw-c63p
- Advisorynvd.nist.gov/vuln/detail/CVE-2019-16786
- Linkgithub.com/Pylons/waitress/commit/f11093a6b3240fc26830b6111e826128af7771c3
- Linkaccess.redhat.com/errata/RHSA-2020:0720
- Linkdocs.pylonsproject.org/projects/waitress/en/latest/#security-fixes
- Packagegithub.com/Pylons/waitress
- Linkgithub.com/pypa/advisory-database/tree/main/vulns/waitress/PYSEC-2019-137.yaml
- Linklists.debian.org/debian-lts-announce/2022/05/msg00011.html
- Linklists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GVDHR2DNKCNQ7YQXISJ45NT4IQDX3LJ7
- Linklists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LYEOTGWJZVKPRXX2HBNVIYWCX73QYPM5
- Linkwww.oracle.com/security-alerts/cpuapr2022.html
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.