# CVE-2014-0466: Command injection in n/a

> Attackers can execute arbitrary commands or delete files via crafted PostScript files due to missing Ghostscript safety flags in a2ps.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **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 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-0466, GHSA-5wf6-vx35-ff8x, MGASA-2014-0161

## What is CVE-2014-0466?

CVE-2014-0466 is a medium-severity command injection vulnerability in n/a, published on 3 Apr 2014. 

### Official description

The fixps script in a2ps 4.14 does not use the -dSAFER option when executing gs, which allows context-dependent attackers to delete arbitrary files or execute arbitrary commands via a crafted PostScript file.

## Which versions are affected by CVE-2014-0466?

It affects 1 product.


Products: Gnu A2ps.

## How do I fix CVE-2014-0466?

Apply the vendor's patch.

## Is CVE-2014-0466 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-1170](https://insights.sbomify.com/CVE-2004-1170/): Command injection in n/a (critical 10.0)
- [CVE-2015-8107](https://insights.sbomify.com/CVE-2015-8107/): Other in n/a (high 7.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-2014-0466 and fix it if it is affected.

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

## Sources

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

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