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.
References
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 01:02
Type | Values Removed | Values Added |
---|---|---|
References | () http://chromium.googlecode.com/issues/attachment?aid=5579180911289877192&name=Google+Chrome+Advisory.doc - Vendor Advisory | |
References | () http://code.google.com/p/chromium/issues/detail?id=9860 - | |
References | () https://exchange.xforce.ibmcloud.com/vulnerabilities/50447 - |
Information
Published : 2009-04-24 15:30
Updated : 2024-11-21 01:02
NVD link : CVE-2009-1413
Mitre link : CVE-2009-1413
CVE.ORG link : CVE-2009-1413
JSON object : View
Products Affected
- chrome
CWE
CWE-264
Permissions, Privileges, and Access Controls