CVE-2006-5177 json
The NTLM authentication in MailEnable Professional 2.0 and Enterprise 2.0 allows remote attackers to (1) execute arbitrary code via unspeci…
published 2006-10-06 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-5162
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.3%
- EPSS 7.3% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
The NTLM authentication in MailEnable Professional 2.0 and Enterprise 2.0 allows remote attackers to (1) execute arbitrary code via unspecified vectors involving crafted base64 encoded NTLM Type 3 messages, or (2) cause a denial of service via crafted base64 encoded NTLM Type 1 messages, which trigger a buffer over-read.
Patch / fix
- mailenable.com/hotfix/ patch
- secunia.com/advisories/22179 advisory
- labs.musecurity.com/advisories/MU-200609-01.txt advisory
Timeline
- Published
- First public exploit (EDB-28735)
Exploit prediction
7.26% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-28735 MailEnable 2.x - SMTP NTLM Multiple Authentication Vulnerabilities dos, 2006-11-29
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
secunia.com
/advisories/22179
third-party-advisory, patch, vendor-advisory
-
mailenable.com
/hotfix/
patch
-
labs.musecurity.com
/advisories/MU-200609-01.txt
patch, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/29287
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/29286
vdb-entry
-
securityfocus.com
/bid/20290
vdb-entry
-
vupen.com
/english/advisories/2006/3862
vdb-entry
Sources
- CVE List CVE-2006-5177
- NVD CVE-2006-5177
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.