CVE-2019-16792
Published: 22 January 2020
Waitress through version 1.3.1 allows request smuggling by sending the Content-Length header twice. Waitress would header fold a double Content-Length header and due to being unable to cast the now comma separated value to an integer would set the Content-Length to 0 internally. If two Content-Length headers are sent in a single request, Waitress would treat the request as having no body, thereby treating the body of the request as a new request in HTTP pipelining. This issue is fixed in Waitress 1.4.0.
Priority
Status
Package | Release | Status |
---|---|---|
waitress Launchpad, Ubuntu, Debian |
bionic |
Needs triage
|
eoan |
Ignored
(end of life)
|
|
focal |
Not vulnerable
(1.4.1-1)
|
|
groovy |
Not vulnerable
(1.4.1-1)
|
|
hirsute |
Not vulnerable
(1.4.1-1)
|
|
impish |
Not vulnerable
(1.4.1-1)
|
|
jammy |
Not vulnerable
(1.4.1-1)
|
|
kinetic |
Not vulnerable
(1.4.1-1)
|
|
lunar |
Not vulnerable
(1.4.1-1)
|
|
mantic |
Not vulnerable
(1.4.1-1)
|
|
trusty |
Does not exist
|
|
upstream |
Released
(1.4.1-1)
|
|
xenial |
Needs triage
|
|
Patches: upstream: https://github.com/Pylons/waitress/commit/575994cd42e83fd772a5f7ec98b2c56751bd3f65 |
Severity score breakdown
Parameter | Value |
---|---|
Base score | 7.5 |
Attack vector | Network |
Attack complexity | Low |
Privileges required | None |
User interaction | None |
Scope | Unchanged |
Confidentiality | None |
Integrity impact | High |
Availability impact | None |
Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |