CVE-2009-3011
Last modified
CVE-2009-3011 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.94% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Chrome | <= 1.0.154.48 | — | |
| Chrome | 0.2.149.27 | — | |
| Chrome | 0.2.149.29 | — | |
| Chrome | 0.2.149.30 | — | |
| Chrome | 0.2.152.1 | — | |
| Chrome | 0.2.153.1 | — | |
| Chrome | 0.3.154.0 | — | |
| Chrome | 0.3.154.3 | — | |
| Chrome | 0.4.154.18 | — | |
| Chrome | 0.4.154.22 | — | |
| Chrome | 0.4.154.31 | — | |
| Chrome | 0.4.154.33 | — | |
| Chrome | 1.0.154.36 | — | |
| Chrome | 1.0.154.39 | — | |
| Chrome | 1.0.154.42 | — | |
| Chrome | 1.0.154.43 | — | |
| Chrome | 1.0.154.46 | — | |
| Chrome | 2.0.172.28 | — | |
| Chrome | 2.0.172.37 | — | |
| Chrome | 3.0.193.2 | Beta |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2009-3011?
How severe is CVE-2009-3011?
How do I fix CVE-2009-3011?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2009
- CVE-2009-3005Lunascape 5.1.3 and 5.1.4 allows remote attackers to spoof t…
- CVE-2009-3006Maxthon Browser 2.5.3.80 UNICODE allows remote attackers to …
- CVE-2009-3007Mozilla Firefox 3.5.1 and SeaMonkey 1.1.17, and Flock 2.5.1,…
- CVE-2009-3008K-Meleon 1.5.3 allows context-dependent attackers to spoof t…
- CVE-2009-3009Cross-site scripting (XSS) vulnerability in Ruby on Rails 2.…
- CVE-2009-3010Mozilla Firefox 3.0.13 and earlier, 3.5, 3.6 a1 pre, and 3.7…
- CVE-2009-3012Mozilla Firefox 3.0.13 and earlier, 3.5, 3.6 a1 pre, and 3.7…
- CVE-2009-3013Opera 9.52 and earlier, and 10.00 Beta 3 Build 1699, does no…
- CVE-2009-3014Mozilla Firefox 3.0.13 and earlier, 3.5, 3.6 a1 pre, and 3.7…
- CVE-2009-3015QtWeb 3.0 Builds 001 and 003 does not properly block javascr…
- CVE-2009-3016Apple Safari 4.0.3 does not properly block javascript: and d…
- CVE-2009-3017Orca Browser 1.2 build 5 does not properly block data: URIs …
Are you affected by CVE-2009-3011?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST