CVE-2009-1413: XSS
First published: Fri Apr 24 2009(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| 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 | =1.0.154.53 | |
| Google Chrome | =1.0.154.59 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- agent/type
- agent/description
- agent/last-modified-date
- agent/softwarecombine
- agent/first-publish-date
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- agent/severity
- agent/author
- agent/weakness
- agent/references
- agent/tags
- agent/event
- collector/mitre-cve
- source/MITRE
- vendor/google
- canonical/google chrome
- version/google chrome/1.0.154.36
- version/google chrome/1.0.154.39
- version/google chrome/1.0.154.42
- version/google chrome/1.0.154.43
- version/google chrome/1.0.154.46
- version/google chrome/1.0.154.53
- version/google chrome/1.0.154.59