Medium

HTTP Request Smuggling: Invalid Transfer-Encoding in Waitress

  • Disclosed: 20.12.2019
  • Updated: 11.10.2026 13:19

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:

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) waitress < 1.4.0 1.4.0

References

CVSS score 7.1/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N
Weakness (CWE)
CWE-444
Platform
Python (PyPI)
Package
waitress
Disclosed
20.12.2019
Updated
11.10.2026 13:19

Sources and licenses

OSV / GitHub Advisory Database - PYSEC-2019-137 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-g2xc-35jw-c63p - CC BY 4.0

Vulnerability history: waitress

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (10) in the archive
Total entries
10
First → latest
12.2019 10.2024
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Critical 2
  • High 4
  • Medium 4

Disclosures per year

  1. 2019: 5
  2. 2020: 1
  3. 2021: 0
  4. 2022: 2
  5. 2023: 0
  6. 2024: 2
  7. 2025: 0
  8. 2026: 0
Severity:
  1. High · 7.5 CVE-2022-24761 < 2.1.1 2.1.1
  2. HTTP Request Smuggling: Invalid Transfer-Encoding in Waitress this entry
    Medium · 7.1 CVE-2019-16786 < 1.4.0 1.4.0
  3. Critical · 7.5 CVE-2019-16792 < 1.4.0 1.4.0

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.