# CVE-2002-0410: Path traversal in n/a

> Remote attackers can read arbitrary server files via manipulated attachment filenames in AeroMail, exposing sensitive data.

- **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:** 11 Jun 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-xv2v-3fj4-g6xm

## What is CVE-2002-0410?

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

### Official description

send_message.php in AeroMail before 1.45 allows remote attackers to read arbitrary files on the server, instead of just uploaded files, via an attachment that modifies the filename to be uploaded.

## Which versions are affected by CVE-2002-0410?

It affects 1 product.


Products: Aeromail Aeromail.

## How do I fix CVE-2002-0410?

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

## Is CVE-2002-0410 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-0411](https://insights.sbomify.com/CVE-2002-0411/): Cross-site scripting in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0410 and fix it if it is affected.

What it is: CVE-2002-0410 is a medium-severity path traversal vulnerability in n/a, published on 11 Jun 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-0410 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-2002-0410/ (Markdown: https://insights.sbomify.com/CVE-2002-0410/index.md)
```

## Sources

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

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