Computer Security
[EN] securityvulns.ru no-pyccku


Related information

  Microsoft Outlook Express buffer overflow

  ZDI-06-007: Microsoft Windows Address Book (WAB) File Format Parsing Vulnerability

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

Microsoft Security Bulletin MS06-016
Cumulative Security Update for Outlook Express (911567)
Published: April 11, 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 two prior security updates. See the frequently asked questions (FAQ) section of this bulletin for the complete list.

Caveats: None

Tested Software and Security Update Download Locations:

Affected Software:


Microsoft Windows 2000 Service Pack 4


Microsoft Windows XP Service Pack 1 and 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


Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (Windows Me) – Review the FAQ section of this bulletin for details about these operating systems.

Tested Microsoft Windows Components:

Affected Components:


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 Microsoft Windows Server 2003 on Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems - 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 Service Pack 1 on Microsoft Windows XP Service Pack 1 or when installed on Microsoft Windows 2000 Service Pack 4 - Download the update


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

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

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.
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.

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.

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 impacted than users who operate with administrative user rights.

We recommend that customers 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 Windows 2000 Service Pack 4 Outlook Express 6 Service Pack 1 on Windows 2000 Service Pack 4 or on Windows XP Service Pack 1 Outlook Express 6 for Windows XP Service Pack 2 (Including the 64-bit Edition) Outlook Express 6 for Windows Server 2003 or on Windows 2003 Service Pack 1 (Including 64-Bit Edition)

Microsoft Outlook Express when using a Windows Address Book File Vulnerability - CVE-2006-0014


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 severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows:


The Microsoft Windows Server 2003 R2 Systems severity rating is the same as the Windows Server 2003 severity rating.


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


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


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


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

Frequently asked questions (FAQ) related to this security update

What updates does this release replace?
This security update replaces two prior security updates. 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 Outlook Express 6 Service Pack 1 on Windows 2000 Service Pack 4 or on Windows XP Service Pack 1 Outlook Express 6 for Windows XP Service Pack 2 Outlook Express 6 for Windows Server 2003 Outlook Express 6 for Windows Server 2003 Service Pack 1 (including 64-Bit Edition)

MS04-018


Replaced


Replaced


Not Applicable


Replaced


Not Applicable

MS05-030


Replaced


Replaced


Not Applicable


Replaced


Not Applicable

How does the extended support for Windows 98, Windows 98 Second Edition, and Windows Millennium Edition affect the release of security updates for these operating systems?
Microsoft will only release security updates for critical security issues. Non-critical security issues are not offered during this support period. For more information about the Microsoft Support Lifecycle policies for these operating systems, visit the following Web site.

For more information about severity ratings, visit the following Web site.

Are Windows 98, Windows 98 Second Edition, or Windows Millennium Edition critically affected by one or more of the vulnerabilities that are addressed in this security bulletin?
No. Although Windows Millennium Edition does contain the affected component, the vulnerability is not critical. For more information about severity ratings, visit the following 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 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) 1.2.1 to determine whether this update is required?
MBSA 1.2.1 will not determine whether this update is required. MBSA 1.2.1 will only determine if an update is required for products that MBSA 1.2.1 supports. MBSA 1.2.1 does not support the detection of Outlook Express. For more information about MBSA, visit the MBSA Web site. For more information about the programs that MBSA 1.2.1 currently does not detect, see Microsoft Knowledge Base Article 306460. However, Microsoft has developed a version of the Enterprise Scan Tool (EST) that will help customers determine if the security updates provided in this security bulletin are required. See the "Can I use a version of the Enterprise Scan Tool (EST) to determine whether this update is required?" FAQ for more information about this tool.

Can I use the Microsoft Baseline Security Analyzer (MBSA) 2.0 to determine whether this update is required?
Yes. MBSA 2.0 will determine whether this update is required. MBSA 2.0 can detect security updates for products that Microsoft Update supports. For more information about MBSA, visit the MBSA Web site.

What is the Enterprise 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 Scan Tool (EST) and is designed for enterprise administrators. When a version of the Enterprise 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 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?
Yes. SMS can help detect and deploy this security update.

Can I use Systems Management Server (SMS) to determine whether this update is required?
Yes. SMS can help detect and deploy this security update.

SMS can use the SMS SUS Feature pack, which includes the Security Update Inventory Tool (SUIT) to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. Therefore, SMS SUIT has the same limitation listed earlier in this bulletin related to programs that MBSA does not detect.

