HTTP Request Smuggling
What is HTTP Request Smuggling?
HTTP Request SmugglingAn attack that exploits disagreements between a front-end proxy and a back-end server on how an HTTP request ends, so an attacker can sneak a hidden second request through.
HTTP request smuggling abuses inconsistent parsing of the Content-Length (CL) and Transfer-Encoding (TE) headers between a front-end intermediary — load balancer, CDN, or reverse proxy — and the back-end origin. When the two tiers disagree on where a message ends, an attacker prepends a crafted prefix that the back end treats as the start of the next visitor's request. The three classic variants (CL.TE, TE.CL, and TE.TE header obfuscation) exist because RFC 7230 says a request carrying both headers must be rejected, yet many stacks silently prefer one.
The modern era began with James Kettle's 2019 Black Hat USA research "HTTP Desync Attacks: Smashing into the Cell Next Door," which weaponised the technique against real targets, including PayPal's login page. His follow-ups — "HTTP/2: The Sequel Is Always Worse" (2021) and "Browser-Powered Desync Attacks" (2022) — showed that HTTP/2-to-HTTP/1.1 downgrades and client-side desync keep the class alive even as individual servers get patched.
Impact includes web-cache poisoning served to every later visitor, credential and session-cookie capture over shared keep-alive connections, WAF and access-control bypass, and response-queue poisoning.
Defences: prefer HTTP/2 end-to-end (avoid downgrades), reject messages that contain both CL and TE or that are otherwise ambiguous, normalise requests at the edge, and keep front-end and back-end HTTP parsers version-aligned.
flowchart TD A["Attacker"] -->|"CL.TE ambiguous request"| F["Front-end proxy / CDN"] F -->|"forwards full body (keep-alive)"| B["Back-end origin"] B -->|"splits on Transfer-Encoding"| S["Smuggled prefix left in buffer"] V["Next visitor"] -->|"normal request"| F F --> B S -.->|"prepended to victim request"| P["Poisoned response / stolen data"]
● Examples
- 01
CL.TE smuggling against a CDN/back-end pair where the CDN uses Content-Length and the origin uses Transfer-Encoding.
- 02
Smuggled POST request stealing the next user's Authorization header from a shared keep-alive connection.
● Frequently asked questions
What is HTTP Request Smuggling?
An attack that exploits disagreements between a front-end proxy and a back-end server on how an HTTP request ends, so an attacker can sneak a hidden second request through. It belongs to the Vulnerabilities category of cybersecurity.
What does HTTP Request Smuggling mean?
An attack that exploits disagreements between a front-end proxy and a back-end server on how an HTTP request ends, so an attacker can sneak a hidden second request through.
How do you defend against HTTP Request Smuggling?
Defences for HTTP Request Smuggling typically combine technical controls and operational practices, as detailed in the full definition above.
What are other names for HTTP Request Smuggling?
Common alternative names include: HRS, Request smuggling.