Course contentsShow
← Security
Lesson 1111 of 3,05223. Web Security - Modern Web AttacksFree lesson

Request Smuggling for Session Hijacking

Capturing other users' request data including cookies and headers through smuggled request overlap.

Request Smuggling for Session Hijacking

What you'll learn: How attackers exploit HTTP request smuggling to intercept other users' sensitive session data like cookies and authentication headers.

The Attack Mechanism

Once an attacker has successfully created a desync condition (using CL.TE, TE.CL, or TE.TE techniques), they can position a smuggled request to "catch" parts of the next legitimate user's request. This is like hiding a recording device in a shared phone line—your smuggled request waits in the queue, and when the next person makes a call, you capture their conversation.

How Session Data Gets Captured

When you smuggle a partial request, the front-end and back-end servers disagree about where requests begin and end. Your smuggled request might end with what looks like the start of a POST request with a Content-Length header. When the next victim's request arrives, the back-end appends it to your smuggled request body.

The victim's request contains everything they sent: session cookies, authorization headers, CSRF tokens—all the sensitive authentication data. Your smuggled request can be designed to reflect or store this captured data somewhere you control (a comment field, user profile, or callback parameter).

Real-World Impact

Unlike bypassing security controls or cache poisoning, session hijacking via smuggling is particularly dangerous because:

  • You capture credentials without the victim knowing
  • You can impersonate users, including administrators
  • The attack works against any user who happens to connect after your smuggled request
  • No client-side interaction is required

This transforms request smuggling from infrastructure exploitation into a direct credential theft mechanism.

Key Takeaway: Request smuggling can capture subsequent users' complete requests—including cookies and headers—enabling direct session hijacking and account takeover without any victim interaction.