For more information about the Security Update Inventory Tool, see 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 that detects the required updates for Microsoft Office applications.

SMS can use the SMS 2003 Inventory Tool for Microsoft Updates 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.

However, SMS 2.0 customers and SMS 2003 customers who are not using the Inventory Tool for Microsoft Updates must download and deploy an updated version of the Extended Security Update Inventory Tool to receive full detection and deployment for this update.

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

Vulnerability Details

Microsoft Outlook Express when using a Windows Address Book File Vulnerability - CVE-2006-0014

A remote code execution vulnerability exists in Outlook Express when using a Windows Address Book (.wab) file that could allow an attacker who successfully exploited this vulnerability to take complete control of the affected 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 Microsoft Outlook Express when using a Windows Address Book File Vulnerability - CVE-2006-0014:


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 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.


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.
Top of sectionTop of section

Workarounds for Microsoft Outlook Express when using a Windows Address Book File Vulnerability - CVE-2006-0014:

Microsoft has tested the following workarounds. While 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:

Note Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

Note 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 Microsoft Outlook Express when using Windows Address Book File Vulnerability - CVE-2006-0014:

What is the scope of the vulnerability?
A remote code execution vulnerability exists in Outlook Express when using a Windows Address Book (.wab) file that could allow an attacker who successfully exploited this vulnerability to take complete control of the affected 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, and it can query network directory servers using Lightweight Directory Access Protocol (LDAP).

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 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. In order for the exploit to take place, the user would have to save the .wab file to the desktop and open it using Outlook Express.

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 save the .wab file to the desktop and open it using Outlook Express.

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 do not have sufficient administrative permissions are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this.

Are Windows 98, Windows 98 Second Edition or Windows Millennium Edition critically affected by this vulnerability?
No. Although Windows 98, Windows 98 Second Edition or Windows Millennium Edition does contain the affected component, the vulnerability is not critical. For more information about severity ratings, visit the following Web site.

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.
Top of sectionTop of section
Top of sectionTop of section
Top of sectionTop of section

Security Update Information

Affected Software:

For information about the specific security update for your affected software, click the appropriate link:

Outlook Express 6 for Windows 2003 (all versions)

Prerequisites
This security update requires Windows Server 2003 or Windows Server 2003 Service Pack 1.

Inclusion in Future Service Packs
The update for this issue will be included in a future service pack or update rollup.

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

Installation Information

This security update supports the following setup switches.
Supported Security Update Installation Switches
Switch Description

/help


Displays the command-line options
Setup Modes

/passive


Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.

/quiet


Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options

/norestart


Does not restart when installation has completed

/forcerestart


Restarts the computer after installation and forces other applications to close at shutdown without saving open files first.

/warnrestart[:x]


Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.

/promptrestart


Displays a dialog box prompting the local user to allow a restart
Special Options

/overwriteoem


Overwrites OEM files without prompting

/nobackup


Does not back up files needed for uninstall

/forceappsclose


Forces other programs to close when the computer shuts down

/log: path


Allows the redirection of installation log files

/integrate:path


Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.

/extract[:path]


Extracts files without starting the Setup program

/ER


Enables extended error reporting

/verbose


Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for Windows Server 2003:

Windowsserver2003-kb911567-x86-enu /quiet

Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB911567.log file for any failure messages when they use this switch.

To install the security update without forcing the system to restart, use the following command at a command prompt for Windows Server 2003:

Windowsserver2003-kb911567-x86-enu /norestart

For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.

Restart Requirement

This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.

Removal Information

To remove this update, use the Add or Remove Programs tool in Control Panel.

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB911567$\Spuninst folder.
Supported Spuninst.exe Switches
Switch Description

/help


Displays the command-line options
Setup Modes

/passive


Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.

/quiet


Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options

/norestart


Does not restart when installation has completed

/forcerestart


Restarts the computer after installation and forces other applications to close at shutdown without saving open files first.

/warnrestart[:x]


Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.

/promptrestart


Displays a dialog box prompting the local user to allow a restart
Special Options

/forceappsclose


Forces other programs to close when the computer shuts down

/log:path


Allows the redirection of installation log files

File Information

