# CVE-2005-4456: Memory corruption in n/a

> Remote attackers can trigger buffer overflows via IMAP commands to crash the server or execute arbitrary code.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **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-3f6p-4492-5fc4

## What is CVE-2005-4456?

CVE-2005-4456 is a high-severity memory corruption 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

Multiple buffer overflows in MailEnable Professional 1.71 and Enterprise 1.1 before patch ME-10009 allow remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via long (1) LIST, (2) LSUB, and (3) UID FETCH commands.  NOTE: it is possible that these are alternate vectors for the issue described in CVE-2005-4402.

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

It affects 2 products.


Products: Mailenable Mailenable Enterprise, Mailenable Mailenable Professional.

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

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

## Is CVE-2005-4456 being exploited?

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

Public exploit code:

- MailEnable Enterprise Edition 1.1 - 'EXAMINE' Remote Buffer Overflow (exploitdb)

## 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-4456 and fix it if it is affected.

What it is: CVE-2005-4456 is a high-severity memory corruption 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-4456 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-2005-4456/ (Markdown: https://insights.sbomify.com/CVE-2005-4456/index.md)
```

## Sources

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

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