HTTP Request Smuggling: Content-Length Sent Twice in Waitress
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Pylons | Waitress | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-3000-1 | waitress security update |
EUVD |
EUVD-2020-0239 | 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. |
Github GHSA |
GHSA-j7j6-7hfx-5522 | Inconsistent Interpretation of HTTP Requests in Waitress |
Github GHSA |
GHSA-4ppp-gpcr-7qf6 | HTTP Request Smuggling: Content-Length Sent Twice in Waitress |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 2.0% (1.984% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.