The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Datacenter Edition; Windows Server 2003, Enterprise Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; Windows Server 2003, Datacenter Edition with SP1; Windows Server 2003 R2, Web Edition; Windows Server 2003 R2, Standard Edition; Windows Server 2003 R2, Datacenter Edition; Windows Server 2003 R2, Enterprise Edition; Windows Small Business Server 2003 R2:
File Name Version Date Time Size Folder

Inetcomm.dll


6.0.3790.2663


18-Mar-2006


03:38


681,472


RTMGDR

Msoe.dll


6.0.3790.2663


18-Mar-2006


03:38


1,315,328


RTMGDR

Wab32.dll


6.0.3790.2663


18-Mar-2006


03:38


510,976


RTMGDR

Wabimp.dll


6.0.3790.2663


18-Mar-2006


03:38


85,504


RTMGDR

Inetcomm.dll


6.0.3790.2663


18-Mar-2006


03:31


681,472


RTMQFE

Msoe.dll


6.0.3790.2663


18-Mar-2006


03:31


1,315,328


RTMQFE

Wab32.dll


6.0.3790.2663


18-Mar-2006


03:31


510,976


RTMQFE

Wabimp.dll


6.0.3790.2663


18-Mar-2006


03:31


85,504


RTMQFE

Inetcomm.dll


6.0.3790.2663


18-Mar-2006


03:38


681,472


SP1GDR

Msoe.dll


6.0.3790.2663


18-Mar-2006


03:38


1,315,328


SP1GDR

Wab32.dll


6.0.3790.2663


18-Mar-2006


03:38


510,976


SP1GDR

Wabimp.dll


6.0.3790.2663


18-Mar-2006


03:38


85,504


SP1GDR

Inetcomm.dll


6.0.3790.2663


18-Mar-2006


03:44


681,472


SP1QFE

Msoe.dll


6.0.3790.2663


18-Mar-2006


04:04


1,315,328


SP1QFE

Wab32.dll


6.0.3790.2663


18-Mar-2006


03:44


510,976


SP1QFE

Wabimp.dll


6.0.3790.2663


18-Mar-2006


03:44


85,504


SP1QFE

Windows Server, 2003 Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; and Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems:
File Name Version Date Time Size CPU Folder

Inetcomm.dll


6.0.3790.504


18-Mar-2006


04:09


2,031,104


IA-64


RTMGDR

Msoe.dll


6.0.3790.504


18-Mar-2006


04:09


4,087,296


IA-64


RTMGDR

Wab32.dll


6.0.3790.504


18-Mar-2006


04:09


1,569,792


IA-64


RTMGDR

Wabimp.dll


6.0.3790.504


18-Mar-2006


04:09


220,160


IA-64


RTMGDR

Winetcomm.dll


6.0.3790.504


18-Mar-2006


04:09


608,256


x86


RTMGDR\WOW

Wmsoe.dll


6.0.3790.504


18-Mar-2006


04:09


1,202,688


x86


RTMGDR\WOW

Wwab32.dll


6.0.3790.504


18-Mar-2006


04:09


479,744


x86


RTMGDR\WOW

Wwabimp.dll


6.0.3790.504


18-Mar-2006


04:09


81,920


x86


RTMGDR\WOW

Inetcomm.dll


6.0.3790.504


18-Mar-2006


04:09


2,031,104


IA-64


RTMQFE

Msoe.dll


6.0.3790.504


18-Mar-2006


04:09


4,087,296


IA-64


RTMQFE

Wab32.dll


6.0.3790.504


18-Mar-2006


04:09


1,569,792


IA-64


RTMQFE

Wabimp.dll


6.0.3790.504


18-Mar-2006


04:09


220,160


IA-64


RTMQFE

Winetcomm.dll


6.0.3790.504


18-Mar-2006


04:09


608,256


x86


RTMQFE\WOW

Wmsoe.dll


6.0.3790.504


18-Mar-2006


04:09


1,202,688


x86


RTMQFE\WOW

Wwab32.dll


6.0.3790.504


18-Mar-2006


04:09


479,744


x86


RTMQFE\WOW

Wwabimp.dll


6.0.3790.504


18-Mar-2006


04:09


81,920


x86


RTMQFE\WOW

Inetcomm.dll


6.0.3790.2663


18-Mar-2006


04:12


2,031,104


IA-64


SP1GDR

Msoe.dll


6.0.3790.2663


18-Mar-2006


04:12


4,087,296


IA-64


SP1GDR

Wab32.dll


6.0.3790.2663


