# CVE-2005-4457: Path traversal in n/a

> Remote attackers can cause a crash or execute arbitrary code via path traversal sequences in the UID FETCH command of MailEnable Enterprise.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 21 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vx4g-c7q3-585r

## What is CVE-2005-4457?

CVE-2005-4457 is a high-severity path traversal vulnerability in n/a, published on 21 Dec 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MailEnable Enterprise 1.1 before patch ME-10009 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via several "..." (triple dot) sequences in a UID FETCH command.

## Which versions are affected by CVE-2005-4457?

It affects 1 product.


Products: Mailenable Mailenable Enterprise.

## How do I fix CVE-2005-4457?

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

## Is CVE-2005-4457 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-6997](https://insights.sbomify.com/CVE-2006-6997/): Weak cryptography in n/a (critical 10.0)
- [CVE-2006-6605](https://insights.sbomify.com/CVE-2006-6605/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-6423](https://insights.sbomify.com/CVE-2006-6423/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-1792](https://insights.sbomify.com/CVE-2006-1792/): Auth bypass in n/a (critical 10.0)
- [CVE-2006-5176](https://insights.sbomify.com/CVE-2006-5176/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4457 and fix it if it is affected.

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

## Sources

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

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