Google Chrome 1.0.x does not cancel timeouts upon a page transition, which makes it easier for attackers to conduct Universal XSS attacks by calling setTimeout to trigger future execution of JavaScript code, and then modifying document.location to arrange for JavaScript execution in the context of an arbitrary web site. NOTE: this can be leveraged for a remote attack by exploiting a chromehtml: argument-injection vulnerability.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Chrome | 1.0.154.36 (including) | 1.0.154.36 (including) | |
| Chrome | 1.0.154.39 (including) | 1.0.154.39 (including) | |
| Chrome | 1.0.154.42 (including) | 1.0.154.42 (including) | |
| Chrome | 1.0.154.43 (including) | 1.0.154.43 (including) | |
| Chrome | 1.0.154.46 (including) | 1.0.154.46 (including) | |
| Chrome | 1.0.154.53 (including) | 1.0.154.53 (including) | |
| Chrome | 1.0.154.59 (including) | 1.0.154.59 (including) |
References
- http://chromium.googlecode.com/issues/attachment?aid=5579180911289877192\u0026name=Google+Chrome+Advisory.doc
- http://code.google.com/p/chromium/issues/detail?id=9860
- https://exchange.xforce.ibmcloud.com/vulnerabilities/50447
- http://chromium.googlecode.com/issues/attachment?aid=5579180911289877192\u0026name=Google+Chrome+Advisory.doc
- http://code.google.com/p/chromium/issues/detail?id=9860
- https://exchange.xforce.ibmcloud.com/vulnerabilities/50447