# CVE-2008-6936: Command injection in n/a

> Remote attackers can inject command line arguments via crafted URIs in Exodus, leading to file overwrites, denial of service, or code execution.

- **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:** 11 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jqx5-rg54-8gq4

## What is CVE-2008-6936?

CVE-2008-6936 is a critical command injection vulnerability in n/a, published on 11 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

Argument injection vulnerability in Exodus 0.10 allows remote attackers to inject arbitrary command line arguments, overwrite arbitrary files, and cause a denial of service via encoded spaces in a pres:// URI, a different vector than CVE-2008-6935.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2008-6936?

It affects 1 product.


Products: Jabber Exodus.

## How do I fix CVE-2008-6936?

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

## Is CVE-2008-6936 being exploited?

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

Public exploit code:

- Exodus 0.10 - URI Handler Arbitrary Parameter Injection (1) (exploitdb)
- Exodus 0.10 - URI Handler Arbitrary Parameter Injection (2) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-6937](https://insights.sbomify.com/CVE-2008-6937/): Command injection in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-6936 and fix it if it is affected.

What it is: CVE-2008-6936 is a critical command injection vulnerability in n/a, published on 11 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-6936 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-2008-6936/ (Markdown: https://insights.sbomify.com/CVE-2008-6936/index.md)
```

## Sources

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

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