HTTP Request Smuggling Affecting python-waitress package, versions *


Severity

Recommended
low

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.77% (82nd 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-PYTHONWAITRESS-3385870
  • published26 Mar 2023
  • disclosed20 Dec 2019

Introduced: 20 Dec 2019

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

How to fix?

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

NVD Description

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

Waitress through version 1.3.1 implemented a "MAY" part of the RFC7230 which states: "Although the line terminator for the start-line and header fields is the sequence CRLF, a recipient MAY recognize a single LF as a line terminator and ignore any preceding CR." Unfortunately if a front-end server does not parse header fields with an LF the same way as it does those with a CRLF it can lead to the front-end and the back-end server parsing the same HTTP message in two different ways. This can lead to a potential for HTTP request smuggling/splitting whereby Waitress may see two requests while the front-end server only sees a single HTTP message. This issue is fixed in Waitress 1.4.0.

CVSS Scores

version 3.1