Computer Security
[EN] securityvulns.ru no-pyccku


Related information

  Microsoft Internet Explorer / Outlook Express multiple security vulnerabilities

  [Full-disclosure] ZDI-06-048: Microsoft Internet Explorer normalize() Function Memory Corruption Vulnerability

  [Full-disclosure] Secunia Research: Internet Explorer Script Error Handling Memory Corruption

  Microsoft Security Bulletin MS06-072

From:MICROSOFT <secure_(at)_microsoft.com>
Date:12.12.2006
Subject:Microsoft Security Bulletin MS06-076 Cumulative Security Update for Outlook Express (923694)

Microsoft Security Bulletin MS06-076
Cumulative Security Update for Outlook Express (923694)
Published: December 12, 2006

Version: 1.0
Summary

Who Should Read this Document: Customers who use Microsoft Outlook Express

Impact of Vulnerability: Remote Code Execution

Maximum Severity Rating: Important

Recommendation: Customers should apply the update at the earliest opportunity

Security Update Replacement: This bulletin replaces several prior security updates. See the frequently asked questions (FAQ) section of this bulletin for the complete list.

Caveats: Microsoft Knowledge Base Article 923694 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues. For more information, see Microsoft Knowledge Base Article 923694.

Tested Software and Security Update Download Locations:

Affected Software:


Microsoft Windows 2000 Service Pack 4


Microsoft Windows XP Service Pack 2


Microsoft Windows XP Professional x64 Edition


Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1


Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems


Microsoft Windows Server 2003 x64 Edition

Non-Affected Software:

Windows Vista

Tested Microsoft Windows Components:

Affected Components:


Outlook Express 5.5 Service Pack 2 on Microsoft Windows 2000 Service Pack 4 - Download the Update


Outlook Express 6 Service Pack 1 when installed on Microsoft Windows 2000 Service Pack 4 - Download the update


Outlook Express 6 on Microsoft Windows XP Service Pack 2 - Download the update


Outlook Express 6 on Microsoft Windows XP Professional x64 Edition - Download the update


Outlook Express 6 on Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 - Download the update


Outlook Express 6 on Microsoft Windows Server 2003 x64 Edition - Download the update


Outlook Express 6 on Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems - Download the update

The software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

Note The security updates for Microsoft Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 x64 Edition also apply to Windows Server 2003 R2.
Top of sectionTop of section
General Information

Executive Summary

Executive Summary:

This update resolves a newly discovered, privately reported vulnerability. The vulnerability is documented in the "Vulnerability Details" section of this bulletin.

We recommend that customers should apply the update at the earliest opportunity.

Severity Ratings and Vulnerability Identifiers:
Vulnerability Identifiers Impact of Vulnerability Outlook Express 5.5 Service Pack 2 on Microsoft Windows 2000 Service Pack 4 Outlook Express 6 Service Pack 1 when installed on Microsoft Windows 2000 Service Pack 4 Outlook Express 6 on Microsoft Windows XP Service Pack 2 (including the 64-Bit Edition) Outlook Express 6 on Microsoft Windows Server 2003 or on Microsoft Windows Server 2003 Service Pack 1 (including the 64-Bit Edition)

Windows Address Book Contact Record Vulnerability - CVE-2006-2386


Remote Code Execution


Important


Important


Important


Important

This assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.

Note The security updates for Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 x64 Edition also apply to Windows Server 2003 R2.

Note The severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows:


The Windows XP Professional x64 Edition severity rating is the same as the Windows XP Service Pack 2 severity rating.


The Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.


The Windows Server 2003 with SP1 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.


The Windows Server 2003 x64 Edition severity rating is the same as the Windows Server 2003 severity rating.
Top of sectionTop of section

Frequently Asked Questions (FAQ) Related to This Security Update

What are the known issues that customers may experience when they install this security update?
Microsoft Knowledge Base Article 923694 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues. For more information, see Microsoft Knowledge Base Article 923694.


Microsoft Knowledge Base Article 923694 : Error message when you open the Windows Address Book or you open Outlook Express after you install cumulative security update.

