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.
History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published: 2019-12-20T23:00:20

Updated: 2024-08-05T01:24:48.017Z

Reserved: 2019-09-24T00:00:00

Link: CVE-2019-16786

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2019-12-20T23:15:11.277

Modified: 2023-11-07T03:05:44.287

Link: CVE-2019-16786

cve-icon Redhat

Severity : Important

Publid Date: 2019-12-20T00:00:00Z

Links: CVE-2019-16786 - Bugzilla