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

> Remote attackers can list files and obtain mailbox names via directory traversal in Dovecot IMAP commands.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-2414, DSA-1080-1, GHSA-w66v-p2rf-jx67

## What is CVE-2006-2414?

CVE-2006-2414 is a medium-severity path traversal vulnerability in n/a, published on 16 May 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in Dovecot 1.0 beta and 1.0 allows remote attackers to list files and directories under the mbox parent directory and obtain mailbox names via ".." sequences in the (1) LIST or (2) DELETE IMAP command.

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

It affects 1 product.


Products: Timo Sirainen Dovecot.

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

Upgrade to a fixed version.

## Is CVE-2006-2414 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5973](https://insights.sbomify.com/CVE-2006-5973/): Memory corruption in n/a (medium 5.0)
- [CVE-2006-0730](https://insights.sbomify.com/CVE-2006-0730/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2414 is a medium-severity path traversal vulnerability in n/a, published on 16 May 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-2414 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-2006-2414/ (Markdown: https://insights.sbomify.com/CVE-2006-2414/index.md)
```

## Sources

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

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