Microsoft Outlook Express 5.5/6.0 Windows Address Book File Parser memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in Microsoft Outlook Express 5.5/6.0. This affects an unknown part of the component Windows Address Book File Parser. The manipulation results in memory corruption. This vulnerability is identified as CVE-2006-0014. There is not any exploit available. Applying a patch is advised to resolve this issue.
Details
A vulnerability, which was classified as critical, was found in Microsoft Outlook Express 5.5/6.0 (Mail Client Software). Affected is an unknown functionality of the component Windows Address Book File Parser. 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. CVE summarizes:
Buffer overflow in Microsoft Outlook Express 5.5 and 6 allows remote attackers to execute arbitrary code via a crafted Windows Address Book (WAB) file containing "certain Unicode strings" and modified length values.
The bug was discovered 04/11/2006. The weakness was released 04/11/2006 by Stuart Pearson and ATmaCA as MS06-016 as confirmed bulletin (Technet). The advisory is shared for download at microsoft.com. This vulnerability is traded as CVE-2006-0014 since 11/09/2005. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available.
It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 21213 (MS06-016: Vulnerability in Outlook Express Could Allow Remote Code Execution (911567)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows : Microsoft Bulletins and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 90307 (Microsoft Outlook Express Cumulative Security Update Missing (MS06-016)).
Applying the patch MS06-016 is able to eliminate this problem. The bugfix is ready for download at windowsupdate.microsoft.com. A possible mitigation has been published immediately after the disclosure of the vulnerability. Attack attempts may be identified with Snort ID 6413. In this case the pattern Content-Transfer-Encoding is used for detection. Furthermore it is possible to detect and prevent this kind of attack with TippingPoint and the filter 3794.
The vulnerability is also documented in the databases at X-Force (25535), Tenable (21213), SecurityFocus (BID 17459†), OSVDB (30821†) and Secunia (SA19617†). Entry connected to this vulnerability is available at VDB-2740. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
License
Support
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 21213
Nessus Name: MS06-016: Vulnerability in Outlook Express Could Allow Remote Code Execution (911567)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: MS06-016
Snort ID: 6413
Snort Message: SMTP Base64 encoded Windows Address Book attachment detected
Snort Pattern: 🔍
TippingPoint: 🔍
McAfee IPS: 🔍
McAfee IPS Version: 🔍
SourceFire IPS: 🔍
ISS Proventia IPS: 🔍
PaloAlto IPS: 🔍
Fortigate IPS: 🔍
Timeline
11/09/2005 🔍04/11/2006 🔍
04/11/2006 🔍
04/11/2006 🔍
04/11/2006 🔍
04/11/2006 🔍
04/11/2006 🔍
04/11/2006 🔍
04/11/2006 🔍
04/11/2006 🔍
04/12/2006 🔍
04/12/2006 🔍
12/12/2006 🔍
06/25/2025 🔍
Sources
Vendor: microsoft.comAdvisory: MS06-016
Researcher: Stuart Pearson, ATmaCA
Status: Confirmed
CVE: CVE-2006-0014 (🔍)
GCVE (CVE): GCVE-0-2006-0014
GCVE (VulDB): GCVE-100-2136
OVAL: 🔍
X-Force: 25535 - Microsoft Outlook Express Windows Address Book file buffer overflow, High Risk
SecurityFocus: 17459 - Microsoft Outlook Express Windows Address Book File Parsing Buffer Overflow Vulnerability
Secunia: 19617 - Outlook Express Windows Address Book File Vulnerability, Moderately Critical
OSVDB: 30821 - Microsoft Outlook Express Windows Address Book Contact Record Code Execution
SecurityTracker: 1015898
Vulnerability Center: 11061 - [MS06-016] Microsoft Outlook Express Windows Address Book File Vulnerability, Critical
Vupen: ADV-2006-1321
See also: 🔍
Entry
Created: 04/12/2006 16:24Updated: 06/25/2025 04:44
Changes: 04/12/2006 16:24 (105), 06/16/2019 14:33 (2), 06/25/2025 04:44 (18)
Complete: 🔍
Cache ID: 216:84A:103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.