|
|
| Home > CAPEC List > Individual CAPEC Dictionary Definition (Release 1.1) | View the CAPEC List |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Individual CAPEC Dictionary Definition (Release 1.1)
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Reusing Session IDs (aka Session Replay) | |||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Attack Pattern ID | Pattern Abstraction: Standard 60 | ||||||||||||||||||||||||||||||||
| Typical Severity | High | ||||||||||||||||||||||||||||||||
| Description | Summary This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay. Attack Execution Flow
| ||||||||||||||||||||||||||||||||
| Attack Prerequisites | The target host uses session IDs to keep track of the users. Session IDs are used to control access to resources. The session IDs used by the target host are not well protected from session theft. | ||||||||||||||||||||||||||||||||
| Typical Likelihood of Exploit | High | ||||||||||||||||||||||||||||||||
| Methods of Attack |
| ||||||||||||||||||||||||||||||||
| Examples-Instances | Description OpenSSL and SSLeay allow remote attackers to reuse SSL sessions and bypass access controls. Related Vulnerability CVE-1999-0428 Description Merak Mail IceWarp Web Mail uses a static identifier as a user session ID that does not change across sessions, which could allow remote attackers with access to the ID to gain privileges as that user, e.g. by extracting the ID from the user's answer or forward URLs. Related Vulnerability CVE-2002-0258 | ||||||||||||||||||||||||||||||||
| Attacker Skill or Knowledge Required | Low: If an attacker can steal a valid session ID, he can then try to be authenticated with that stolen session ID. Medium/High: More sophisticated attack can be used to hijack a valid session from a user and spoof a ligitimate user by reusing his valid session ID. | ||||||||||||||||||||||||||||||||
| Probing Techniques | The attacker can listen to a conversation between the client and server and steal a valid session ID. The attacker can try to steal session information from the user's coookies. The attacker can try a valid session from a finished transaction and find out that the transaction associated with the session ID did not time out. | ||||||||||||||||||||||||||||||||
| Solutions and Mitigations | Always invalidate a session ID after the user logout. Setup a session time out for the session IDs. Protect the communication between the client and server. For instance it is best practice to use SSL to mitigate man in the middle attack. Do not code send session ID with GET method, otherwise the session ID will be copied to the URL. In general avoid writing session IDs in the URLs. URLs can get logged in log files, which are vulnerable to an attacker. Encrypt the session data associated with the session ID. Use multifactor authentication. | ||||||||||||||||||||||||||||||||
| Attack Motivation- |
| ||||||||||||||||||||||||||||||||
| Context Description | |||||||||||||||||||||||||||||||||
| Related Weaknesses |
| ||||||||||||||||||||||||||||||||
| Related Attack Patterns |
| ||||||||||||||||||||||||||||||||
| Related Security Principles |
| ||||||||||||||||||||||||||||||||
| Purpose | Penetration | ||||||||||||||||||||||||||||||||
| CIA Impact |
| ||||||||||||||||||||||||||||||||
| Technical Context |
| ||||||||||||||||||||||||||||||||
| References | G. Hoglund and G. McGraw. Exploiting Software: How to Break Code. Addison-Wesley, February 2004. | ||||||||||||||||||||||||||||||||
| Source |
| ||||||||||||||||||||||||||||||||
|
|
|