Home > CAPEC List > CAPEC-102: Session Sidejacking (Version 2.11)  

CAPEC-102: Session Sidejacking

Session Sidejacking
Definition in a New Window Definition in a New Window
Attack Pattern ID: 102
Abstraction: Detailed
Status: Draft
Completeness: Complete
Presentation Filter:
+ Summary

Session sidejacking takes advantage of an unencrypted communication channel between a victim and target system. The attacker sniffs traffic on a network looking for session tokens in unencrypted traffic. Once a session token is captured, the attacker performs malicious actions by using the stolen token with the targeted application to impersonate the victim.

This attack is a specific method of session hijacking, which is exploiting a valid session token to gain unauthorized access to a target system or information. Other methods to perform a session hijacking are session fixation, cross-site scripting, or compromising a user or server machine and stealing the session token.

+ Attack Steps
  1. Detect Unprotected Session Token Transfer: The attacker sniffs on the wireless network to detect unencrypted traffic that contains session tokens.

    The attacker uses a network sniffer tool like ferret or hamster to monitor the wireless traffic at a WiFi hotspot while examining it for evidence of transmittal of session tokens in unencrypted or recognizably encrypted form. An attacker applies his knowledge of the manner by which session tokens are generated and transmitted by various target systems to identify the session tokens.

  1. Capture session token: The attacker uses sniffing tools to capture a session token from traffic.

  2. Insert captured session token: The attacker attempts to insert a captured session token into communication with the targeted application to confirm viability for exploitation.

  1. Session Token Exploitation: The attacker leverages the captured session token to interact with the targeted application in a malicious fashion, impersonating the victim.

+ Attack Prerequisites
  • An attacker and the victim are both using the same WiFi network.

  • The victim has an active session with a target system.

  • The victim is not using a secure channel to communicate with the target system (e.g. SSL, VPN, etc.)

  • The victim initiated communication with a target system that requires transfer of the session token or the target application uses AJAX and thereby periodically "rings home" asynchronously using the session token

+ Typical Severity


+ Typical Likelihood of Exploit

Likelihood: High

+ Methods of Attack
  • Time and State
  • Analysis
  • Spoofing
  • Protocol Manipulation
+ Examples-Instances


The attacker and the victim are using the same WiFi public hotspot. When the victim connects to the hotspot, he has a hosted e-mail account open. This e-mail account uses AJAX on the client side which periodically asynchronously connects to the server side and transfers, amongst other things, the user's session token to the server. The communication is supposed to happen over HTTPS. However, the configuration in the public hotspot initially disallows the HTTPS connection (or any other connection) between the victim and the hosted e-mail servers because the victim first needs to register with the hotspot. The victim does so, but his e-mail client already defaulted to using a connection without HTTPS, since it was denied access the first time. Victim's session token is now flowing unencrypted between the victim's browser and the hosted e-mail servers. The attacker leverages this opportunity to capture the session token and gain access to the victim's hosted e-mail account.

+ Attacker Skills or Knowledge Required

Skill or Knowledge Level: Low

Easy to use tools exist to automate this attack.

+ Resources Required

A packet sniffing tool, such as wireshark, can be used to capture session information.

+ Probing Techniques

Use available tools to snoop on communications between the victim and the target system and try to capture the transmitted session token

Use the captured session token to impersonate the victim on the target system to perform actions and view information on their behalf.

+ Solutions and Mitigations

Make sure that HTTPS is used to communicate with the target system. Alternatively, use VPN if possible. It is important to ensure that all communication between the client and the server happens via an encrypted secure channel.

Modify the session token with each transmission and protect it with cryptography. Add the idea of request sequencing that gives the server an ability to detect replay attacks.

+ Attack Motivation-Consequences
ScopeTechnical ImpactNote
Gain privileges / assume identity
Modify memory
Read memory
DoS: crash / exit / restart
DoS: instability
+ Relevant Security Requirements

Ensure that SSL is used for all communication between the client and the target system where sensitive data and/or operations are available.

Ensure that session cookies are only transmitted via SSL pipes by setting the cookie's secure attribute to true.

+ Purposes
  • Exploitation
+ CIA Impact
Confidentiality Impact: HighIntegrity Impact: HighAvailability Impact: Low
+ Technical Context
Architectural Paradigms
+ Content History
CAPEC Content TeamThe MITRE Corporation2014-06-23Internal_CAPEC_Team
CAPEC Content TeamThe MITRE Corporation2017-05-01Updated Related_Attack_PatternsInternal
CAPEC Content TeamThe MITRE Corporation2017-08-04Updated Resources_RequiredInternal

More information is available — Please select a different filter.
Page Last Updated or Reviewed: August 04, 2017