# CVE-2004-1170: Command injection in n/a

> Remote attackers can execute arbitrary commands via shell metacharacters in filenames processed by a2ps.

- **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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Dec 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-1170, DSA-612-1, GHSA-6hxv-9334-gpvg

## What is CVE-2004-1170?

CVE-2004-1170 is a critical command injection vulnerability in Suse Suse Linux, published on 10 Dec 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

a2ps 4.13 allows remote attackers to execute arbitrary commands via shell metacharacters in the filename.

## Which versions are affected by CVE-2004-1170?

It affects 3 products.


Products: Gnu A2ps, Sun Java Desktop System, Suse Suse Linux.

## How do I fix CVE-2004-1170?

Upgrade to a fixed version.

## Is CVE-2004-1170 being exploited?

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

Public exploit code:

- GNU a2ps 4.13 - File Name Command Execution (exploitdb)

## Other vulnerabilities in Suse Suse Linux

- [CVE-2015-8107](https://insights.sbomify.com/CVE-2015-8107/): Other in n/a (high 7.8)
- [CVE-2014-0466](https://insights.sbomify.com/CVE-2014-0466/): Command injection in n/a (medium 6.8)
- [CVE-2001-1593](https://insights.sbomify.com/CVE-2001-1593/): Path traversal in n/a (low 2.1)
- [CVE-2004-1377](https://insights.sbomify.com/CVE-2004-1377/): Path traversal in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1170 and fix it if it is affected.

What it is: CVE-2004-1170 is a critical command injection vulnerability in Suse Suse Linux, published on 10 Dec 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-1170 exists.

Affected product: Suse Suse Linux. 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-2004-1170/ (Markdown: https://insights.sbomify.com/CVE-2004-1170/index.md)
```

## Sources

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

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