Skip navigation
How to manually check for CL.TE Request Smuggling Vulnerabilities:
0:00 / 0:30

How to manually check for CL.TE Request Smuggling Vulnerabilities:

Web Security Academy

@WebSecAcademy148K followers

Visit on X
518 likesDownloadOriginal post

28,034 views

How to manually check for CL.TE Request Smuggling Vulnerabilities: 1️⃣ See if a GET request accepts POST 2️⃣ See if it accepts HTTP/1 3️⃣ Disable "Update Content-Length" 4️⃣ Send with CL & TE headers: POST / HTTP/1.1 Host: Content-Length: 6 Transfer-Encoding: chunked 0 G 5️⃣ Send request twice. If you receive a response like "Unrecognized method GPOST", you've just confirmed a CL.TE vulnerability! Try this out for yourself in our CL.TE lab:

4 Comments

Comments from the original post on X (Twitter)

  • walmart's profile picture

    @alluredsky

    I'm glad request smuggling is getting its well deserved resurgence in attention

  • Fabre Pierre-jean's profile picture

    @FabrePierrejean

    but the labs dont work. Look the first lab, i copy/paste the solution to prove it and sent it twice

  • dark18's profile picture

    @dark184465

    Thank you

  • Mohsin Ali's profile picture

    @MohsinA76056681

    What's the impact for this bug