# CVE-2009-3011: Cross-site scripting in n/a

> Remote attackers can execute JavaScript via data URIs in Refresh headers, enabling cross-site scripting attacks against Google Chrome users.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-frx8-mqfc-pcm6

## What is CVE-2009-3011?

CVE-2009-3011 is a medium-severity cross-site scripting vulnerability in Google Chrome, published on 31 Aug 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2009-3011?

It affects 1 product.


Products: Google Chrome.

## How do I fix CVE-2009-3011?

No fix has been published for CVE-2009-3011 yet. Limit exposure of the affected software until one is available.

## Is CVE-2009-3011 being exploited?

There is no known exploitation of CVE-2009-3011 in the wild and no public exploit code.

## Other vulnerabilities in Google Chrome

- [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild)
- [CVE-2026-85046](https://insights.sbomify.com/CVE-2026-85046/): Google Chromium V8 Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-3011 and fix it if it is affected.

What it is: CVE-2009-3011 is a medium-severity cross-site scripting vulnerability in Google Chrome, published on 31 Aug 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2009-3011 in the wild and no public exploit code.

Affected product: Google Chrome. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2009-3011/ (Markdown: https://insights.sbomify.com/CVE-2009-3011/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2009-3011
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2009-3011
- OSV: https://osv.dev/vulnerability/CVE-2009-3011

---
From sbomify Insights: https://insights.sbomify.com/CVE-2009-3011/
Summaries are generated and may contain mistakes; the official description above is the record.