CVE-2019-16785

HTTP Request Smuggling: LF vs CRLF handling in Waitress

Published Dec 20, 2019 CVSS 3.1 · 7.1 High EPSS 2.5% KEV · Not listed
Description
Waitress through version 1.3.1 implemented a "MAY" part of the RFC7230 which states: "Although the line terminator for the start-line and header fields is the sequence CRLF, a recipient MAY recognize a single LF as a line terminator and ignore any preceding CR." Unfortunately if a front-end server does not parse header fields with an LF the same way as it does those with a CRLF it can lead to the front-end and the back-end server parsing the same HTTP message in two different ways. This can lead to a potential for HTTP request smuggling/splitting whereby Waitress may see two requests while the front-end server only sees a single HTTP message. This issue is fixed in Waitress 1.4.0.

Analysis

No analysis available yet

Remediation

No remediation available yet

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-2019-0156 Waitress through version 1.3.1 implemented a \"MAY\" part of the RFC7230 which states: \"Although the line terminator for the start-line and header fields is the sequence CRLF, a recipient MAY recognize a single LF as a line terminator and ignore any preceding CR.\" Unfortunately if a front-end server does not parse header fields with an LF the same way as it does those with a CRLF it can lead to the front-end and the back-end server parsing the same HTTP message in two different ways. This can lead to a potential for HTTP request smuggling/splitting whereby Waitress may see two requests while the front-end server only sees a single HTTP message. This issue is fixed in Waitress 1.4.0.
Github GHSA Github GHSA GHSA-pg36-wpm5-g57p HTTP Request Smuggling: LF vs CRLF handling in Waitress
History

No history.

Weaknesses
  • CWE-444

    Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 5, 2024, 1:24 AM
Reserved
Sep 24, 2019, 12:00 AM
Status
Modified
Published
Dec 20, 2019, 11:15 PM
Modified
Jun 17, 2026, 2:22 AM
Severity
Important
Public date
Dec 20, 2019, 12:00 AM