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

> Remote attackers can create or delete arbitrary directories in YaPiG via path traversal in the dir parameter of upload.php.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jun 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-5f5c-9qpc-p4vg

## What is CVE-2005-1884?

CVE-2005-1884 is a medium-severity path traversal vulnerability in n/a, published on 7 Jun 2005. It can be exploited over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in the (1) rmdir or (2) mkdir commands in upload.php in YaPiG 0.92b, 0.93u and 0.94u allows remote attackers to create or delete arbitrary directories via a .. (dot dot) in the dir parameter.

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

It affects 1 product.


Products: Yapig Yapig.

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

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

## Is CVE-2005-1884 being exploited?

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

Public exploit code:

- YaPiG 0.9x - 'upload.php' Directory Traversal (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-4800](https://insights.sbomify.com/CVE-2005-4800/): Code injection in n/a (critical 9.0)
- [CVE-2005-4801](https://insights.sbomify.com/CVE-2005-4801/): Cross-site request forgery in n/a (high 7.5)
- [CVE-2005-1881](https://insights.sbomify.com/CVE-2005-1881/): File upload in n/a (high 7.5)
- [CVE-2005-1882](https://insights.sbomify.com/CVE-2005-1882/): Code injection in n/a (high 7.5)
- [CVE-2007-4951](https://insights.sbomify.com/CVE-2007-4951/): Code injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1884 is a medium-severity path traversal vulnerability in n/a, published on 7 Jun 2005. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1884 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-2005-1884/ (Markdown: https://insights.sbomify.com/CVE-2005-1884/index.md)
```

## Sources

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

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