# CVE-2009-2180: Path traversal in n/a

> Remote attackers can read arbitrary files via directory traversal in Pc4 Uploader's index.php file parameter.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jun 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-28hq-5337-p2wc

## What is CVE-2009-2180?

CVE-2009-2180 is a medium-severity path traversal vulnerability in n/a, published on 23 Jun 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in upfiles/index.php in Pc4 Uploader 10.0 and earlier allow remote attackers to read arbitrary files via (1) a .. (dot dot) or (2) absolute path in the file parameter.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2009-2180?

It affects 1 product.


Products: Pc4arb Pc4 Uploader.

## How do I fix CVE-2009-2180?

No fix has been published for CVE-2009-2180 yet. Limit exposure of the affected software until one is available.

## Is CVE-2009-2180 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-2180 exists.

Public exploit code:

- pc4 Uploader 10.0 - Remote File Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-1742](https://insights.sbomify.com/CVE-2009-1742/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-2180 and fix it if it is affected.

What it is: CVE-2009-2180 is a medium-severity path traversal vulnerability in n/a, published on 23 Jun 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-2180 exists.

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-2009-2180/ (Markdown: https://insights.sbomify.com/CVE-2009-2180/index.md)
```

## Sources

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

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