# CVE-2019-11595: Code injection in n/a

> Malicious filter lists can execute arbitrary code in the browser via the rewrite option when scripts are loaded through open redirects.

- **Severity:** Critical 9.0 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cq4j-49w3-ppw7

## What is CVE-2019-11595?

CVE-2019-11595 is a critical code injection vulnerability in n/a, published on 29 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In uBlock before 0.9.5.15, the $rewrite filter option allows filter-list maintainers to run arbitrary code in a client-side session when a web service loads a script for execution using XMLHttpRequest or Fetch, and the script origin has an open redirect.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2019-11595?

It affects 1 product.


Products: Ublockorigin Ublock Origin.

## How do I fix CVE-2019-11595?

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

## Is CVE-2019-11595 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11595 and fix it if it is affected.

What it is: CVE-2019-11595 is a critical code injection vulnerability in n/a, published on 29 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-11595 in the wild and no public exploit code.

Affected product: n/a. 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-2019-11595/ (Markdown: https://insights.sbomify.com/CVE-2019-11595/index.md)
```

## Sources

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

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