# CVE-2006-4955: Path traversal in n/a

> Remote attackers can read arbitrary files via directory traversal in the downloadfile servlet of Neon WebMail for Java.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mr87-c8m9-c37x

## What is CVE-2006-4955?

CVE-2006-4955 is a medium-severity path traversal vulnerability in n/a, published on 23 Sep 2006. It can be exploited over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in the downloadfile servlet in Neon WebMail for Java before 5.08 allows remote attackers to read arbitrary files via a .. (dot dot) sequence in the (1) savefolder and (2) savefilename parameters.

## Which versions are affected by CVE-2006-4955?

It affects 1 product.


Products: Neosys Neon Webmail.

## How do I fix CVE-2006-4955?

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

## Is CVE-2006-4955 being exploited?

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

Public exploit code:

- NeoSys Neon Webmail for Java 5.06/5.07 - 'downloadfile' Servlet Traversal Arbitrary File Access (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-4951](https://insights.sbomify.com/CVE-2006-4951/): File upload in n/a (high 7.5)
- [CVE-2006-4952](https://insights.sbomify.com/CVE-2006-4952/): Missing authorization in n/a (high 7.5)
- [CVE-2006-4953](https://insights.sbomify.com/CVE-2006-4953/): SQL injection in n/a (high 7.5)
- [CVE-2006-4954](https://insights.sbomify.com/CVE-2006-4954/): Missing authorization in n/a (high 7.5)
- [CVE-2006-4956](https://insights.sbomify.com/CVE-2006-4956/): Cross-site scripting in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4955 and fix it if it is affected.

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

## Sources

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

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