What updates does this release replace?
This security update replaces a prior security update. The security bulletin IDs and affected operating systems are listed in the following table.
Bulletin ID Outlook Express 5.5 Service Pack 2 on Windows 2000 Service Pack 4 Outlook Express 6 Service Pack 1 on Windows 2000 Service Pack 4 Outlook Express 6 on Windows XP Service Pack 2 (including the 64-Bit Edition) Outlook Express 6 for Windows Server 2003 and Microsoft Windows Server 2003 for Itanium-based Systems Outlook Express 6 on Windows Server 2003 Service Pack 1, Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 x64 Edition

MS06-016


Replaced


Replaced


Replaced


Replaced


Replaced

MS06-043


Not Applicable


Not Applicable


Replaced


Not Applicable


Replaced

Extended security update support for Windows 98, Windows 98 Second Edition, or Windows Millennium Edition ended on July 11, 2006. I am still using one of these operating systems, what should I do?
Windows 98, Windows 98 Second Edition, or Windows Millennium Edition has reached the end of their life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Support Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.

Extended security update support for Microsoft Windows XP Home Edition Service Pack 1 or Service Pack 1a, Windows XP Media Center Edition 2002 Service Pack 1, Windows XP Media Center Edition 2004 Service Pack 1, Windows XP Professional Service Pack 1 or Service Pack 1a, and Windows XP Tablet PC Edition Service Pack 1 ended on October 10, 2006. I am still using one of these operating systems; what should I do?
Windows XP (all versions) Service Pack 1has reached the end of its support life cycle. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.

Extended security update support for Microsoft Windows NT Workstation 4.0 Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. Extended security update support for Microsoft Windows NT Server 4.0 Service Pack 6a ended on December 31, 2004. Extended security update support for Microsoft Windows 2000 Service Pack 3 ended on June 30, 2005. I am still using one of these operating systems, what should I do?
Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, Windows 2000 Service Pack 2, and Windows 2000 Service Pack 3 have reached the end of their life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Support Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.

Customers who require custom support for these products must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.

Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?
The following table provides the MBSA detection summary for this security update.
Product MBSA 1.2.1 Enterprise Update Scan Tool (EST) MBSA 2.0

Outlook Express 5.5 Service Pack 2 on Microsoft Windows 2000 Service Pack 4


No


Yes


Yes

Outlook Express 6 Service Pack 1 on Microsoft Windows 2000 Service Pack 4


No


Yes


Yes

Outlook Express 6 on Microsoft Windows XP Service Pack 2


No


Yes


Yes

Outlook Express 6 on Microsoft Windows XP Professional x64 Edition


No


No


Yes

Outlook Express 6 on Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1


No


Yes


Yes

Outlook Express 6 on Microsoft Windows Server 2003 x64 Edition


No


No


Yes

Outlook Express 6 on Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems


No


No


Yes

For more information about MBSA, visit the MBSA Web site. For more information about the programs that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.

What is the Enterprise Update Scan Tool (EST)?
As part of an ongoing commitment to provide detection tools for bulletin-class security updates, Microsoft delivers a stand-alone detection tool whenever the Microsoft Baseline Security Analyzer (MBSA) and the Office Detection Tool (ODT) cannot detect whether the update is required for an MSRC release cycle. This stand-alone tool is called the Enterprise Update Scan Tool (EST) and is designed for enterprise administrators. When a version of the Enterprise Update Scan Tool is created for a specific bulletin, customers can run the tool from a command line interface (CLI) and view the results of the XML output file. To help customers better utilize the tool, detailed documentation will be provided with the tool. There is also a version of the tool that offers an integrated experience for SMS administrators.

Can I use a version of the Enterprise Update Scan Tool (EST) to determine whether this update is required?
Yes. Microsoft has created a version of the EST that will determine if you have to apply this update. For download links and more information about the version of the EST that is being released this month, see the following Microsoft Web site. SMS customers should review the "Can I use Systems Management Server (SMS) to determine whether this update is required?" FAQ for more information about SMS and EST.

Can I use Systems Management Server (SMS) to determine whether this update is required?
The following table provides the SMS detection summary for this security update.
Product SMS 2.0 SMS 2003

