# CVE-2010-0011: Code injection in n/a

> Remote attackers can execute arbitrary commands via JavaScript due to exposed run method in Uzbl browser.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 25 Feb 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h8hq-vp3m-hv4f

## What is CVE-2010-0011?

CVE-2010-0011 is a high-severity code injection vulnerability in n/a, published on 25 Feb 2010. 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

The eval_js function in uzbl-core.c in Uzbl before 2010.01.05 exposes the run method of the Uzbl object, which allows remote attackers to execute arbitrary commands via JavaScript code.

Weakness: CWE-264

## Which versions are affected by CVE-2010-0011?

It affects 1 product.


Products: Uzbl Uzbl.

## How do I fix CVE-2010-0011?

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

## Is CVE-2010-0011 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-2809](https://insights.sbomify.com/CVE-2010-2809/): Code injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0011 and fix it if it is affected.

What it is: CVE-2010-0011 is a high-severity code injection vulnerability in n/a, published on 25 Feb 2010. 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-2010-0011 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-2010-0011/ (Markdown: https://insights.sbomify.com/CVE-2010-0011/index.md)
```

## Sources

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

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