agendaless waitress CVE-2019-16792 vulnerability in Agendaless and Other Products
Published on January 22, 2020

HTTP Request Smuggling: Content-Length Sent Twice in Waitress

product logo product logo product logo
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.

NVD

Vulnerability Analysis

CVE-2019-16792 is exploitable with network access, and requires small amount of user privileges. This vulnerability is consided to have a high level of attack complexity. The potential impact of an exploit of this vulnerability is considered to have a high impact on confidentiality, with no impact on integrity, and no impact on availability.

Attack Vector:
NETWORK
Attack Complexity:
HIGH
Privileges Required:
LOW
User Interaction:
NONE
Scope:
CHANGED
Confidentiality Impact:
HIGH
Integrity Impact:
LOW
Availability Impact:
NONE

Weakness Type

What is a HTTP Request Smuggling Vulnerability?

When malformed or abnormal HTTP requests are interpreted by one or more entities in the data flow between the user and the web server, such as a proxy or firewall, they can be interpreted inconsistently, allowing the attacker to "smuggle" a request to one device without the other device being aware of it.

CVE-2019-16792 has been classified to as a HTTP Request Smuggling vulnerability or weakness.


Products Associated with CVE-2019-16792

You can be notified by email with stack.watch whenever vulnerabilities like CVE-2019-16792 are published in these products:

 
 
 

Affected Versions

Pylons Waitress:

Exploit Probability

EPSS
0.85%
Percentile
74.63%

EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.