Waitress up to 1.3.1 HTTP Message Split request smuggling
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.2 | $0-$5k | 0.00 |
A vulnerability, which was classified as critical, was found in Waitress up to 1.3.1. Affected is some unknown functionality. The manipulation as part of a HTTP Message leads to a request smuggling vulnerability (Split). CWE is classifying the issue as CWE-444. The product acts as an intermediary HTTP agent
(such as a proxy or firewall) in the data flow between two
entities such as a client and server, but it does not
interpret malformed HTTP requests or responses in ways that
are consistent with how the messages will be processed by
those entities that are at the ultimate destination. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
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.
The weakness was released 12/20/2019 (GitHub Repository). The advisory is shared for download at github.com. This vulnerability is traded as CVE-2019-16785 since 09/24/2019. The exploitability is told to be difficult. It is possible to launch the attack remotely. A authentication is required for exploitation. There are neither technical details nor an exploit publicly available.
Upgrading to version 1.4.0 eliminates this vulnerability.
Entry connected to this vulnerability is available at 147577.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.2
VulDB Base Score: 6.0
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.1
NVD Vector: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Name: SplitClass: Request smuggling / Split
CWE: CWE-444
ATT&CK: Unknown
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Waitress 1.4.0
Patch: github.com
Timeline
09/24/2019 🔍12/20/2019 🔍
12/21/2019 🔍
03/16/2024 🔍
Sources
Advisory: RHSA-2020:0720Status: Not defined
CVE: CVE-2019-16785 (🔍)
See also: 🔍
Entry
Created: 12/21/2019 17:55Updated: 03/16/2024 09:50
Changes: 12/21/2019 17:55 (41), 12/21/2019 18:00 (11), 03/16/2024 09:50 (4)
Complete: 🔍
No comments yet. Languages: en.
Please log in to comment.