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

> Attackers can execute arbitrary commands via shell metacharacters in filenames when using run-mailcap in Debian mime-support.

- **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 needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Jan 2015
- **Updated:** 14 Oct 2026
- **Also known as:** DEBIAN-CVE-2014-7209, DLA-125-1, DSA-3114-1, GHSA-5w9q-jf7m-rmj2, UBUNTU-CVE-2014-7209, USN-2453-1

## What is CVE-2014-7209?

CVE-2014-7209 is a high-severity command injection vulnerability in n/a, published on 6 Jan 2015. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

run-mailcap in the Debian mime-support package before 3.52-1+deb7u1 allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a filename.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 1 product.


Products: Debian Mime-Support.

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

Upgrade to a fixed version.

## Is CVE-2014-7209 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0214](https://insights.sbomify.com/CVE-2003-0214/): Path traversal in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-7209 and fix it if it is affected.

What it is: CVE-2014-7209 is a high-severity command injection vulnerability in n/a, published on 6 Jan 2015. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-7209 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-7209/ (Markdown: https://insights.sbomify.com/CVE-2014-7209/index.md)
```

## Sources

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

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