# CVE-2011-0702: Path traversal in n/a

> Local attackers can overwrite arbitrary files via symlink attacks on temporary files in the feh image viewer.

- **Severity:** Low 3.3 (`AV:L/AC:M/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Feb 2011
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2011-0702, GHSA-jw56-55h4-jxhw

## What is CVE-2011-0702?

CVE-2011-0702 is a low-severity path traversal vulnerability in n/a, published on 14 Feb 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The feh_unique_filename function in utils.c in feh before 1.11.2 might allow local users to overwrite arbitrary files via a symlink attack on a /tmp/feh_ temporary file.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2011-0702?

It affects 1 product.


Products: Feh Project Feh.

## How do I fix CVE-2011-0702?

Upgrade to a fixed version.

## Is CVE-2011-0702 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-7875](https://insights.sbomify.com/CVE-2017-7875/): Integer overflow in n/a (critical 9.8)
- [CVE-2010-2246](https://insights.sbomify.com/CVE-2010-2246/): Command injection in n/a (medium 5.1)
- [CVE-2011-1031](https://insights.sbomify.com/CVE-2011-1031/): Path traversal in n/a (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-0702 and fix it if it is affected.

What it is: CVE-2011-0702 is a low-severity path traversal vulnerability in n/a, published on 14 Feb 2011. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-0702 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-2011-0702/ (Markdown: https://insights.sbomify.com/CVE-2011-0702/index.md)
```

## Sources

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

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