First published: Wed Jan 22 2020(Updated: )
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.
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Agendaless Waitress | <=1.3.1 | |
Oracle Communications Cloud Native Core Network Function Cloud Native Environment | =1.10.0 | |
Debian Debian Linux | =9.0 | |
debian/waitress | 1.2.0~b2-2+deb10u1 1.4.4-1.1+deb11u1 2.1.2-2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-16792 is a vulnerability that allows request smuggling by sending the Content-Length header twice in Waitress through version 1.3.1.
CVE-2019-16792 has a severity score of 7.5, which is considered high.
To fix CVE-2019-16792, you need to update Waitress to version 1.4.0 or later.
Waitress versions up to and including 1.3.1 are affected by CVE-2019-16792.
You can find more information about CVE-2019-16792 on the following sources: [GitHub Advisory](https://github.com/Pylons/waitress/security/advisories/GHSA-4ppp-gpcr-7qf6), [NVD](https://nvd.nist.gov/vuln/detail/CVE-2019-16792), [GitHub Commit](https://github.com/Pylons/waitress/commit/575994cd42e83fd772a5f7ec98b2c56751bd3f65).