CVE-2019-16789

 

Published at: - 26-12-2019 06:15

Last modified: - 23-09-2022 08:58

Total changes: - 4

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.

Common Vulnerability Scoring System (CVSS)

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

 

Verification logic

 

Reference

• https://github.com/Pylons/waitress/commit/11d9e138125ad46e951027184b13242a3c1de017
• https://github.com/github/advisory-review/pull/14604
• https://docs.pylonsproject.org/projects/waitress/en/latest/#security-fixes
• FEDORA-2020-bdcc8ffc24-Mailing List, Third Party Advisory
• FEDORA-2020-65a7744e38-Mailing List, Third Party Advisory
• RHSA-2020:0720-Third Party Advisory
• https://www.oracle.com/security-alerts/cpuapr2022.html
• [debian-lts-announce] 20220512 [SECURITY] [DLA 3000-1] waitress security update-Mailing List, Third Party Advisory

 

Keywords

NVD

 

CVE-2019-16789

 

CVE

 

Common vulnerabilities & exposures

 

CVSS

 

Common vulnerability scoring system

 

Security

 

Vulnerabilities

 

Exposures