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

> Local users can overwrite arbitrary files via symlink attacks on PIM daemon dump/cache files, requiring signal interaction.

- **Severity:** Low 3.3 (`AV:L/AC:M/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Jan 2011
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-0007, DSA-2147-1, GHSA-h6hm-9c4m-mf67

## What is CVE-2011-0007?

CVE-2011-0007 is a low-severity path traversal vulnerability in n/a, published on 11 Jan 2011. 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

pimd 2.1.5 and possibly earlier versions allows user-assisted local users to overwrite arbitrary files via a symlink attack on (1) pimd.dump when a USR1 signal is sent, or (2) pimd.cache when USR2 is sent.

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

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

It affects 1 product.


Products: Troglobit Pimd.

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

Apply the vendor's patch.

## Is CVE-2011-0007 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2011-0007 is a low-severity path traversal vulnerability in n/a, published on 11 Jan 2011. 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-2011-0007 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-0007/ (Markdown: https://insights.sbomify.com/CVE-2011-0007/index.md)
```

## Sources

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

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