CVE-2019-16789

published 26 Dec 2019 · updated 5 Aug 2024

HTTP Request Smuggling in Waitress: Invalid whitespace characters in headers

7.1HighCVSS 7.1EPSS 3%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 3%. Fixed in 1.4.1.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Pylons>=< 1.4.1 <1.4.11.4.1

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2019-16789 severity on Zeptric[![CVE-2019-16789](https://zeptric.io/badge/cve/CVE-2019-16789.svg)](https://zeptric.io/cve/CVE-2019-16789)