CAPECattack pattern

CAPEC-102 Session Sidejacking

High Official page ↗
Abstraction
Detailed
Status
Draft
Likelihood of attack
High
Typical severity
High
CAPEC version
3.9

Description

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.

Execution flow

1. [Explore] [Detect Unprotected Session Token Transfer] The attacker sniffs on the wireless network to detect unencrypted traffic that contains session tokens. 2. [Experiment] [Capture session token] The attacker uses sniffing tools to capture a session token from traffic. 3. [Experiment] [Insert captured session token] The attacker attempts to insert a captured session token into communication with the targeted application to confirm viability for exploitation. 4. [Exploit] [Session Token Exploitation] The attacker leverages the captured session token to interact with the targeted application in a malicious fashion, impersonating the victim.

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

Skills required

• [Low] Easy to use tools exist to automate this attack.

Consequences

• Confidentiality, Access Control, Authorization: Gain Privileges • Integrity: Modify Data • Confidentiality: Read Data • Availability: Unreliable Execution

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.

Related

Child of · CAPEC (1)

Weakness · CWE (5)

  • CWE-294 Authentication Bypass by Capture-replay weakness
  • CWE-319 Cleartext Transmission of Sensitive Information weakness
  • CWE-522 Insufficiently Protected Credentials weakness
  • CWE-523 Unprotected Transport of Credentials weakness
  • CWE-614 Sensitive Cookie in HTTPS Session Without 'Secure' Attribute weakness

Referenced by CWE · attack pattern (5)

  • CWE-294 Authentication Bypass by Capture-replay weakness
  • CWE-319 Cleartext Transmission of Sensitive Information weakness
  • CWE-522 Insufficiently Protected Credentials weakness
  • CWE-523 Unprotected Transport of Credentials weakness
  • CWE-614 Sensitive Cookie in HTTPS Session Without 'Secure' Attribute weakness