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.
{
"unresolved_ranges": [
{
"cpes": [
"cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*"
],
"vendor_product": "debian:debian_linux",
"source": "CPE_STRING",
"extracted_events": [
{
"last_affected": "9.0"
}
]
},
{
"cpes": [
"cpe:2.3:o:fedoraproject:fedora:30:*:*:*:*:*:*:*",
"cpe:2.3:o:fedoraproject:fedora:31:*:*:*:*:*:*:*"
],
"vendor_product": "fedoraproject:fedora",
"source": "CPE_STRING",
"extracted_events": [
{
"last_affected": "30"
},
{
"last_affected": "31"
}
]
},
{
"cpes": [
"cpe:2.3:a:oracle:communications_cloud_native_core_network_function_cloud_native_environment:1.10.0:*:*:*:*:*:*:*"
],
"vendor_product": "oracle:communications_cloud_native_core_network_function_cloud_native_environment",
"source": "CPE_STRING",
"extracted_events": [
{
"last_affected": "1.10.0"
}
]
},
{
"extracted_events": [
{
"last_affected": "15"
}
],
"vendor_product": "redhat:openstack",
"source": "CPE_STRING",
"cpes": [
"cpe:2.3:a:redhat:openstack:15:*:*:*:*:*:*:*"
]
}
]
}{
"extracted_events": [
{
"introduced": "0"
},
{
"fixed": "1.3.1"
}
],
"source": [
"CPE_RANGE",
"REFERENCES"
],
"cpe": "cpe:2.3:a:agendaless:waitress:*:*:*:*:*:*:*:*"
}