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.
History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published: 2019-12-26T16:40:12

Updated: 2024-08-05T01:24:48.331Z

Reserved: 2019-09-24T00:00:00

Link: CVE-2019-16789

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2019-12-26T17:15:13.707

Modified: 2024-11-21T04:31:11.543

Link: CVE-2019-16789

cve-icon Redhat

Severity : Important

Publid Date: 2019-12-26T00:00:00Z

Links: CVE-2019-16789 - Bugzilla