First published: Mon Aug 31 2009(Updated: )
Google Chrome 1.0.154.48 and earlier, 2.0.172.28, 2.0.172.37, and 3.0.193.2 Beta does not properly block data: URIs in Refresh headers in HTTP responses, which allows remote attackers to conduct cross-site scripting (XSS) attacks via vectors related to (1) injecting a Refresh header that contains JavaScript sequences in a data:text/html URI or (2) entering a data:text/html URI with JavaScript sequences when specifying the content of a Refresh header. NOTE: the JavaScript executes outside of the context of the HTTP site.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Google Chrome | <=1.0.154.48 | |
Google Chrome | =0.2.149.27 | |
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 | |
Google Chrome | =2.0.172.28 | |
Google Chrome | =2.0.172.37 | |
Google Chrome | =3.0.193.2-beta |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.