What is session hijacking?
-
Monitoring UDP session
-
Monitoring TCP sessions
-
Taking over UDP sessions
-
Taking over TCP sessions
Session hijacking specifically means taking over an existing TCP session between a client and server. The attacker steals or intercepts session tokens (like session IDs or cookies) to impersonate the victim. Monitoring (A, B) is passive observation, not takeover. UDP (C) is connectionless and doesn't maintain sessions in the same way TCP does. Session hijacking targets the stateful nature of TCP connections.
Session hijacking is the act of taking over an already-established TCP session — typically by stealing or predicting the session identifier/cookie — so the attacker can impersonate the legitimate user without needing their credentials. It's an active takeover of the connection, not merely passive monitoring, and it applies to TCP-based sessions (like HTTP over TCP), not UDP.