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

> Remote attackers can crash the MailEnable mail server by sending malicious format string specifiers in the mailto field.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-83xw-w29w-x4x9

## What is CVE-2005-0804?

CVE-2005-0804 is a medium-severity memory corruption vulnerability in n/a, published on 20 Mar 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Format string vulnerability in MailEnable 1.8 allows remote attackers to cause a denial of service (application crash) via format string specifiers in the mailto field.

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

It affects 1 product.


Products: Mailenable Mailenable Standard.

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

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

## Is CVE-2005-0804 being exploited?

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

Public exploit code:

- MailEnable 1.8 - Remote Format String Denial of Service (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0804 is a medium-severity memory corruption vulnerability in n/a, published on 20 Mar 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0804 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-0804/ (Markdown: https://insights.sbomify.com/CVE-2005-0804/index.md)
```

## Sources

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

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