18-Mar-2006


04:12


1,569,792


IA-64


SP1GDR

Wabimp.dll


6.0.3790.2663


18-Mar-2006


04:12


220,160


IA-64


SP1GDR

Winetcomm.dll


6.0.3790.504


18-Mar-2006


04:12


681,472


x86


SP1GDR\WOW

Wmsoe.dll


6.0.3790.504


18-Mar-2006


04:12


1,315,328


x86


SP1GDR\WOW

Wwab32.dll


6.0.3790.504


18-Mar-2006


04:12


510,976


x86


SP1GDR\WOW

Wwabimp.dll


6.0.3790.504


18-Mar-2006


04:12


85,504


x86


SP1GDR\WOW

Inetcomm.dll


6.0.3790.2663


18-Mar-2006


04:09


2,374,144


IA-64


SP1QFE

Msoe.dll


6.0.3790.2663


18-Mar-2006


04:09


4,605,952


IA-64


SP1QFE

Wab32.dll


6.0.3790.2663


18-Mar-2006


04:09


1,710,592


IA-64


SP1QFE

Wabimp.dll


6.0.3790.2663


18-Mar-2006


04:09


242,688


IA-64


SP1QFE

Winetcomm.dll


6.0.3790.504


18-Mar-2006


04:09


681,472


x86


SP1QFE\WOW

Wmsoe.dll


6.0.3790.504


18-Mar-2006


04:09


1,315,328


x86


SP1QFE\WOW

Wwab32.dll


6.0.3790.504


18-Mar-2006


04:09


510,976


x86


SP1QFE\WOW

Wwabimp.dll


6.0.3790.504


18-Mar-2006


04:09


85,504


x86


SP1QFE\WOW

Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition; Windows Server 2003 R2, Standard x64 Edition; Windows Server 2003 R2, Enterprise x64 Edition; and Windows Server 2003 R2, Datacenter x64 Edition:
File Name Version Date Time Size CPU Folder

Inetcomm.dll


6.0.3790.2663


18-Mar-2006


04:11


1,159,168


x64


SP1GDR

Msoe.dll


6.0.3790.2663


18-Mar-2006


04:11


2,146,816


x64


SP1GDR

Wab32.dll


6.0.3790.2663


18-Mar-2006


04:11


831,488


x64


SP1GDR

Wabimp.dll


6.0.3790.2663


18-Mar-2006


04:11


128,000


x64


SP1GDR

Winetcomm.dll


6.0.3790.2663


18-Mar-2006


04:11


681,472


x86


SP1GDR\WOW

Wmsoe.dll


6.0.3790.2663


18-Mar-2006


04:11


1,315,328


x86


SP1GDR\WOW

Wwab32.dll


6.0.3790.2663


18-Mar-2006


04:11


510,976


x86


SP1GDR\WOW

Wwabimp.dll


6.0.3790.2663


18-Mar-2006


04:11


85,504


x86


SP1GDR\WOW

Inetcomm.dll


6.0.3790.2663


18-Mar-2006


04:11


1,159,168


x64


SP1QFE

Msoe.dll


6.0.3790.2663


18-Mar-2006


04:11


2,146,816


x64


SP1QFE

Wab32.dll


6.0.3790.2663


18-Mar-2006


04:11


831,488


x64


SP1QFE

Wabimp.dll


6.0.3790.2663


18-Mar-2006


04:11


128,000


x64


SP1QFE

Winetcomm.dll


6.0.3790.2663


18-Mar-2006


04:11


681,472


x86


SP1QFE\WOW

Wmsoe.dll


6.0.3790.2663


18-Mar-2006


04:11


1,315,328


x86


SP1QFE\WOW

Wwab32.dll


6.0.3790.2663


18-Mar-2006


04:11


510,976


x86


SP1QFE\WOW

Wwabimp.dll


6.0.3790.2663


18-Mar-2006


04:11


85,504


x86


SP1QFE\WOW

Note When you install this security update on Windows Server 2003, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix. If you have previously installed a hotfix to update an affected file, the installer copies the RTMQFE files to your system. Otherwise, the installer copies the RTMGDR files to your system.

For more information about this behavior, see Microsoft Knowledge Base Article 824994.

For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

Arpidfix.exe is used by the security update installer to address an issue documented in Microsoft Knowledge Base Article 904630. This file is not installed onto the affected system.

