CVE-2006-0637
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBuffer 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceBuffer overflow vulnerability in cram.dll of QUALCOMM Eudora WorldMail 3.0 allows remote attackers to execute arbitrary code via a specially crafted IMAP APPEND command containing an overly long message literal argument. This is a distinct vulnerability from CVE-2005-4267 with a different attack vector.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Eudora WorldMail is installedCheck the system for presence of QUALCOMM Eudora WorldMail email server software. Look in Program Files or registry for WorldMail installation directories.Affected if The software is not installed - not affected. If installed, continue to version check.
-
Confirm installed version is 3.0Locate the WorldMail installation directory and check version information for the server components, or use system utilities to query the installed version of QUALCOMM Eudora WorldMail.Affected if Installed version is exactly 3.0 - vulnerable. Versions other than 3.0 are not affected by this specific CVE.
-
Verify IMAP service is enabledCheck if the IMAP service is running and accessible on the mail server. This can be done by attempting to connect to port 143 (IMAP) or checking service configuration.Affected if IMAP service is disabled or not listening - the attack surface may be reduced, but the vulnerability still exists in the code if WorldMail 3.0 is installed.
-
Inspect cram.dll versionLocate cram.dll within the WorldMail installation directory and check its file properties for version information.Affected if cram.dll exists in WorldMail 3.0 installation - the vulnerable component is present.
A system is affected if QUALCOMM Eudora WorldMail version 3.0 is installed with IMAP service enabled, as the buffer overflow vulnerability in cram.dll is triggered via crafted IMAP APPEND commands.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataSince this is a 2006 vulnerability in likely discontinued software, primary options include: if patches exist, apply them; otherwise, migrate to a supported email server solution. Network filtering of external IMAP access can reduce exposure in the interim.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-0637 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2006-0637 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data