# CVE-2014-2095: Path traversal in n/a

> Local attackers can gain privileges by placing a malicious Python bytecode file in the current working directory when using non-Fedora packages.

- **Severity:** Medium 4.6 (`AV:L/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:** 26 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-2095, GHSA-437w-v33j-rq35

## What is CVE-2014-2095?

CVE-2014-2095 is a medium-severity path traversal vulnerability in n/a, published on 26 Feb 2014. 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

Untrusted search path vulnerability in Catfish 0.6.0 through 1.0.0, when a Fedora package such as 0.8.2-1 is not used, allows local users to gain privileges via a Trojan horse bin/catfish.pyc under the current working directory.

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

It affects 1 product.


Products: Catfish Project Catfish.

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

Upgrade to a fixed version.

## Is CVE-2014-2095 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-2093](https://insights.sbomify.com/CVE-2014-2093/): Path traversal in n/a (medium 4.6)
- [CVE-2014-2094](https://insights.sbomify.com/CVE-2014-2094/): Path traversal in n/a (medium 4.6)
- [CVE-2014-2096](https://insights.sbomify.com/CVE-2014-2096/): Path traversal in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2095 is a medium-severity path traversal vulnerability in n/a, published on 26 Feb 2014. 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-2095 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-2095/ (Markdown: https://insights.sbomify.com/CVE-2014-2095/index.md)
```

## Sources

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

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