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.
References
Link | Resource |
---|---|
https://docs.pylonsproject.org/projects/waitress/en/latest/#security-fixes | Release Notes |
https://github.com/Pylons/waitress/commit/575994cd42e83fd772a5f7ec98b2c56751bd3f65 | Patch |
https://github.com/Pylons/waitress/security/advisories/GHSA-4ppp-gpcr-7qf6 | Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2022/05/msg00011.html | Mailing List Third Party Advisory |
https://www.oracle.com/security-alerts/cpuapr2022.html | Patch Third Party Advisory |
Configurations
History
No history.
Information
Published : 2020-01-22 19:15
Updated : 2024-02-28 17:28
NVD link : CVE-2019-16792
Mitre link : CVE-2019-16792
CVE.ORG link : CVE-2019-16792
JSON object : View
Products Affected
agendaless
- waitress
oracle
- communications_cloud_native_core_network_function_cloud_native_environment
debian
- debian_linux
CWE
CWE-444
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')