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

> Attackers can cause a denial of service via CPU consumption by sending usernames with equals signs to Courier MTA.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-2659, DSA-1101, GHSA-jf3h-hc4x-5q33

## What is CVE-2006-2659?

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

### Official description

libs/comverp.c in Courier MTA before 0.53.2 allows attackers to cause a denial of service (CPU consumption) via unknown vectors involving usernames that contain the "=" (equals) character, which is not properly handled during encoding.

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

It affects 1 product.


Products: Double Precision Incorporated Courier Mta.

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

Upgrade to a fixed version.

## Is CVE-2006-2659 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0040](https://insights.sbomify.com/CVE-2003-0040/): SQL injection in n/a (high 7.5)
- [CVE-2004-0224](https://insights.sbomify.com/CVE-2004-0224/): Memory corruption in n/a (high 7.5)
- [CVE-2002-0914](https://insights.sbomify.com/CVE-2002-0914/): Denial of service in n/a (medium 5.0)
- [CVE-2002-1311](https://insights.sbomify.com/CVE-2002-1311/): Information disclosure in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2659 is a high-severity denial of service vulnerability in n/a, published on 30 May 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-2659 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-2659/ (Markdown: https://insights.sbomify.com/CVE-2006-2659/index.md)
```

## Sources

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

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