Mailenable Enterprise 2.0 NTLM Authentication memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.1$0-$5k0.00

Summaryinfo

A vulnerability has been found in Mailenable Enterprise 2.0 and classified as critical. Affected by this vulnerability is an unknown functionality of the component NTLM Authentication. Performing a manipulation results in memory corruption. This vulnerability is reported as CVE-2006-5177. Moreover, an exploit is present.

Detailsinfo

A vulnerability, which was classified as very critical, was found in Mailenable Enterprise 2.0 (Mail Server Software). This affects an unknown part of the component NTLM Authentication. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was disclosed 10/10/2006 by Mu Security with Mu Security research team (Website). The advisory is shared at xforce.iss.net. This vulnerability is uniquely identified as CVE-2006-5177 since 10/05/2006. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/23/2026).

A public exploit has been developed in Perl. The exploit is shared for download at securityfocus.com. It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 22483 (MailEnable SMTP Connector Multiple NTLM Authentication Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SMTP problems and running in the context r.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. Furthermore it is possible to detect and prevent this kind of attack with TippingPoint and the filter 9048.

The vulnerability is also documented in the databases at X-Force (29287), Tenable (22483), SecurityFocus (BID 20290†), OSVDB (29434†) and Secunia (SA22179†). The entries VDB-2707, VDB-2728, VDB-2727 and VDB-2767 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 10.0
VulDB Meta Temp Score: 9.1

VulDB Base Score: 10.0
VulDB Temp Score: 9.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Programming Language: 🔍
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 22483
Nessus Name: MailEnable SMTP Connector Multiple NTLM Authentication Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍
TippingPoint: 🔍

McAfee IPS: 🔍
McAfee IPS Version: 🔍

ISS Proventia IPS: 🔍
PaloAlto IPS: 🔍

Timelineinfo

09/29/2006 🔍
10/02/2006 +3 days 🔍
10/02/2006 +0 days 🔍
10/05/2006 +3 days 🔍
10/09/2006 +4 days 🔍
10/10/2006 +1 days 🔍
10/10/2006 +0 days 🔍
03/12/2015 +3075 days 🔍
04/23/2026 +4060 days 🔍

Sourcesinfo

Advisory: xforce.iss.net
Researcher: Mu Security
Organization: Mu Security research team
Status: Not defined
Confirmation: 🔍

CVE: CVE-2006-5177 (🔍)
GCVE (CVE): GCVE-0-2006-5177
GCVE (VulDB): GCVE-100-32637
X-Force: 29287
SecurityFocus: 20290 - MailEnable SMTP NTLM Authentication Multiple Vulnerabilities
Secunia: 22179
OSVDB: 29434 - MailEnable SMTP Connector NTLM Authentication base64 Type 1 Message DoS
Vulnerability Center: 12854 - MailEnable base64 encoded type3 message DoS and Code Execution Vulnerability, Medium
Vupen: ADV-2006-3862

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 03/12/2015 15:51
Updated: 04/23/2026 18:28
Changes: 03/12/2015 15:51 (74), 07/09/2019 06:59 (7), 04/23/2026 18:28 (20)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!