Google Chrome before 4.0.211.0 cannot properly restrict modifications to cookies established in HTTPS sessions, which allows man-in-the-middle attackers to overwrite or delete arbitrary cookies via a Set-Cookie header in an HTTP response, related to lack of the HTTP Strict Transport Security (HSTS) includeSubDomains feature, aka a "cookie forcing" issue.
References
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 00:58
Type | Values Removed | Values Added |
---|---|---|
References | () http://code.google.com/p/browsersec/wiki/Part2#Same-origin_policy_for_cookies - | |
References | () http://lists.w3.org/Archives/Public/public-webapps/2009JulSep/1148.html - | |
References | () http://michael-coates.blogspot.com/2010/01/cookie-forcing-trust-your-cookies-no.html - | |
References | () http://scarybeastsecurity.blogspot.com/2008/11/cookie-forcing.html - | |
References | () http://scarybeastsecurity.blogspot.com/2011/02/some-less-obvious-benefits-of-hsts.html - | |
References | () https://bugzilla.mozilla.org/show_bug.cgi?id=660053 - Patch |
Information
Published : 2011-08-09 19:55
Updated : 2024-11-21 00:58
NVD link : CVE-2008-7294
Mitre link : CVE-2008-7294
CVE.ORG link : CVE-2008-7294
JSON object : View
Products Affected
- chrome
CWE
CWE-264
Permissions, Privileges, and Access Controls