In Waitress through version 1.4.0, if a proxy server is used in front of waitress, an invalid request may be sent by an attacker that bypasses the front-end and is parsed differently by waitress leading to a potential for HTTP request smuggling. Specially crafted requests containing special whitespace characters in the Transfer-Encoding header would get parsed by Waitress as being a chunked request, but a front-end server would use the Content-Length instead as the Transfer-Encoding header is considered invalid due to containing invalid characters. If a front-end server does HTTP pipelining to a backend Waitress server this could lead to HTTP request splitting which may lead to potential cache poisoning or unexpected information disclosure. This issue is fixed in Waitress 1.4.1 through more strict HTTP field validation.
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.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Waitress | Agendaless | * | 1.4.0 (including) |
| Red Hat OpenStack Platform 15.0 (Stein) | RedHat | python-waitress-0:1.4.2-1.el8ost | * |
| Red Hat Quay 3 | RedHat | quay/clair-rhel8:v3.4.0-25 | * |
| Red Hat Quay 3 | RedHat | quay/quay-bridge-operator-bundle:v3.4.0-3 | * |
| Red Hat Quay 3 | RedHat | quay/quay-bridge-operator-rhel8:v3.4.0-17 | * |
| Red Hat Quay 3 | RedHat | quay/quay-builder-qemu-rhcos-rhel8:v3.4.0-17 | * |
| Red Hat Quay 3 | RedHat | quay/quay-builder-rhel8:v3.4.0-18 | * |
| Red Hat Quay 3 | RedHat | quay/quay-container-security-operator-bundle:v3.4.0-2 | * |
| Red Hat Quay 3 | RedHat | quay/quay-container-security-operator-rhel8:v3.4.0-2 | * |
| Red Hat Quay 3 | RedHat | quay/quay-openshift-bridge-rhel8-operator:v3.4.0-17 | * |
| Red Hat Quay 3 | RedHat | quay/quay-operator-bundle:v3.4.0-89 | * |
| Red Hat Quay 3 | RedHat | quay/quay-operator-rhel8:v3.4.0-132 | * |
| Red Hat Quay 3 | RedHat | quay/quay-rhel8:v3.4.0-51 | * |
| Waitress | Ubuntu | bionic | * |
| Waitress | Ubuntu | disco | * |
| Waitress | Ubuntu | eoan | * |
| Waitress | Ubuntu | esm-infra/bionic | * |
| Waitress | Ubuntu | esm-infra/xenial | * |
| Waitress | Ubuntu | trusty | * |
| Waitress | Ubuntu | upstream | * |
| Waitress | Ubuntu | xenial | * |
HTTP requests or responses (“messages”) can be malformed or unexpected in ways that cause web servers or clients to interpret the messages in different ways than intermediary HTTP agents such as load balancers, reverse proxies, web caching proxies, application firewalls, etc. For example, an adversary may be able to add duplicate or different header fields that a client or server might interpret as one set of messages, whereas the intermediary might interpret the same sequence of bytes as a different set of messages. For example, discrepancies can arise in how to handle duplicate headers like two Transfer-encoding (TE) or two Content-length (CL), or the malicious HTTP message will have different headers for TE and CL. The inconsistent parsing and interpretation of messages can allow the adversary to “smuggle” a message to the client/server without the intermediary being aware of it. This weakness is usually the result of the usage of outdated or incompatible HTTP protocol versions in the HTTP agents.