CVE-2008-7294
09.08.2011, 19:55
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.Enginsight
| Vendor | Product | Version |
|---|---|---|
| chrome | 𝑥 ≤ 3.0.195.38 | |
| chrome | 0.1.38.1 | |
| chrome | 0.1.38.2 | |
| chrome | 0.1.38.4 | |
| chrome | 0.1.40.1 | |
| chrome | 0.1.42.2 | |
| chrome | 0.1.42.3 | |
| chrome | 0.2.149.27 | |
| chrome | 0.2.149.29 | |
| chrome | 0.2.149.30 | |
| chrome | 0.2.152.1 | |
| chrome | 0.2.153.1 | |
| chrome | 0.3.154.0 | |
| chrome | 0.3.154.3 | |
| chrome | 0.4.154.18 | |
| chrome | 0.4.154.22 | |
| chrome | 0.4.154.31 | |
| chrome | 0.4.154.33 | |
| chrome | 1.0.154.36 | |
| chrome | 1.0.154.39 | |
| chrome | 1.0.154.42 | |
| chrome | 1.0.154.43 | |
| chrome | 1.0.154.46 | |
| chrome | 1.0.154.48 | |
| chrome | 1.0.154.52 | |
| chrome | 1.0.154.53 | |
| chrome | 1.0.154.59 | |
| chrome | 1.0.154.64 | |
| chrome | 1.0.154.65 | |
| chrome | 2.0.156.1 | |
| chrome | 2.0.157.0 | |
| chrome | 2.0.157.2 | |
| chrome | 2.0.158.0 | |
| chrome | 2.0.159.0 | |
| chrome | 2.0.169.0 | |
| chrome | 2.0.169.1 | |
| chrome | 2.0.170.0 | |
| chrome | 2.0.172 | |
| chrome | 2.0.172.2 | |
| chrome | 2.0.172.8 | |
| chrome | 2.0.172.27 | |
| chrome | 2.0.172.28 | |
| chrome | 2.0.172.30 | |
| chrome | 2.0.172.31 | |
| chrome | 2.0.172.33 | |
| chrome | 2.0.172.37 | |
| chrome | 2.0.172.38 | |
| chrome | 3.0.182.2 | |
| chrome | 3.0.190.2 | |
| chrome | 3.0.193.2:beta | |
| chrome | 3.0.195.2 | |
| chrome | 3.0.195.21 | |
| chrome | 3.0.195.24 | |
| chrome | 3.0.195.25 | |
| chrome | 3.0.195.27 | |
| chrome | 3.0.195.32 | |
| chrome | 3.0.195.33 | |
| chrome | 3.0.195.36 | |
| chrome | 3.0.195.37 |
𝑥
= Vulnerable software versions
Ubuntu Releases
Common Weakness Enumeration
References