# CVE-2009-2011: Command injection in n/a

> Remote attackers can execute arbitrary commands via a malicious .dxstudio file exploiting unrestricted shell.execute API in DX Studio Player browser plugin.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 16 Jun 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hfvg-qx3h-rpgq

## What is CVE-2009-2011?

CVE-2009-2011 is a critical command injection vulnerability in n/a, published on 16 Jun 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

Worldweaver DX Studio Player 3.0.29.0, 3.0.22.0, 3.0.12.0, and probably other versions before 3.0.29.1, when used as a plug-in for Firefox, does not restrict access to the shell.execute JavaScript API method, which allows remote attackers to execute arbitrary commands via a .dxstudio file that invokes this method.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Dxstudio Dx Studio Player.

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

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

## Is CVE-2009-2011 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-2011 exists.

Public exploit code:

- Worldweaver DX Studio Player shell.execute() Command Execution (metasploit)
- Worldweaver DX Studio Player < 3.0.29.1 Firefox plugin - Command Injection (exploitdb)
- Worldweaver DX Studio Player 3.0.29 - 'shell.execute()' Command Execution (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-2011 is a critical command injection vulnerability in n/a, published on 16 Jun 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-2011 exists.

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-2009-2011/ (Markdown: https://insights.sbomify.com/CVE-2009-2011/index.md)
```

## Sources

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

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