CVE-2019-16792

HTTP Request Smuggling: Content-Length Sent Twice in Waitress

Published Jan 22, 2020 CVSS 3.1 · 7.1 High EPSS 2.0% KEV · Not listed
Description
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-3000-1 waitress security update
EUVD 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 Github GHSA GHSA-j7j6-7hfx-5522 Inconsistent Interpretation of HTTP Requests in Waitress
Github GHSA Github GHSA GHSA-4ppp-gpcr-7qf6 HTTP Request Smuggling: Content-Length Sent Twice in Waitress
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 5, 2024, 1:24 AM
Reserved
Sep 24, 2019, 12:00 AM
Status
Modified
Published
Jan 22, 2020, 7:15 PM
Modified
Jun 17, 2026, 2:22 AM