# 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.


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Nov 2006
- **Updated:** 3 Apr 2025
- **Also known as:** GHSA-r65h-347c-jjp4

## What is CVE-2006-6025?

CVE-2006-6025 is a high-severity vulnerability in n/a, published on 21 Nov 2006. 

### Official description

QUALCOMM Eudora WorldMail 4.0 allows remote attackers to cause a denial of service, as demonstrated by a certain module in VulnDisco Pack.  NOTE: The provenance of this information is unknown; the details are obtained solely from third party information. As of 20061118, this disclosure has no actionable information. However, because the VulnDisco Pack author is a reliable researcher, the issue is being assigned a CVE identifier for tracking purposes.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Qualcomm Eudora Worldmail.

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

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

## Is CVE-2006-6025 being exploited?

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

## 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-0637](https://insights.sbomify.com/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 (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6025 is a high-severity vulnerability in n/a, published on 21 Nov 2006. 
Exploitation: There is no known exploitation of CVE-2006-6025 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-6025/ (Markdown: https://insights.sbomify.com/CVE-2006-6025/index.md)
```

## Sources

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

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