Candidate: CVE-2019-16785
PublicDate: 2019-12-20 23:15:00 UTC
References:
 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16785
 https://docs.pylonsproject.org/projects/waitress/en/latest/#security-fixes
 https://github.com/Pylons/waitress/security/advisories/GHSA-pg36-wpm5-g57p
Description:
 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.
Ubuntu-Description:
Notes:
Mitigation:
Bugs:
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947306
Priority: low
Discovered-by:
Assigned-to:
CVSS:
 nvd: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N [7.5 HIGH]


Patches_waitress:
 upstream: https://github.com/Pylons/waitress/commit/8eba394ad75deaf9e5cd15b78a3d16b12e6b0eba
upstream_waitress: released (1.4.0)
precise/esm_waitress: DNE
trusty_waitress: ignored (out of standard support)
trusty/esm_waitress: DNE
xenial_waitress: ignored (end of standard support, was needed)
esm-infra/xenial_waitress: needed
bionic_waitress: needed
disco_waitress: ignored (reached end-of-life)
eoan_waitress: ignored (reached end-of-life)
focal_waitress: not-affected (1.4.1-1)
groovy_waitress: not-affected (1.4.1-1)
hirsute_waitress: not-affected (1.4.1-1)
impish_waitress: not-affected (1.4.1-1)
jammy_waitress: not-affected (1.4.1-1)
devel_waitress: not-affected (1.4.1-1)