Verifying that the Update Has Been Applied


Microsoft Baseline Security Analyzer

To verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.


File Version Verification

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

1.


Click Start, and then click Search.

2.


In the Search Results pane, click All files and folders under Search Companion.

3.


In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.

4.


In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.

5.


On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.


Registry Key Verification

You may also be able to verify the files that this security update has installed by reviewing the following registry key.

Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; Windows Server 2003, Datacenter Edition with SP1; Windows Server 2003, Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems; Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP2\KB911567\911567

Note This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly if an administrator or an OEM integrates or slipstreams the 911567 security update into the Windows installation source files.
Top of sectionTop of section

Outlook Express 6 on Windows XP Service Pack 2 and XP Professional x64 Edition

Prerequisites
This security update requires Microsoft Windows XP Service Pack 2. For more information, see Microsoft Knowledge Base Article 322389.

Inclusion in Future Service Packs
The update for this issue will be included in a future service pack or update rollup.

Installation Information

This security update supports the following setup switches.
Supported Security Update Installation Switches
Switch Description

/help


Displays the command-line options
Setup Modes

/passive


Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.

/quiet


Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options

/norestart


Does not restart when installation has completed

/forcerestart


Restarts the computer after installation and forces other applications to close at shutdown without saving open files first.

/warnrestart[:x]


Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.

/promptrestart


Displays a dialog box prompting the local user to allow a restart
Special Options

/overwriteoem


Overwrites OEM files without prompting

/nobackup


Does not back up files needed for uninstall

/forceappsclose


Forces other programs to close when the computer shuts down

/log:path


Allows the redirection of installation log files

/integrate:path


Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.

/extract[:path]


Extracts files without starting the Setup program

/ER


Enables extended error reporting

/verbose


Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for Microsoft Windows XP:

Windowsxp-kb911567-x86-enu /quiet

Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB911567.log file for any failure messages when they use this switch.

To install the security update without forcing the system to restart, use the following command at a command prompt for Windows XP:

Windowsxp-kb911567-x86-enu /norestart

For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.

Restart Requirement

This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.

To remove this security update, use the Add or Remove Programs tool in Control Panel.

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB911567$\Spuninst folder.
Supported Spuninst.exe Switches
Switch Description

/help


Displays the command-line options
Setup Modes

/passive


Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.

/quiet


Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options

/norestart


Does not restart when installation has completed

/forcerestart


Restarts the computer after installation and forces other applications to close at shutdown without saving open files first.

/warnrestart[:x]


Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.

/promptrestart


Displays a dialog box prompting the local user to allow a restart
Special Options

/forceappsclose


Forces other programs to close when the computer shuts down

/log:path


Allows the redirection of installation log files

File Information

The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, Windows XP Home Edition Service Pack 2, and Windows XP Media Center Edition 2005:
File Name Version Date Time Size Folder

Inetcomm.dll


6.0.2900.2869


17-Mar-2006


09:07


679,424


SP2GDR

Msoe.dll


6.0.2900.2869


17-Mar-2006


09:07


1,311,744


SP2GDR

Wab32.dll


6.0.2900.2869


17-Mar-2006


09:07


510,464


SP2GDR

Wabimp.dll


6.0.2900.2869


17-Mar-2006


09:07


85,504


SP2GDR

Inetcomm.dll


6.0.2900.2869


17-Mar-2006


09:12


679,424


SP2QFE

Msoe.dll


6.0.2900.2869


17-Mar-2006


09:12


1,311,744


SP2QFE

Wab32.dll


6.0.2900.2869


17-Mar-2006


09:12


510,464


SP2QFE

Wabimp.dll


6.0.2900.2869


17-Mar-2006


09:12


85,504


SP2QFE

Windows XP Professional x64:
File Name Version Date Time Size CPU Folder

Inetcomm.dll


6.0.3790.2663


18-Mar-2006


04:11


1,159,168


x64


SP1GDR

Msoe.dll


6.0.3790.2663


18-Mar-2006


04:11


2,146,816


x64


SP1GDR

Wab32.dll


6.0.3790.2663


18-Mar-2006


04:11


831,488


x64


SP1GDR

Wabimp.dll


6.0.3790.2663


18-Mar-2006


04:11


128,000


x64


SP1GDR

Wininetcomm.dll


6.0.3790.2663


18-Mar-2006


04:11


681,472


x86


SP1GDR\WOW

