10.2 - Session Hijacking
10.2 - Session hijacking
Key Terms:
- Session hijacking – Taking over an established connection between a host and a web server using a token.
- Session ID – A combination of letters and numbers assigned to an open connection between a user and a server.
Session Hijacking Process
The first step to hijack an active session is to first sniff the traffic between the target machine and the server. Next, the hacker will monitor the traffic and try to predict the packet sequence numbers. Then they will desynchronise the current session to be able to predict the session ID. Finally, commands will be injected to target the server.
Session IDs
The key to session hijacking lies in session IDs. Once a client is authenticated, the server provides a short period of time that the client can maintain an open connection. The server assumes that information sent and received during this session is being done by the appropriate user. Each reservation, or session, is assigned an alphanumeric session ID, also known as a session token. This token serves as the key--and this is where the opportunity lies for an attacker. If an attacker can capture or even calculate the ID, they can hijack a session.
Application-Level Hijacking
This is when the session ID lets the server know who it is communicating with. Session IDs can be found in web history, hidden fields and cookies.
Comments
Post a Comment