HTTP Request Smuggling Affecting python3-waitress package, versions *


Severity

Recommended
low

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.34% (71st 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-3386168
  • published26 Mar 2023
  • disclosed20 Dec 2019

Introduced: 20 Dec 2019

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

How to fix?

There is no fixed version for RHEL:8 python3-waitress.

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.

Waitress through version 1.3.1 would parse the Transfer-Encoding header and only look for a single string value, if that value was not chunked it would fall through and use the Content-Length header instead. According to the HTTP standard Transfer-Encoding should be a comma separated list, with the inner-most encoding first, followed by any further transfer codings, ending with chunked. Requests sent with: "Transfer-Encoding: gzip, chunked" would incorrectly get ignored, and the request would use a Content-Length header instead to determine the body size of the HTTP message. This could allow for Waitress to treat a single request as multiple requests in the case of HTTP pipelining. This issue is fixed in Waitress 1.4.0.

CVSS Scores

version 3.1