W-REQUEST-SMUGGLE-CLTEImpact

HTTP Request Smuggling — CL.TE

Frontend honours Content-Length, backend honours Transfer-Encoding — smuggle a second request to bypass auth / poison.

§ Where this technique fits

W-REQUEST-SMUGGLE-CLTE is catalogued under the Impact tactic of the offensive-security kill-chain. It appears in 1 approved dossier in the registry, typically at step 2 on average.

§ Dossiers chaining this technique

HTTP request smuggling (CL.TE) → admin panel bypass
Frontend uses Content-Length, backend uses Transfer-Encoding. Smuggle a request whose path bypasses the frontend's authentication checks.
step 2 / 6

§ What commonly comes next

01
X-Original-URL / X-Rewrite-URL Bypass
W-HEADER-AUTH-BYPASS · Privilege Escalation
seen 1×

§ Where this technique fits

§ Dossiers chaining this technique

HTTP request smuggling (CL.TE) → admin panel bypass

§ What commonly comes next