Outlook Express 5.5 Service Pack 2 on Microsoft Windows 2000 Service Pack 4


Yes (with EST)


Yes

Outlook Express 6 Service Pack 1 on Microsoft Windows 2000 Service Pack 4


Yes (with EST)


Yes

Outlook Express 6 on Microsoft Windows XP Service Pack 2


Yes (with EST)


Yes

Outlook Express 6 on Microsoft Windows XP Professional x64 Edition


Yes (with EST)


Yes

Outlook Express 6 on Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1


Yes (with EST)


Yes

Outlook Express 6 on Microsoft Windows Server 2003 x64 Edition


Yes (with EST)


Yes

Outlook Express 6 on Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems


Yes (with EST)


Yes

SMS 2.0 and SMS 2003 Software Update Services (SUS) Feature Pack can use MBSA 1.2.1 for detection and therefore have the same limitation that is listed earlier in this bulletin related to programs that MBSA 1.2.1 does not detect.

For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool, can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about the Security Update Inventory Tool, visit the following Microsoft Web site. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 Inventory Tool for Microsoft Updates, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

For more information about SMS, visit the SMS Web site.
Top of sectionTop of section

Vulnerability Details

Windows Address Book Contact Record Vulnerability - CVE-2006-2386

A remote code execution vulnerability in a component of Outlook Express could allow an attacker who sent a Windows Address Book file to a user of an affected system to take complete control of the system.

If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.

Mitigating Factors for Windows Address Book Contact Record Vulnerability - CVE-2006-2386:


An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.


In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to attempt to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. In order for the exploit to take place, the user would have to open the .wab file.


In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially-crafted .wab file to the user and by persuading the user to open the file.
Top of sectionTop of section

Workarounds for Windows Address Book Contact Record Vulnerability - CVE-2006-2386:

Microsoft has tested the following workarounds. Although these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section:


Back up and remove the .wab file association
Removing the WAB registry key helps protect the affected system from attempts to exploit this vulnerability. To backup and remove the WAB registry key, follow these steps:

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

We recommend backing up the registry before you edit it.

1.


Click Start, click Run, type “regedit" (without the quotation marks), and then click OK.

2.


Expand HKEY_CLASSES_ROOT, and then click .WAB.

3.


Click File, and then click Export.

4.


In the Export Registry File dialog box, type a file name in the File Name box, and then click Save.

5.


Click Edit, and then click Delete to remove the registry key.

6.


In the Confirm Key Delete dialog box, you receive an “Are you sure you want to delete this key and all of its subkeys” message. Click Yes.

Impact of Workaround: Users will not be able to open address books by double clicking them. They will have to manually start the Windows Address Book application and pass the address book to be used as a command line parameter or they can import the address book from the File menu. This does not affect the use of address books in Outlook Express.
Top of sectionTop of section

FAQ for Windows Address Book Contact Record Vulnerability - CVE-2006-2386:

What is the scope of the vulnerability?
A remote code execution vulnerability in a component of Outlook Express could allow an attacker who sent a Windows Address Book file to a user of an affected system to take complete control of the system.

If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.

What causes the vulnerability?
An unchecked buffer in the Windows Address Book (WAB) functions within Outlook Express.

What is a Windows Address Book?
Windows provides an address book for storing contact information. The WAB is an application and service that enables users to keep track of people. The WAB has a local database and user interface for finding and editing information about people.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.

How could an attacker exploit the vulnerability?
In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to attempt to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. In order for the exploit to take place, the user would have to open the .wab file.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially-crafted .wab file to the user and by persuading the user to open the file.

A specially crafted .wab file opened from the local file system or from a network share could also allow lead to memory corruption that could potentially allow code execution.

What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who have sufficient administrative permissions are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do?
The update removes the vulnerability by modifying the way that Outlook Express, when using a .wab file, validates the length of a field before it passes it to the allocated buffer.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

Disclaimer:

The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

Revisions:


V1.0 (December 12, 2006): Bulletin published.

About | Terms of use | Privacy Policy
© SecurityVulns, 3APA3A, Vladimir Dubrovin
Nizhny Novgorod