Lab: Exploiting HTTP request smuggling to perform web cache poisoning

In-depth solution to PortSwigger's "Exploiting HTTP request smuggling to perform web cache poisoning" lab.

Try it yourself:

Timestamps:
00:00 - Intro
00:38 - Detect the CL.TE vulnerability
02:02 - Confirm the CL.TE vulnerability
03:54 - Find & turn onsite redirect into offsite redirect
05:37 - Find static asset cached by frontend
06:42 - Poison the frontend server's cached asset

[netletic]

Hey everyone! Check out this playlist for all my solutions to the HTTP Request Smuggling labs from PortSwigger – 👀

Here are the timestamps for this video – ⏱
00:00 - Intro
00:38 - Detect the CL.TE vulnerability
02:02 - Confirm the CL.TE vulnerability
03:54 - Find & turn onsite redirect into offsite redirect
05:37 - Find static asset cached by frontend
06:42 - Poison the frontend server's cached asset

[cowid]

Jarno, you really have a knack for breaking down complicated steps into something easier to digest. The effort you put in shows, and the quality is top-notch! Most content creators out there solely click around or paraphrase the solution out loud without much explanation, but you stand out by breaking everything down piece by piece. Your understanding of the topic really shines through. I hope you will continue adding content, you save me hours of headache !

[huyhuynh]

Thank you! I really enjoyed the video, especially how you made everything seem so simple. I particularly liked the backend part where every 30 seconds, it takes a JS file. By injecting our JS payload, anyone accessing the page triggers the payload.

[amrzaki]

This is so great; thank you keep up the good work.

[bolbolinfosec]

I am sincerely grateful to you, Thanks Bro ❤❤❤
you excel as an educator!