# CVE-2006-0449: Denial of service in n/a

> Remote attackers can cause a denial of service in E-Post Mail and SPA-PRO Mail by triggering an infinite loop via a malformed IMAP APPEND command.

- **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:** 27 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3chq-78vx-cp74

## What is CVE-2006-0449?

CVE-2006-0449 is a medium-severity denial of service vulnerability in n/a, published on 27 Jan 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Early termination vulnerability in the IMAP service in E-Post Mail 4.05 and SPA-PRO Mail 4.05 allows remote attackers to cause a denial of service (infinite loop) by sending an APPEND command and disconnecting before the expected amount of data is sent.

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

It affects 2 products.


Products: E-Post Corporation Mail Server, E-Post Corporation Spa-Pro Mail Atsolomon.

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

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

## Is CVE-2006-0449 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-0447](https://insights.sbomify.com/CVE-2006-0447/): Memory corruption in n/a (high 7.5)
- [CVE-2006-0448](https://insights.sbomify.com/CVE-2006-0448/): Path traversal in n/a (high 7.5)
- [CVE-2008-2049](https://insights.sbomify.com/CVE-2008-2049/): Information disclosure in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0449 is a medium-severity denial of service vulnerability in n/a, published on 27 Jan 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-0449 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-0449/ (Markdown: https://insights.sbomify.com/CVE-2006-0449/index.md)
```

## Sources

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

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