HTTP Request Smuggling Affecting python2-waitress package, versions <1.4.3-3.3.1


Severity

Recommended
0.0
high
0
10

Based on SUSE Linux Enterprise Server 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-SLES151-PYTHON2WAITRESS-2696610
  • published14 Apr 2022
  • disclosed10 Nov 2020

Introduced: 10 Nov 2020

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

How to fix?

Upgrade SLES:15.1 python2-waitress to version 1.4.3-3.3.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python2-waitress package and not the python2-waitress package as distributed by SLES. See How to fix? for SLES:15.1 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