# CVE-2001-1408: Path traversal in n/a

> Remote attackers can read arbitrary files via directory traversal in the mailbox parameter of WebMail in Cobalt Qube 3.

- **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:** 31 Aug 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-h5vm-pcc6-h2f9

## What is CVE-2001-1408?

CVE-2001-1408 is a medium-severity path traversal vulnerability in n/a, published on 31 Aug 2002. It can be exploited over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in readmsg.php in WebMail 2.0.1 in Cobalt Qube 3 allows remote attackers to read arbitrary files via a .. (dot dot) in the mailbox parameter.

## Which versions are affected by CVE-2001-1408?

It affects 2 products.


Products: Cobalt Qube, Cobalt Webmail.

## How do I fix CVE-2001-1408?

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

## Is CVE-2001-1408 being exploited?

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

Public exploit code:

- Cobalt Qube Webmail 1.0 - Directory Traversal (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-1058](https://insights.sbomify.com/CVE-2002-1058/): Directory traversal vulnerability in splashAdmin.php for Cobalt Qube 3.0 allows local users and remote attackers, to gain privileges as the Qube Admin via .. (critical 10.0)
- [CVE-1999-0831](https://insights.sbomify.com/CVE-1999-0831/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-1408 and fix it if it is affected.

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

## Sources

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

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