HTTP Request Smuggling: Content-Length Sent Twice in Waitress
21Vexday Risk Score
Sem sinal de exploração. Nenhum artefato público de exploração conhecido até agora.
ssvc Trackcvss 7.1epss 2.1%
probabilidade de exploração
2.1%top 20% das CVEs
exploração observada
nãonenhuma fonte reporta
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.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N
Produtos afetados
Pylons · WaitressReferências
https://docs.pylonsproject.org/projects/waitress/en/latest/#security-fixeshttps://github.com/Pylons/waitress/commit/575994cd42e83fd772a5f7ec98b2c56751bd3f65https://github.com/Pylons/waitress/security/advisories/GHSA-4ppp-gpcr-7qf6https://lists.debian.org/debian-lts-announce/2022/05/msg00011.htmlhttps://www.oracle.com/security-alerts/cpuapr2022.html