Waitress through version 1.3.1 implemented a "MAY" part of the RFC7230 which states: "Although the line terminator for the start-line and header fields is the sequence CRLF, a recipient MAY recognize a single LF as a line terminator and ignore any preceding CR." Unfortunately if a front-end server does not parse header fields with an LF the same way as it does those with a CRLF it can lead to the front-end and the back-end server parsing the same HTTP message in two different ways. This can lead to a potential for HTTP request smuggling/splitting whereby Waitress may see two requests while the front-end server only sees a single HTTP message. This issue is fixed in Waitress 1.4.0.
{
"unresolved_ranges": [
{
"extracted_events": [
{
"last_affected": "9.0"
}
],
"vendor_product": "debian:debian_linux",
"cpes": [
"cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*"
],
"source": "CPE_FIELD"
},
{
"extracted_events": [
{
"last_affected": "30"
},
{
"last_affected": "31"
}
],
"source": "CPE_FIELD",
"vendor_product": "fedoraproject:fedora",
"cpes": [
"cpe:2.3:o:fedoraproject:fedora:30:*:*:*:*:*:*:*",
"cpe:2.3:o:fedoraproject:fedora:31:*:*:*:*:*:*:*"
]
},
{
"extracted_events": [
{
"last_affected": "1.10.0"
}
],
"cpes": [
"cpe:2.3:a:oracle:communications_cloud_native_core_network_function_cloud_native_environment:1.10.0:*:*:*:*:*:*:*"
],
"source": "CPE_FIELD",
"vendor_product": "oracle:communications_cloud_native_core_network_function_cloud_native_environment"
},
{
"extracted_events": [
{
"last_affected": "15"
}
],
"source": "CPE_FIELD",
"vendor_product": "redhat:openstack",
"cpes": [
"cpe:2.3:a:redhat:openstack:15:*:*:*:*:*:*:*"
]
}
]
}