# CVE-2005-2223: Denial of service in n/a

> Remote attackers can crash the MailEnable SMTP service during authentication, causing a denial of service.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 12 Jul 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-5874-jrx9-mcpx

## What is CVE-2005-2223?

CVE-2005-2223 is a medium-severity denial of service vulnerability in n/a, published on 12 Jul 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unknown vulnerability in the SMTP service in MailEnable Standard before 1.9 and Professional before 1.6 allows remote attackers to cause a denial of service (crash) during authentication.

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

It affects 2 products.


Products: Mailenable Mailenable Professional, Mailenable Mailenable Standard.

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

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

## Is CVE-2005-2223 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2222](https://insights.sbomify.com/CVE-2005-2222/): Other in n/a (critical 10.0)
- [CVE-2005-2278](https://insights.sbomify.com/CVE-2005-2278/): Memory corruption in n/a (high 7.2)
- [CVE-2007-0652](https://insights.sbomify.com/CVE-2007-0652/): Cross-site request forgery in n/a (medium 5.1)
- [CVE-2006-0503](https://insights.sbomify.com/CVE-2006-0503/): Denial of service in n/a (medium 5.0)
- [CVE-2007-0651](https://insights.sbomify.com/CVE-2007-0651/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2223 is a medium-severity denial of service vulnerability in n/a, published on 12 Jul 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-2223 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-2223/ (Markdown: https://insights.sbomify.com/CVE-2005-2223/index.md)
```

## Sources

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

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