Google Chrome 1.0.154.48 and earlier, 2.0.172.28, 2.0.172.37, and 3.0.193.2 Beta does not properly block data: URIs in Refresh headers in HTTP responses, which allows remote attackers to conduct cross-site scripting (XSS) attacks via vectors related to (1) injecting a Refresh header that contains JavaScript sequences in a data:text/html URI or (2) entering a data:text/html URI with JavaScript sequences when specifying the content of a Refresh header. NOTE: the JavaScript executes outside of the context of the HTTP site.
2009-08-31T16:30:06.860
2025-04-09T00:30:58.490
Deferred
CVSSv2: 4.3 (MEDIUM)
AV:N/AC:M/Au:N/C:N/I:P/A:N
8.6
2.9
Type | Vendor | Product | Version/Range | Vulnerable? |
---|---|---|---|---|
Application | chrome | ≤ 1.0.154.48 | Yes | |
Application | chrome | 0.2.149.27 | Yes | |
Application | chrome | 0.2.149.29 | Yes | |
Application | chrome | 0.2.149.30 | Yes | |
Application | chrome | 0.2.152.1 | Yes | |
Application | chrome | 0.2.153.1 | Yes | |
Application | chrome | 0.3.154.0 | Yes | |
Application | chrome | 0.3.154.3 | Yes | |
Application | chrome | 0.4.154.18 | Yes | |
Application | chrome | 0.4.154.22 | Yes | |
Application | chrome | 0.4.154.31 | Yes | |
Application | chrome | 0.4.154.33 | Yes | |
Application | chrome | 1.0.154.36 | Yes | |
Application | chrome | 1.0.154.39 | Yes | |
Application | chrome | 1.0.154.42 | Yes | |
Application | chrome | 1.0.154.43 | Yes | |
Application | chrome | 1.0.154.46 | Yes | |
Application | chrome | 2.0.172.28 | Yes | |
Application | chrome | 2.0.172.37 | Yes | |
Application | chrome | 3.0.193.2 | Yes |