CVE-2024-14029
Received Received - Intake

Tornado HTTP Request Smuggling via Duplicate Chunked Headers

Publication date: 2026-09-15

Last updated on: 2026-09-15

Assigner: VulnCheck

Description
Tornado before 6.4.1 ignores duplicate Transfer-Encoding: chunked headers, treating requests as having no message body and parsing the chunked body as a subsequent request. Attackers can exploit this inconsistency when Tornado is deployed behind proxies to perform HTTP request smuggling, enabling access control bypass, cache poisoning, or connection desynchronization.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-15
Last Modified
2026-09-15
Generated
2026-09-15
AI Q&A
2026-09-15
EPSS Evaluated
N/A
NVD
CVE-2024-14029
EUVD
EUVD-2024-55765

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
tornadoweb tornado to 6.4.1 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
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.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Tornado before 6.4.1 has a flaw where duplicate Transfer-Encoding: chunked headers are ignored, causing the server to treat requests as having no body. This leads to incorrect parsing of the chunked body as a new request. When deployed behind proxies, this inconsistency enables HTTP request smuggling attacks.

Detection Guidance

To detect this vulnerability, monitor for duplicate Transfer-Encoding: chunked headers in HTTP requests. Use tools like Wireshark or tcpdump to capture and analyze traffic for malformed requests. Check proxy logs for inconsistencies in request parsing or unexpected request sequences.

Impact Analysis

Attackers can exploit this to bypass access controls, poison caches, or disrupt connections. This may allow unauthorized access to sensitive data, manipulate cached content, or cause service disruptions in systems using affected Tornado versions behind proxies.

Compliance Impact

This vulnerability could lead to unauthorized data access or manipulation, violating GDPR's data protection principles or HIPAA's security requirements for protected health information. Organizations may face compliance failures if exploited.

Mitigation Strategies

Immediately upgrade Tornado to version 6.4.1 or later. If upgrading is not possible, configure proxies to reject requests with duplicate Transfer-Encoding headers. Implement strict HTTP request validation at the proxy level to block malformed requests.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2024-14029. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart