Lab: CL.0 request smuggling

[@netletic]

Hey everyone! Check out this playlist for all my solutions to the HTTP Request Smuggling labs from PortSwigger - 👀 kzbin.info/aero/PLGb2cDlBWRUX1_7RAIjRkZDYgAB3VbUSw Here are the timestamps for this video - ⏱ 00:00 - Intro 01:17 - Find endpoint that ignores Content-Length 02:36 - Use Differential Responses to detect & confirm the CL.0 vulnerability 04:24 - Exploit the CL.0 vulnerability to bypass the frontend security control

[@vlkn-ml5jv]

I appreciate your effort in making it understandable. Normally, I don't leave comments, but I had to make an exception in this case.

[@netletic]

thank you @vlkn-ml5jv, glad it was helpful! 🔥

[@panchakosha]

You are a beast! Only one more to go. Your efforts are greatly appreciated.

[@netletic]

thanks @panchakosha, and thanks for cheering me on throughout the entire series - that was great motivation! 🔥

[@thinhdang9256]

how can you make a graph for this attack, could you tell me which website or app did you use?

[@thinhdang9256]

when i try to solve the lab, i didn't add Connection: Keep-Alive header and add group 2 req but i still solve this like the previous lab (TE-CL)

[@thinhdang9256]

Did the step add header and add group not necessary

[@muhammadadel9537]

@@thinhdang9256 I think the Connection: keep-alive is being added automatically by the application Check a normal request, and you will notice that it is being added automatically. but the burp option "Strip Connection header over HTTP/2" removes it.