Wmsoe.dll


6.0.3790.2663


18-Mar-2006


04:11


1,315,328


x86


SP1GDR\WOW

Wwab32.dll


6.0.3790.2663


18-Mar-2006


04:11


510,976


x86


SP1GDR\WOW

Wwabimp.dll


6.0.3790.2663


18-Mar-2006


04:11


85,504


x86


SP1GDR\WOW

Inetcomm.dll


6.0.3790.2663


18-Mar-2006


04:09


1,159,168


x64


SP1QFE

Msoe.dll


6.0.3790.2663


18-Mar-2006


04:09


2,146,816


x64


SP1QFE

Wab32.dll


6.0.3790.2663


18-Mar-2006


04:09


831,488


x64


SP1QFE

Wabimp.dll


6.0.3790.2663


18-Mar-2006


04:09


128,000


x64


SP1QFE

Wininetcomm.dll


6.0.3790.2663


18-Mar-2006


04:09


681,472


x86


SP1QFE\WOW

Wmsoe.dll


6.0.3790.2663


18-Mar-2006


04:09


1,315,328


x86


SP1QFE\WOW

Wwab32.dll


6.0.3790.2663


18-Mar-2006


04:09


510,976


x86


SP1QFE\WOW

Wwabimp.dll


6.0.3790.2663


18-Mar-2006


04:09


85,504


x86


SP1QFE\WOW

Notes When you install this security update, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

If you have previously installed a hotfix to update one of these files, the installer copies the SP1QFE or SP2QFE files to your system. Otherwise, the installer copies the SP1GDR or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.

For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

Arpidfix.exe is used by the security update installer to address an issue documented in Microsoft Knowledge Base Article 904630. This file is not installed onto the affected system.

Verifying that the Update Has Been Applied


Microsoft Baseline Security Analyzer

To verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.


File Version Verification

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

1.


Click Start, and then click Search.

2.


In the Search Results pane, click All files and folders under Search Companion.

3.


In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.

4.


In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.

5.


On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.


Registry Key Verification

You may also be able to verify the files that this security update has installed by reviewing the following registry keys.

Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, Windows XP Home Edition Service Pack 2, and Windows XP Media Center Edition 2005:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB911567\911567

For Windows XP Professional x64 Edition:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP2\KB911567\911567

Note These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly if an administrator or an OEM integrates or slipstreams the 911567 security update into the Windows installation source files.
Top of sectionTop of section

Outlook Express 6 Service Pack 1 on Microsoft Windows XP Service Pack 1 or when installed on Microsoft Windows 2000 Service Pack 4

Prerequisites
To install the Outlook Express 6 Service Pack 1 (SP1) version of this update, you must be running Internet Explorer 6 SP1 (version 6.00.2800.1106) on one of the following versions of Windows:


Microsoft Windows 2000 Service Pack 4


Microsoft Small Business Server 2000 Service Pack 1a (SP1a) or Small Business Server 2000 running with Windows 2000 Server Service Pack 4 (SP4)


Microsoft Windows XP Service Pack 1

The software that is listed 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.

For more information about how to obtain the latest service pack, see Microsoft Knowledge Base Article 260910.

Inclusion in Future Service Packs
The update for this issue may be included in a future update rollup.

Installation Information

This security update supports the following setup switches.
Supported Security Update Installation Switches
Switch Description

/help


Displays the command-line options
Setup Modes

/passive


Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.

/quiet


Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options

/norestart


Does not restart when installation has completed

/forcerestart


Restarts the computer after installation and forces other applications to close at shutdown without saving open files first.

/warnrestart[:x]


Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.

/promptrestart


Displays a dialog box prompting the local user to allow a restart
Special Options

/overwriteoem


Overwrites OEM files without prompting

/nobackup


Does not back up files needed for uninstall

/forceappsclose


Forces other programs to close when the computer shuts down

/log:path


Allows the redirection of installation log files

/integrate:path


Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.

/extract[:path]


Extracts files without starting the Setup program

/ER


Enables extended error reporting

/verbose


Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for Windows 2000 Service Pack 4 or Windows XP Service Pack 1:

OE6.0sp1-KB911567-Windows-2000-XP-x86-ENU /quiet

Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB911567-OE6SP1-20060316.165634.log file for any failure messages when they use this switch.

To install the security update without forcing the system to restart, use the following command at a command prompt for Windows 2000 Service Pack 4:

