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.
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
| Link | Tags |
|---|---|
| https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/GVDHR2DNKCNQ7YQXISJ45NT4IQDX3LJ7/ | vendor advisory |
| https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LYEOTGWJZVKPRXX2HBNVIYWCX73QYPM5/ | vendor advisory |
| https://access.redhat.com/errata/RHSA-2020:0720 | third party advisory vendor advisory |
| https://www.oracle.com/security-alerts/cpuapr2022.html | third party advisory patch |
| https://docs.pylonsproject.org/projects/waitress/en/latest/#security-fixes | vendor advisory |
| https://github.com/Pylons/waitress/security/advisories/GHSA-pg36-wpm5-g57p | third party advisory exploit |
| https://github.com/Pylons/waitress/commit/8eba394ad75deaf9e5cd15b78a3d16b12e6b0eba | third party advisory patch |
| https://lists.debian.org/debian-lts-announce/2022/05/msg00011.html | third party advisory mailing list |