dbcve.org
Mailenable EnterpriseApplication · Mailenable

CVE-2006-6423

HIGH · 10.0 CVSS v2.0 Published 2006-12-12
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges Zero-click Patch available

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 · unedited
Stack-based buffer overflow in the IMAP service for MailEnable Professional and Enterprise Edition 2.0 through 2.35, Professional Edition 1.6 through 1.84, and Enterprise Edition 1.1 through 1.41 allows remote attackers to execute arbitrary code via a pre-authentication command followed by a crafted parameter and a long string, as addressed by the ME-10025 hotfix.

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

A detailed technical summary for this CVE is being prepared.

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
Mailenable EnterpriseApplication
Affected:= 1.1= 1.2= 1.11= 1.12= 1.13= 1.14= 1.15= 1.16= 1.17= 1.18= 1.19= 1.21
Mailenable ProfessionalApplication
Affected:= 1.84

CVSS 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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch secunia.com →
Recommended fix Moderate confidence

MailEnable Enterprise Edition 2.36 or later; MailEnable Professional Edition 1.85 or later (or latest available version)

  1. 1. Identify the exact MailEnable version currently installed by checking the product or checking the About section in MailEnable Administrator.
  2. 2. Download the ME-10025 hotfix from MailEnable's support site or contact MailEnable support to obtain the hotfix if upgrading to a newer version is not immediately feasible.
  3. 3. If upgrading, navigate to MailEnable's official download page and obtain version 2.36 or later for Enterprise Edition 2.x, or the latest version for Professional Edition 1.x (beyond 1.84).
  4. 4. Before applying any upgrade or hotfix, backup the MailEnable configuration and data directories.
  5. 5. Stop the MailEnable IMAP service before applying the patch or upgrade.
  6. 6. Apply the ME-10025 hotfix or install the upgraded version following MailEnable's installation instructions.
  7. 7. Restart the MailEnable IMAP service and verify IMAP functionality.
  8. 8. Monitor logs for any errors and confirm the server is responding to IMAP connections.
Caveat Review release notes for any configuration or compatibility changes between versions; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-6423 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-6423 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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