HTTP Desync Attack
What is HTTP Desync Attack?
HTTP Desync AttackA modern form of HTTP request smuggling that desynchronises a chain of proxies and servers to inject malicious traffic into other users' connections.
Popularised by James Kettle's 2019 Black Hat/DEF CON research "HTTP Desync Attacks: Request Smuggling Reborn", desync attacks deliberately put a front-end proxy out of step with the back-end about where one request ends and the next begins. The flaw lives in keep-alive connections that pool many users' requests: if the two servers disagree on message length, attacker-prefixed bytes get glued onto the next victim's request.
Classic variants exploit the Content-Length / Transfer-Encoding ambiguity — CL.TE, TE.CL and TE.TE — where the front-end trusts one header and the back-end the other. Kettle's original research demonstrated impact against real stacks including PayPal's login page, and the same parsing bugs produced fixes such as Go's net/http CVE-2019-16276. His 2022 DEF CON 30 work "Browser-Powered Desync Attacks" extended the class to client-side and HTTP/2-downgrade desync, and his 2025 "HTTP/1.1 must die" research argues the only durable fix is end-to-end HTTP/2.
Consequences include stealing other users' session cookies, reaching internal admin endpoints, response-queue poisoning, and bypassing WAFs or authentication. Defences: run HTTP/2 end-to-end (no downgrade to HTTP/1.1 upstream), reject any request carrying both Content-Length and Transfer-Encoding, normalise or drop ambiguous requests at the edge, disable upstream connection reuse where feasible, and test continuously with tooling like HTTP Request Smuggler.
flowchart TB A["Attacker sends one crafted request<br/>with conflicting CL + TE headers"] --> FE["Front-end proxy<br/>uses Content-Length"] FE -->|"forwards full bytes on<br/>pooled keep-alive socket"| BE["Back-end server<br/>uses Transfer-Encoding"] BE --> Q["Leftover 'smuggled' bytes stay<br/>queued on the connection"] V["Victim's next request<br/>on same socket"] --> Q Q --> P["Smuggled prefix + victim request<br/>= poisoned request"] P --> R["Cookie theft, internal access,<br/>response poisoning, WAF bypass"]
● Examples
- 01
HTTP/2-to-HTTP/1.1 downgrade desync that exfiltrates other users' session cookies.
- 02
Front-end keep-alive desync that hijacks the next request to an internal admin URL.
● Frequently asked questions
What is HTTP Desync Attack?
A modern form of HTTP request smuggling that desynchronises a chain of proxies and servers to inject malicious traffic into other users' connections. It belongs to the Vulnerabilities category of cybersecurity.
What does HTTP Desync Attack mean?
A modern form of HTTP request smuggling that desynchronises a chain of proxies and servers to inject malicious traffic into other users' connections.
How do you defend against HTTP Desync Attack?
Defences for HTTP Desync Attack typically combine technical controls and operational practices, as detailed in the full definition above.
What are other names for HTTP Desync Attack?
Common alternative names include: HTTP/1.1 desync, Connection-state attack.