|
Status: Draft Weakness ID: 614 (Weakness Variant)Description Summary The Secure attribute for sensitive cookies in HTTPS sessions is not set, which could cause the user agent to send those cookies in plaintext over an HTTP session. Potential Mitigations Always set the secure attribute when the cookie should sent via HTTPS only. Demonstrative Examples The snippet of code below, taken from a servlet doPost() method, sets an accountID cookie (sensitive) without calling setSecure(true). Java Example: Cookie c = new Cookie(ACCOUNT_ID, acctID); response.addCookie(c);
Observed Examples
Relationships
Taxonomy Mappings
Time of Introduction ImplementationContent History Submissions Anonymous Tool Vendor (under NDA). (Externally Mined) Modifications Sean Eidemiller. Cigital. 2008-07-01. (External) added/updated demonstrative examples Eric Dalci. Cigital. 2008-07-01. (External) updated Potential_Mitigations, Time_of_Introduction CWE Content Team. MITRE. 2008-09-08. (Internal) updated Relationships, Taxonomy_Mappings Previous Entry Names Unset Secure Attribute for Sensitive Cookies in HTTPS Session (changed 2008-04-11) |
|
|
|||