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

> Authenticated remote attackers can rename other users' folders via path traversal in the IMAP RENAME command.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:P/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:** No
- **Published:** 9 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2869-r8x6-9882

## What is CVE-2006-0127?

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

### Official description

Directory traversal vulnerability in the IMAP service of Rockliffe MailSite before 6.1.22.1 allows remote authenticated users to rename the folders of other users via a .. (dot dot) in the RENAME command.

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

It affects 1 product.


Products: Rockliffe Mailsite.

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

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

## Is CVE-2006-0127 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-0128](https://insights.sbomify.com/CVE-2006-0128/): Memory corruption in n/a (critical 10.0)
- [CVE-2000-0398](https://insights.sbomify.com/CVE-2000-0398/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-0342](https://insights.sbomify.com/CVE-2006-0342/): Denial of service in n/a (high 7.8)
- [CVE-2006-0130](https://insights.sbomify.com/CVE-2006-0130/): Missing authorization in n/a (high 7.5)
- [CVE-2006-0790](https://insights.sbomify.com/CVE-2006-0790/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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