← Back to Attack / Defense Lab
OSI LAYER 5 // Session Layer

Session Fixation

Session fixation occurs when an attacker causes a victim to authenticate using a session identifier that the attacker already knows.

01 // HOW IT WORKS

Mechanism

The application accepts a pre-authentication session and fails to issue a new identifier after login or privilege elevation.

02 // DETECTION

Indicators to watch

Authentication events where the session identifier remains unchanged, reuse of pre-login tokens, and suspicious session continuity across privilege changes.

03 // ATTACK FLOW

Concept diagram

01Pre-login session↓
02Attacker-known identifier↓
03Victim authenticates↓
04Session remains predictable↓
05Rotate ID after login
04 // PREVENTION

Defensive controls

Regenerate session identifiers after authentication and privilege changes; invalidate old sessions and use secure cookie attributes.

05 // SECURITY TOOL

Recommended security control

Web framework session management

Use a local test application to verify session rotation.

06 // DEFENCE PRACTICE LAB

Defence practice lab

The administrator has not attached a tool link yet. This slot will show “Build Soon” until an external link is configured.

Build Soon
◈
DEFENCE PRACTICE LAB // BUILD SOONThe administrator can add or edit an external defence practice lab link from the private admin portal.
07 // DEFENCE TECHNIQUES

Defence techniques

Defence techniques for this attack will be added by the administrator.

AUTHORIZED LEARNING

All attack descriptions are for defensive education. Test scanning, traffic generation, interception, wireless testing, and vulnerable applications only on systems and networks you own or are explicitly authorized to assess.