Discrepancies in how front-end proxies and back-end servers parse HTTP requests allow attackers to smuggle a hidden request inside another, enabling cache poisoning, session hijacking, WAF bypass, and access to other users' responses.
Immediate Response
1Disable HTTP/1.1 connection reuse (keep-alive) between front-end and back-end servers.
2Configure front-end and back-end to reject ambiguous requests with conflicting headers.
3Purge any poisoned cache entries and invalidate affected sessions.
4Deploy WAF rules to block requests with duplicate Content-Length or Transfer-Encoding headers.