Back to feed
19Track

HTTP Request Smuggling: Invalid Transfer-Encoding in Waitress

Pylons Waitress · CVE-2019-16786
0 news outlets0 CERTs and agencies0 research labs

Assessment: Track

SSVC decision points: exploitation none, automatable no, technical impact partial, deployment low.

What is it?

Waitress through version 1.3.1 would parse the Transfer-Encoding header and only look for a single string value, if that value was not chunked it would fall through and use the Content-Length header instead. According to the HTTP standard Transfer-Encoding should be a comma separated list, with the inner-most encoding first, followed by any further transfer codings, ending with chunked. Requests sent with: "Transfer-Encoding: gzip, chunked" would incorrectly get ignored, and the request would use a Content-Length header instead to determine the body size of the HTTP message. This could allow for Waitress to treat a single request as multiple requests in the case of HTTP pipelining. This issue is fixed in Waitress 1.4.0.

Evidence

Official warnings1National CERTs, government cyber security agencies and the vendor’s own advisories

Exploitation

  • Exploit code published (not verified by us)
  • Exploited in the wild (confirmed by a source)
  • Listed as known exploited (CISA KEV)
CVSS
7.1
EPSS
–
First seen
5 Mar 2020
Status
confirmed

All Pylons vulnerabilities