OE6.0sp1-KB911567-Windows-2000-XP-x86-ENU /norestart

For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.

Restart Requirement

This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.

Removal Information

To remove this security update, use the Add or Remove Programs tool in Control Panel.

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB911567-OE6SP1-20060316.165634$\Spuninst.
Supported Spuninst.exe Switches
Switch Description

/help


Displays the command-line options
Setup Modes

/passive


Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.

/quiet


Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options

/norestart


Does not restart when installation has completed

/forcerestart


Restarts the computer after installation and forces other applications to close at shutdown without saving open files first.

/warnrestart[:x]


Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.

/promptrestart


Displays a dialog box prompting the local user to allow a restart
Special Options

/forceappsclose


Forces other programs to close when the computer shuts down

/log:path


Allows the redirection of installation log files

File Information

The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Outlook Express 6 Service Pack 1 on Windows 2000 Service Pack 4, Windows XP Service Pack 1 and Microsoft Small Business Server 2000 Service Pack 1a (SP1a) or Small Business Server 2000 running with Windows 2000 Server Service Pack 4 (SP4):
File Name Version Date Time Size

Directdb.dll


6.0.2800.1807


27-Feb-2006


21:31


75,776

Inetcomm.dll


6.0.2800.1807


27-Feb-2006


21:31


596,480

Inetres.dll


6.0.2800.1807


27-Feb-2006


21:31


47,616

Msident.dll


6.0.2800.1807


27-Feb-2006


21:29


44,032

Msimn.exe


6.0.2800.1807


27-Feb-2006


21:32


56,832

Msoe.dll


6.0.2800.1807


27-Feb-2006


21:32


1,176,064

Msoeacct.dll


6.0.2800.1807


27-Feb-2006


21:31


229,376

Msoeres.dll


6.0.2800.1807


27-Feb-2006


21:32


2,479,616

Msoert2.dll


6.0.2800.1807


27-Feb-2006


21:31


91,136

Oeimport.dll


6.0.2800.1807


27-Feb-2006


21:31


93,184

Oemig50.exe


6.0.2800.1807


27-Feb-2006


21:32


55,808

Oemiglib.dll


6.0.2800.1807


27-Feb-2006


21:32


31,744

Wab.exe


6.0.2800.1807


27-Feb-2006


21:31


42,496

Wab32.dll


6.0.2800.1816


17-Mar-2006


00:08


465,408

Wabfind.dll


6.0.2800.1807


27-Feb-2006


21:31


30,208

Wabimp.dll


6.0.2800.1807


27-Feb-2006


21:31


77,824

Wabmig.exe


6.0.2800.1807


27-Feb-2006


21:31


27,648

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

Verifying that the Update Has Been Applied


Microsoft Baseline Security Analyzer

To verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.


File Version Verification

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

1.


Click Start, and then click Search.

2.


In the Search Results pane, click All files and folders under Search Companion.

3.


In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.

4.


In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.

5.


On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.


Registry Key Verification

You may also be able to verify the files that this security update has installed by reviewing the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Outlook Express 6\SP1\KB911567-OE6SP1-20060316.165634\Filelist

Note This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly when an administrator or an OEM integrates or slipstreams the 911567 security update into the Windows installation source files.
Top of sectionTop of section

Outlook Express 5.5 Service Pack 2 for Windows 2000 Service Pack 4

Prerequisites


To install the Outlook Express 5.5 Service Pack 2 (SP2) version of this update, you must be running Internet Explorer 5.01 SP4 (version 5.00.3700.1000) on one of the following versions of Windows:


Microsoft Windows 2000 Service Pack 4


Microsoft Small Business Server 2000 Service Pack 1a (SP1a) or Small Business Server 2000 running with Windows 2000 Server Service Pack 4 (SP4)

The software that is listed 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.

For more information about how to obtain the latest service pack, see Microsoft Knowledge Base Article 260910.

Inclusion in Future Service Packs
The update for this issue may be included in a future update rollup.

Installation Information

This security update supports the following setup switches.
Supported Security Update Installation Switches
Switch Description

/help


Displays the command-line options
Setup Modes

/passive


Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.

/quiet


Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options

/norestart


Does not restart when installation has completed

/forcerestart


Restarts the computer after installation and forces other applications to close at shutdown without saving open files first.

/warnrestart[:x]


Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.

/promptrestart


