Total vulnerabilities in the database
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.
Software | From | Fixed in |
---|---|---|
agendaless / waitress | - | 1.3.1.x |
oracle / communications_cloud_native_core_network_function_cloud_native_environment | 1.10.0 | 1.10.0.x |
debian / debian_linux | 9.0 | 9.0.x |
fedoraproject / fedora | 30 | 30.x |
fedoraproject / fedora | 31 | 31.x |
redhat / openstack | 15 | 15.x |
![]() |
- | 1.4.0 |