CVE-2019-16785
Description
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.
How to fix
- waitress1.4.0 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| agendaless waitress | v ≤ 1.3.1 | — |
| oracle communications_cloud_native_core_network_function_cloud_native_environment | 1.10.0 | — |
| debian debian_linux | 9.0 | — |
| fedoraproject fedora | 30, 31 | — |
| redhat openstack | 15 | — |
| waitressPyPI | v < 1.4.0 | 1.4.0 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.