Displays a dialog box prompting the local user to allow a restart
Special Options

/overwriteoem


Overwrites OEM files without prompting

/nobackup


Does not back up files needed for uninstall

/forceappsclose


Forces other programs to close when the computer shuts down

/log:path


Allows the redirection of installation log files

/integrate:path


Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.

/extract[:path]


Extracts files without starting the Setup program

/ER


Enables extended error reporting

/verbose


Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for Windows 2000 Service Pack 4:

OE5.5sp2-KB911567-Windows2000sp4-x86-ENU /quiet

Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB911567-OE55SP2-20060317.162653.log file for any failure messages when they use this switch.

To install the security update without forcing the system to restart, use the following command at a command prompt for Windows 2000 Service Pack 4:

OE5.5sp2-KB911567-Windows2000sp4-x86-ENU /norestart

For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.

Restart Requirement

This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.

Removal Information

To remove this security update, use the Add or Remove Programs tool in Control Panel.

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB911567-OE55SP2-20060317.162653$\Spuninst folder.
Supported Spuninst.exe Switches
Switch Description

/help


Displays the command-line options
Setup Modes

/passive


Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.

/quiet


Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options

/norestart


Does not restart when installation has completed

/forcerestart


Restarts the computer after installation and forces other applications to close at shutdown without saving open files first.

/warnrestart[:x]


Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.

/promptrestart


Displays a dialog box prompting the local user to allow a restart
Special Options

/forceappsclose


Forces other programs to close when the computer shuts down

/log:path


Allows the redirection of installation log files

File Information

The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Outlook Express 5.5 Service Pack 2 on Windows 2000 Service Pack 4, Microsoft Small Business Server 2000 Service Pack 1a (SP1a) or Small Business Server 2000 running with Windows 2000 Server Service Pack 4 (SP4):
File Name Version Date Time Size

Inetcomm.dll


5.50.4963.1700


17-Mar-2006


22:30


565,008

msoe.dll


5.50.4963.1700


17-Mar-2006


22:30


1,147,152

Wab.exe


5.50.4963.1700


17-Mar-2006


22:30


20,752

Wab32.dll


5.50.4963.1700


17-Mar-2006


22:30


452,368

Wabimp.dll


5.50.4963.1700


17-Mar-2006


22:30


85,264

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

Verifying that the Update Has Been Applied


Microsoft Baseline Security Analyzer

To verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.


File Version Verification

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

1.


Click Start, and then click Search.

2.


In the Search Results pane, click All files and folders under Search Companion.

3.


In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.

4.


In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.

5.


On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.


Registry Key Verification

You may also be able to verify the files that this security update has installed by reviewing the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Outlook Express 5.50\SP2\KB911567-OE55SP2-20060317.162653\Filelist

Note This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly when an administrator or an OEM integrates or slipstreams the 911567 security update into the Windows installation source files.
Top of sectionTop of section
Top of sectionTop of section

Acknowledgments

Microsoft thanks the following for working with us to help protect customers:


Stuart Pearson, working with TippingPoint and the Zero Day Initiative, for reporting the Microsoft Outlook Express when using a Windows Address Book File Vulnerability - CVE-2006-0014


ATmaCA for reporting similar behavior to the Microsoft Outlook Express when using a Windows Address Book File Vulnerability - CVE-2006-0014

Obtaining Other Security Updates:

Updates for other security issues are available at the following locations:


Security updates are available in the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch."


Updates for consumer platforms are available at the Microsoft Update Web site.

Support:


Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.


International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.

Security Resources:


The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.


Microsoft Software Update Services


Microsoft Windows Server Update Services


Microsoft Baseline Security Analyzer (MBSA)


Windows Update


Microsoft Update


Windows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.


Office Update?

Software Update Services:

By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.

For more information about how to deploy security updates by using Software Update Services, visit the Software Update Services Web site.

Windows Server Update Services:

By using Windows Server Update Services (WSUS), administrators can quickly and reliably deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 onto Windows 2000 and later operating systems.

For more information about how to deploy security updates using Windows Server Update Services, visit the Windows Server Update Services Web site.

Systems Management Server:

Microsoft Systems Management Server (SMS) delivers a highly-configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and can perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, visit the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site.

Note SMS uses the Microsoft Baseline Security Analyzer, the Microsoft Office Detection Tool, and the Enterprise Scan Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.

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 (April 11, 2006): Bulletin published.

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