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.
Metrics
Affected Vendors & Products
References
History
No history.
MITRE
Status: PUBLISHED
Assigner: mitre
Published: 2009-04-24T15:00:00
Updated: 2024-08-07T05:13:25.392Z
Reserved: 2009-04-24T00:00:00
Link: CVE-2009-1413
Vulnrichment
No data.
NVD
Status : Modified
Published: 2009-04-24T15:30:00.297
Modified: 2024-11-21T01:02:24.103
Link: CVE-2009-1413
Redhat
No data.