# CVE-2004-2617: Path traversal in n/a

> Remote attackers can read arbitrary files outside the web root in Pegasi Web Server via directory traversal in the URI.

- **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:** 4 Dec 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-mmjh-9xp6-78rw

## What is CVE-2004-2617?

CVE-2004-2617 is a medium-severity path traversal vulnerability in n/a, published on 4 Dec 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in Pegasi Web Server (PWS) 0.2.2 allows remote attackers to read files outside of the web root via a .. (dot dot) directly after the initial '/' (slash) in the URI.

## Which versions are affected by CVE-2004-2617?

It affects 1 product.


Products: Pegasi Web Server Pegasi Web Server.

## How do I fix CVE-2004-2617?

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

## Is CVE-2004-2617 being exploited?

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

Public exploit code:

- Pegasi Web Server 0.2.2 - Arbitrary File Access (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-2618](https://insights.sbomify.com/CVE-2004-2618/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2617 and fix it if it is affected.

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

## Sources

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

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