Vulnerabilities · 2008 · Google
CVE-2008-7294
Google Chrome vulnerability
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.
Affected products
Chrome. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Google Chrome runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- bugzilla.mozilla.org/show_bug.cgi?id=660053 · Patch
- code.google.com/p/browsersec/wiki/Part2#Same-origin_policy_for_cookies
- lists.w3.org/Archives/Public/public-webapps/2009JulSep/1148.html
- 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
- nvd.nist.gov/vuln/detail/CVE-2008-7294
- cve.org/CVERecord?id=CVE-2008-7294
More vulnerabilities in Google products
CVE-2026-28615CVE-2026-28587CVE-2026-28576CVE-2026-28575CVE-2026-20418CVE-2026-20417CVE-2026-20415CVE-2026-20414All 12,443
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.