CVE-2019-16786 PUBLISHED

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.

EPSS 0.90% · 75.5th percentile

Risk Scores

EPSS Score
0.90%
75.5th percentile

Affected Products

VendorProductVersions
Ubuntu:16.04:LTSwaitress0, 0.8.9-2ubuntu1, 0.8.10-1
Ubuntu:18.04:LTSwaitress0, 1.0.1-1

Timeline

References

Open in Interactive Console →