MailenableApplication

CVE-2007-0955

HIGH · 7.8 CVSS v2.0 Published 2007-02-15
Fix available
A fix is available. Upgrade to after 2.35 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
The NTLM_UnPack_Type3 function in MENTLM.dll in MailEnable Professional 2.35 and earlier allows remote attackers to cause a denial of service (application crash) via certain base64-encoded data following an AUTHENTICATE NTLM command to the imap port (143/tcp), which results in an out-of-bounds read.

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 · high confidence

A remote denial of service vulnerability exists in MailEnable Professional 2.35 and earlier. The NTLM_UnPack_Type3 function in MENTLM.dll performs an out-of-bounds read when processing specially crafted base64-encoded data sent after an AUTHENTICATE NTLM command on the IMAP service (port 143/tcp), causing the application to crash.

MitigationUpdate MailEnable Professional to a version newer than 2.35 that includes the patched MENTLM.dll, or apply any available vendor hotfix for CVE-2007-0955. If immediate patching is not feasible, consider restricting or filtering NTLM authentication attempts on IMAP port 143 at the network perimeter.

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
MailenableApplication
Affected:<= 2.35

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

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify MailEnable installation and version
    Check the MailEnable installation directory for version information. Common paths: C:\Program Files\MailEnable\ or inspect Add/Remove Programs in Windows Control Panel for MailEnable Professional version.
    Affected if Installed version is MailEnable Professional 2.35 or earlier (any version <= 2.35).
  2. Verify IMAP service is running
    Check if the MailEnable IMAP service is active. Use command 'netstat -an | findstr :143' or check Services.msc for 'MailEnable IMAP Service'.
    Affected if IMAP service is listening on port 143/tcp, making the vulnerability reachable over the network.
  3. Confirm NTLM authentication is enabled for IMAP
    Inspect MailEnable configuration. In MailEnable Administrator, go to IMAP server properties > Security/Authentication. Alternatively, check the MENTLM.dll file version in the MailEnable bin directory.
    Affected if NTLM authentication is enabled for the IMAP service, which is required to trigger the vulnerable code path.
  4. Check MENTLM.dll file version
    Locate MENTLM.dll in the MailEnable bin directory (typically C:\Program Files\MailEnable\bin\). Right-click the file, select Properties, and check the Version tab.
    Affected if The MENTLM.dll file version corresponds to an unpatched build (versions prior to the CVE-2007-0955 fix). Compare your version to the affected range <= 2.35.

A system is affected if MailEnable Professional version 2.35 or earlier is installed, the IMAP service is running on port 143, and NTLM authentication is enabled for IMAP, allowing remote attackers to trigger the out-of-bounds read in MENTLM.dll.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2.35
Interim mitigation

Update MailEnable Professional to a version newer than 2.35 that includes the patched MENTLM.dll, or apply any available vendor hotfix for CVE-2007-0955. If immediate patching is not feasible, consider restricting or filtering NTLM authentication attempts on IMAP port 143 at the network perimeter.

Fix this in Mailenable Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-0955 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-0955 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