Description
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.
No analysis available yet.
Remediation
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.
Tracking
Sign in to view the affected projects.
Advisories
| 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) |
References
History
No history.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2024-08-05T01:24:48.331Z
Reserved: 2019-09-24T00:00:00.000Z
Link: CVE-2019-16789
No data.
Status : Modified
Published: 2019-12-26T17:15:13.707
Modified: 2024-11-21T04:31:11.543
Link: CVE-2019-16789
OpenCVE Enrichment
No data.
Weaknesses
Debian DLA
EUVD
Github GHSA