# CVE-2006-6610: Command injection in n/a

> Remote attackers can inject console commands into the Nexuiz game client, potentially leading to arbitrary code execution.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 18 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-6610, GHSA-6mc8-ch4h-xh9f

## What is CVE-2006-6610?

CVE-2006-6610 is a high-severity command injection vulnerability in n/a, published on 18 Dec 2006. It can be exploited over the network.

### Official description

clientcommands in Nexuiz before 2.2.1 has unknown impact and remote attack vectors related to "remote console command injection."

## Which versions are affected by CVE-2006-6610?

It affects 1 product.


Products: Alientrap Nexuiz.

## How do I fix CVE-2006-6610?

Upgrade to a fixed version.

## Is CVE-2006-6610 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0657](https://insights.sbomify.com/CVE-2007-0657/): Path traversal in n/a (high 7.5)
- [CVE-2006-6609](https://insights.sbomify.com/CVE-2006-6609/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-6610 and fix it if it is affected.

What it is: CVE-2006-6610 is a high-severity command injection vulnerability in n/a, published on 18 Dec 2006. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2006-6610 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-2006-6610/ (Markdown: https://insights.sbomify.com/CVE-2006-6610/index.md)
```

## Sources

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

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