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

> Attackers can execute arbitrary commands via shell metacharacters in filenames when unp processes archives, requiring user interaction to trigger.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Jan 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-6610, GHSA-r9r9-p68f-q4fg

## What is CVE-2007-6610?

CVE-2007-6610 is a critical command injection vulnerability in n/a, published on 3 Jan 2008. 

### Official description

unp 1.0.12, and other versions before 1.0.14, does not properly escape file names, which might allow context-dependent attackers to execute arbitrary commands via shell metacharacters in a filename argument. NOTE: this might only be a vulnerability when unp is invoked by a third party product.

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

It affects 1 product.


Products: Debian Unp.

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

Upgrade to a fixed version.

## Is CVE-2007-6610 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-6610 is a critical command injection vulnerability in n/a, published on 3 Jan 2008. 
Exploitation: There is no known exploitation of CVE-2007-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-2007-6610/ (Markdown: https://insights.sbomify.com/CVE-2007-6610/index.md)
```

## Sources

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

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