First published: Mon Jun 15 2009(Updated: )
Google Chrome before 1.0.154.53 displays a cached certificate for a (1) 4xx or (2) 5xx CONNECT response page returned by a proxy server, which allows man-in-the-middle attackers to spoof an arbitrary https site by letting a browser obtain a valid certificate from this site during one request, and then sending the browser a crafted 502 response page upon a subsequent request.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Google Chrome | <=1.0.154.52 | |
Google Chrome | =0.2.149.29 | |
Google Chrome | =0.2.149.30 | |
Google Chrome | =0.2.152.1 | |
Google Chrome | =0.2.153.1 | |
Google Chrome | =0.3.154.0 | |
Google Chrome | =0.3.154.3 | |
Google Chrome | =0.4.154.18 | |
Google Chrome | =0.4.154.22 | |
Google Chrome | =0.4.154.31 | |
Google Chrome | =0.4.154.33 | |
Google Chrome | =1.0.154.36 | |
Google Chrome | =1.0.154.39 | |
Google Chrome | =1.0.154.42 | |
Google Chrome | =1.0.154.43 | |
Google Chrome | =1.0.154.46 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.