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.
CPE | Name | Operator | Version |
---|---|---|---|
chrome | eq | 2.0.172.8 | |
chrome | eq | 0.3.154.3 | |
chrome | eq | 3.0.182.2 | |
chrome | eq | 0.2.149.30 | |
chrome | eq | 0.4.154.31 | |
chrome | le | 3.0.195.38 | |
chrome | eq | 1.0.154.39 | |
chrome | eq | 2.0.172.38 | |
chrome | eq | 1.0.154.59 | |
chrome | eq | 0.2.149.27 |
lists.w3.org/Archives/Public/public-webapps/2009JulSep/1148.html
bugzilla.mozilla.org/show_bug.cgi?id=660053
code.google.com/p/browsersec/wiki/Part2
michael-coates.blogspot.com/2010/01/cookie-forcing-trust-your-cookies-no.html
scarybeastsecurity.blogspot.com/2008/11/cookie-forcing.html
scarybeastsecurity.blogspot.com/2011/02/some-less-obvious-benefits-of-hsts.html