NetSight
high7.1

CVE-2019-16786

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 th…

Impact

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.

Affected products

VendorProductAffected versions
AgendalessWaitress
before 1.3.1
OracleCommunications Cloud Native Core Network Function Cloud Native Environment
Version 1.10.0
DebianDebian Linux
Version 9.0
FedoraprojectFedora
Versions 30, 31
RedhatOpenstack
Version 15

Weakness classification

References