HTTP Request Smuggling in Waitress: Invalid whitespace characters in headers
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Pylons | Waitress | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
Configuration 4 [-]
|
Configuration 5 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat OpenStack Platform 15.0 (Stein) | |||
| python-waitress-0:1.4.2-1.el8ost | cpe:/a:redhat:openstack:15::el8 | RHSA-2020:0720 | 2020-03-05T00:00:00Z |
| Red Hat Quay 3 | |||
| quay/clair-rhel8:v3.4.0-25 | cpe:/a:redhat:quay:3::el8 | RHSA-2021:0420 | 2021-02-04T00:00:00Z |
| quay/quay-bridge-operator-bundle:v3.4.0-3 | cpe:/a:redhat:quay:3::el8 | RHSA-2021:0420 | 2021-02-04T00:00:00Z |
| quay/quay-bridge-operator-rhel8:v3.4.0-17 | cpe:/a:redhat:quay:3::el8 | RHSA-2021:0420 | 2021-02-04T00:00:00Z |
| quay/quay-builder-qemu-rhcos-rhel8:v3.4.0-17 | cpe:/a:redhat:quay:3::el8 | RHSA-2021:0420 | 2021-02-04T00:00:00Z |
| quay/quay-builder-rhel8:v3.4.0-18 | cpe:/a:redhat:quay:3::el8 | RHSA-2021:0420 | 2021-02-04T00:00:00Z |
| quay/quay-container-security-operator-bundle:v3.4.0-2 | cpe:/a:redhat:quay:3::el8 | RHSA-2021:0420 | 2021-02-04T00:00:00Z |
| quay/quay-container-security-operator-rhel8:v3.4.0-2 | cpe:/a:redhat:quay:3::el8 | RHSA-2021:0420 | 2021-02-04T00:00:00Z |
| quay/quay-openshift-bridge-rhel8-operator:v3.4.0-17 | cpe:/a:redhat:quay:3::el8 | RHSA-2021:0420 | 2021-02-04T00:00:00Z |
| quay/quay-operator-bundle:v3.4.0-89 | cpe:/a:redhat:quay:3::el8 | RHSA-2021:0420 | 2021-02-04T00:00:00Z |
| quay/quay-operator-rhel8:v3.4.0-132 | cpe:/a:redhat:quay:3::el8 | RHSA-2021:0420 | 2021-02-04T00:00:00Z |
| quay/quay-rhel8:v3.4.0-51 | cpe:/a:redhat:quay:3::el8 | RHSA-2021:0420 | 2021-02-04T00:00:00Z |
No data available yet.
Vendor Workaround
You may enable additional protections on front-end servers, those that follow RFC7230 correctly would drop the request with a 400 Bad Request. Waitress will now correctly responds to the request with a 400 Bad Request, and will drop the connection to avoid any potential HTTP pipelining issues.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-3000-1 | waitress security update |
EUVD |
EUVD-2019-0158 | 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. |
Github GHSA |
GHSA-968f-66r5-5v74 | HTTP Request Smuggling in Waitress: Invalid whitespace characters in headers (Follow-up) |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 2.6% (2.587% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.