HTTP Request Smuggling Affecting python3-waitress package, versions <0:1.4.2-1.el8ost


Severity

Recommended
low

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.11% (46th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-PYTHON3WAITRESS-4395849
  • published26 Mar 2023
  • disclosed26 Dec 2019

Introduced: 26 Dec 2019

CVE-2019-16789  (opens in a new tab)
CWE-444  (opens in a new tab)

How to fix?

Upgrade RHEL:8 python3-waitress to version 0:1.4.2-1.el8ost or higher.
This issue was patched in RHSA-2020:0720.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3-waitress package and not the python3-waitress package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

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.

CVSS Scores

version 3.1