|
|
|
|
CWE-315 Individual Dictionary Definition (Draft 9)
Weakness ID
| Status: Draft 315 (Weakness Variant) | | Description | Summary Storing sensitive data in
plaintext in a cookie makes the data more easily accessible than if
encrypted. This significantly lowers the difficulty of exploitation by attackers. | | Potential Mitigations | Sensitive information should not be stored in plaintext in a cookie. Even if heavy
fortifications are in place, sensitive data should be encrypted to prevent the risk of losing
confidentiality. | | Observed Examples | | Reference | Description |
|---|
| CVE-2002-1800 | Admin password in plaintext in a cookie. | | CVE-2001-1537 | Default configuration has cleartext usernames/passwords in cookie. | | CVE-2001-1536 | Usernames/passwords in cleartext in cookies. | | CVE-2005-2160 | Authentication information stored in cleartext in a cookie. |
| | Relationships | | | Source Taxonomies | PLOVER - Plaintext Storage in Cookie | | Applicable Platforms | All | | Related Attack Patterns | | CAPEC-ID | Attack Pattern Name |
|---|
| 37 | Lifting Data Embedded in Client Distributions | | 74 | Manipulating User State | | 39 | Manipulating Opaque Client-based Data Tokens | | 31 | Accessing/Intercepting/Modifying HTTP Cookies |
|
|
- Weakness
- Base
- Variant
- Class
- Chain
- Composite
- Category
- View
- Deprecated
