# CVE-2010-2945: Path traversal in n/a

> Local attackers can gain privileges by placing a Trojan horse program in the current working directory due to insecure default path configuration in SLiM.

- **Severity:** Medium 6.9 (`AV:L/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 30 Aug 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-2945, GHSA-62w8-6xpw-2cc6

## What is CVE-2010-2945?

CVE-2010-2945 is a medium-severity path traversal vulnerability in n/a, published on 30 Aug 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The default configuration of SLiM before 1.3.2 places ./ (dot slash) at the beginning of the default_path option, which might allow local users to gain privileges via a Trojan horse program in the current working directory, related to slim.conf and cfg.cpp.

Weakness: CWE-16

## Which versions are affected by CVE-2010-2945?

It affects 1 product.


Products: Simone Rota Slim Simple Login Manager.

## How do I fix CVE-2010-2945?

Upgrade to a fixed version.

## Is CVE-2010-2945 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-1756](https://insights.sbomify.com/CVE-2009-1756/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2945 and fix it if it is affected.

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

## Sources

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

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