# CVE-2006-0637: Buffer overflow in cram.dll in QUALCOMM Eudora WorldMail 3.0 allows remote attackers to execute arbitrary code via an IMAP APPEND command wi


- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p489-2qgm-7765

## What is CVE-2006-0637?

CVE-2006-0637 is a high-severity vulnerability in n/a, published on 10 Feb 2006. 

### Official description

Buffer overflow in cram.dll in QUALCOMM Eudora WorldMail 3.0 allows remote attackers to execute arbitrary code via an IMAP APPEND command with a long message literal argument, as demonstrated by Worldmail.pl. NOTE: this is a different vector and a different manipulation than CVE-2005-4267, so it might be a different vulnerability than CVE-2005-4267.

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

It affects 1 product.


Products: Qualcomm Eudora Worldmail.

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

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

## Is CVE-2006-0637 being exploited?

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

Public exploit code:

- Eudora Qualcomm WorldMail 3.0 - 'IMAPd' Remote Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-6024](https://insights.sbomify.com/CVE-2006-6024/): Memory corruption in n/a (critical 9.8)
- [CVE-2014-10031](https://insights.sbomify.com/CVE-2014-10031/): Memory corruption in n/a (high 7.5)
- [CVE-2006-6025](https://insights.sbomify.com/CVE-2006-6025/): QUALCOMM Eudora WorldMail 4.0 allows remote attackers to cause a denial of service, as demonstrated by a certain module in VulnDisco Pack. (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0637 is a high-severity vulnerability in n/a, published on 10 Feb 2006. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0637 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-2006-0637/ (Markdown: https://insights.sbomify.com/CVE-2006-0637/index.md)
```

## Sources

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

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