Response Smuggling: Pwning HTTP/1.1 Connections
Martin Doyhenard introduces HTTP Response Smuggling, exploiting desynchronization in HTTP/1.1 response pipelines to poison caches and hijack user sessions.
Summary
Expanding Beyond HTTP Request Smuggling
While HTTP request smuggling focuses on manipulating incoming requests between reverse proxies and backends, response handling pipelines represent an equally dangerous attack surface.
Introducing HTTP Response Smuggling
Martin Doyhenard analyzes how reverse proxies parse backend HTTP/1.1 response headers, uncovering discrepancies in `Content-Length` and `Transfer-Encoding` processing.
Poisoning Web Caches and Capturing Sensitive Responses
By smuggling premature HTTP responses into shared connection pools, an attacker pairs malicious responses with subsequent benign user requests, hijacking sessions and stealing credentials.
Defensive Architecture for HTTP Reverse Proxies
Doyhenard provides web application firewall (WAF) rule sets and connection isolation recommendations to eliminate response pipeline desynchronization.
Related talks
Main Stage·40 min
James Kettle
PortSwigger researcher James Kettle pioneers HTTP/2 request smuggling, uncovering critical implementation flaws when front-end reverse proxies downgrade to back-end HTTP/1.1.
Black Hat·48 min
Security researchers examine technical aspects of HTTP Desync Attacks: Request Smuggling Reborn.
OWASP Foundation·45 min
James Kettle
James Kettle explores HTTP Desync Attacks: Smashing Into The Cell Next Door.


