|Name ||Reusing Session IDs (aka Session Replay) |
|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. |
|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. |
|Solutions ||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. |
|CWE ID ||Description |
|CWE-200 ||Information Exposure |
|CWE-285 ||Improper Authorization |
|CWE-290 ||Authentication Bypass by Spoofing |
|CWE-294 ||Authentication Bypass by Capture-replay |
|CWE-346 ||Origin Validation Error |
|CWE-384 ||Session Fixation |
|CWE-488 ||Exposure of Data Element to Wrong Session |
|CWE-539 ||Information Exposure Through Persistent Cookies |
|CWE-664 ||Improper Control of a Resource Through its Lifetime |
|CWE-732 ||Incorrect Permission Assignment for Critical Resource |