# CVE-2005-2851: Path traversal in n/a

> Local attackers can read sensitive files via symlink attacks on temporary files in smb4k, requiring local access.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Sep 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-2851, DTSA-25-1, GHSA-m29r-x48f-4j3v

## What is CVE-2005-2851?

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

### Official description

smb4k 0.4 and other versions before 0.6.3 allows local users to read sensitive files via a symlink attack on the (1) smb4k.tmp or (2) sudoers temporary files.

## Which versions are affected by CVE-2005-2851?

It affects 1 product.


Products: Smb4k Smb4k.

## How do I fix CVE-2005-2851?

Upgrade to a fixed version.

## Is CVE-2005-2851 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0475](https://insights.sbomify.com/CVE-2007-0475/): Memory corruption in n/a (medium 4.4)
- [CVE-2007-0472](https://insights.sbomify.com/CVE-2007-0472/): Race condition in n/a (low 3.7)
- [CVE-2007-0474](https://insights.sbomify.com/CVE-2007-0474/): Privilege escalation in n/a (low 3.3)
- [CVE-2007-0473](https://insights.sbomify.com/CVE-2007-0473/): Information disclosure in n/a (low 1.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2851 and fix it if it is affected.

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

## Sources

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

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