CAPEC-31: Accessing/Intercepting/Modifying HTTP Cookies
ID
CAPEC-31
Typical Severity
High
Likelihood Of Attack
High
Status
Draft
This attack relies on the use of HTTP Cookies to store credentials, state information and other critical data on client systems. There are several different forms of this attack. The first form of this attack involves accessing HTTP Cookies to mine for potentially sensitive data contained therein. The second form involves intercepting this data as it is transmitted from client to server. This intercepted information is then used by the adversary to impersonate the remote user/session. The third form is when the cookie's content is modified by the adversary before it is sent back to the server. Here the adversary seeks to convince the target server to operate on this falsified information.
Weaknesses
# ID | Name | Type |
---|---|---|
CWE-20 | Improper Input Validation | weakness |
CWE-113 | Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') | weakness |
CWE-302 | Authentication Bypass by Assumed-Immutable Data | weakness |
CWE-311 | Missing Encryption of Sensitive Data | weakness |
CWE-315 | Cleartext Storage of Sensitive Information in a Cookie | weakness |
CWE-384 | Session Fixation | weakness |
CWE-472 | External Control of Assumed-Immutable Web Parameter | weakness |
CWE-539 | Use of Persistent Cookies Containing Sensitive Information | weakness |
CWE-565 | Reliance on Cookies without Validation and Integrity Checking | weakness |
CWE-602 | Client-Side Enforcement of Server-Side Security | weakness |
CWE-642 | External Control of Critical State Data | weakness |
Taxonomiy Mapping
Type | # ID | Name |
---|---|---|
ATTACK | 1539 | Steal Web Session Cookie |