CVE-2009-1413: n/a vulnerability

CVE-2009-1413: Google Chrome 1.0.x does not cancel timeouts upon a page transition, which makes it easier for attackers to...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 05:13 UTC (UTC+00:00)

Security readout for executives and security teams

This old Chrome flaw could let a malicious page leave JavaScript scheduled, move the browser to another site, and run that script in the new site's context. That is a universal XSS condition, but the provided sources do not include CVSS, a fixed version, or active exploitation evidence. Exposure should be limited to environments still running Google Chrome 1.0.x or retaining related legacy chromehtml handling. Modern supported Chrome deployments are unlikely to match the described affected branch, but confirm through asset inventory rather than assumption. Treat this as a legacy exposure cleanup item unless evidence shows Chrome 1.0.x remains in use. The business risk is high only on obsolete endpoints because universal XSS can compromise sessions and trusted web workflows. Mitigation focus: Inventory endpoints for Google Chrome 1.0.x or legacy Chromium builds.; Move affected browsers to a supported Chrome release per vendor guidance.; Review Chromium advisory references for the fixed version or documented workaround..

Prepared: Jun 28, 2026, 11:04 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2009-1413 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Apr 24, 2009, 15:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
googlechrome-settimeout-xss(50447)CVE reference · vdb-entry, x_refsource_XF

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.