Security Bulletin
Microsoft Security Bulletin MS06-043 - Critical
Vulnerability in Microsoft Windows Could Allow Remote Code Execution (920214)
Published: August 08, 2006
Version: 1.0
Summary
Who Should Read this Document: Customers who use Microsoft Windows
Impact of Vulnerability: Remote Code Execution
Maximum Severity Rating: Critical
Recommendation: Customers should apply the update immediately
Security Update Replacement: None
Caveats: None
Tested Software and Security Update Download Locations:
Affected Software:
- Microsoft Windows XP Service Pack 2
- Microsoft Windows XP Professional x64 Edition
- Microsoft Windows Server 2003 Service Pack 1
- Microsoft Windows Server 2003 with SP1 for Itanium-based Systems
- Microsoft Windows Server 2003 x64 Edition
Tested Microsoft Windows Components:
Affected Components:
- 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 Service Pack 1 - Download the update
- Outlook Express 6 on Microsoft Windows Server 2003 with SP1 for Itanium-based Systems - Download the update
- Outlook Express 6 on Microsoft Windows Server 2003 x64 Edition - Download the update
Non-Affected Software:
- Microsoft Windows 2000 Service Pack 4
- Microsoft Windows XP Service Pack 1
- Microsoft Windows Server 2003
- Microsoft Windows Server 2003 for Itanium-based Systems
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 Service Pack 1 and Windows Server 2003 x64 Edition also apply to Windows Server 2003 R2.
General Information
Executive Summary
Executive Summary:
This update resolves a newly-discovered, publicly-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 immediately.
Severity Ratings and Vulnerability Identifiers:
Vulnerability Identifiers | Impact of Vulnerability | Outlook Express 6 on Windows XP Service Pack 2 (including the 64-bit Edition) | Outlook Express 6 on Windows Server 2003 Service Pack 1 (including the 64-bit Edition) |
---|---|---|---|
MHTML Parsing Vulnerability - CVE-2006-2766 | Remote Code Execution | Critical | Critical |
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 Windows XP Professional x64 Edition severity rating is the same as the Windows XP Service Pack 2 severity rating.
- The 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 Windows Server 2003 x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.
Frequently Asked Questions (FAQ) Related to This Security Update
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 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 6 on 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 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 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
See “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 6 on Windows XP Service Pack 2 | Yes (with EST) | Yes |
Outlook Express 6 on Microsoft Windows XP Professional x64 Edition | No | Yes |
Outlook Express 6 on Microsoft Windows Server 2003 Service Pack 1 | Yes (with EST) | Yes |
Outlook Express 6 on Microsoft Windows Server 2003 x64 Edition | No | Yes |
Outlook Express 6 on Windows Server 2003 with SP1 for Itanium-based Systems | No | Yes |
SMS uses MBSA for detection. Therefore, SMS has the same limitation that is listed earlier in this bulletin related to programs that MBSA 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.
Vulnerability Details
MHTML Parsing Vulnerability - CVE-2006-2766:
There is a remote code execution vulnerability in Windows that results from incorrect parsing of the MHTML protocol. An attacker could exploit the vulnerability by constructing a specially crafted Web page or HTML e-mail that could potentially lead to remote code execution if a user visited a specially crafted Web site or clicked a link in a specially crafted e-mail message.
If a user were 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 MHTML Parsing Vulnerability - CVE-2006-2766:
- In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or instant messenger message that takes users to the attacker's Web site.
- 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.
- By default, Outlook Express 6 opens HTML e-mail messages in the Restricted sites zone. The Restricted sites zone helps limit attacks that could try to exploit this vulnerability by preventing ActiveX Controls from being used when reading HTML e-mail messages. However, if a user clicks a link in an e-mail message, the use could still be vulnerable to this issue through the Web-based attack scenario.
- By default, Internet Explorer on Windows Server 2003 runs in a restricted mode that is known as Enhanced Security Configuration. This mode mitigates this vulnerability in the e-mail vector because reading e-mail messages in plain text is the default configuration for Outlook Express. See the FAQ section for this security update for more information about Internet Explorer Enhanced Security Configuration.
Workarounds for MHTML Parsing Vulnerability - CVE-2006-2766:
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.
Modify the Access Control List to disable the MHTML Protocol registry key
Modifying the Access Control List on the “MHTML Protocol” registry key helps protect the affected system from attempts to exploit this vulnerability. To modify the MHTML Protocol 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.
Note Make a note of the permissions that are listed in the dialog box so that you can restore them to their original values at a later time
- Click Start, click Run, type "regedit" (without the quotation marks), and then click OK.
- Expand HKEY_CLASSES_ROOT, expand CLSID, and then click {05300401-BCBC-11d0-85E3-00C04FD85AB4}.
- Click Edit, and then click Permissions.
- Click Advanced.
- Click to clear the Inherit from parent the permission entries that apply to child objects. Include these with entries explicitly defined here. check box. You are prompted to click Copy, Remove, or Cancel. Click Remove, and then check OK.
- You receive a message that states that no one will be able to access this registry key. Click Yes, and then click OK to close the Permissions for {05300401-BCBC-11d0-85E3-00C04FD85AB4} dialog box.
Impact of Workaround: This workaround disables page rendering for MHTML Web pages.
FAQ for MHTML Parsing Vulnerability - CVE-2006-2766:
What is the scope of the vulnerability?
There is a remote code execution vulnerability in Windows that results from incorrect parsing of the MHTML protocol. An attacker could exploit the vulnerability by constructing a specially crafted Web page or HTML e-mail that could potentially lead to remote code execution if a user visited a specially crafted Web site or clicked a link in a specially crafted e-mail message.
If a user were 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?
Windows incorrectly parses the MHTML protocol.
What is MHTML?
MHTML extends HTML to embed encoded objects, such as images, in the HTML document. Although it is actually the HTML rendering extension that renders MHTML, this functionality may also be referred to as the MHTML rendering extension.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.
What are Internet Explorer security zones?
Internet Explorer security zones are part of a system that divides online content into categories or zones, based on the trustworthiness of the content. Specific Web domains can be assigned to a zone, depending on how much trust is put in the content of each domain. The zone then restricts the capabilities of the Web content, based on the zone's policy. By default, most Internet domains are treated as part of the Internet zone. By default, the policy of the Internet zone prevents scripts and other active code from accessing resources on the local system.
How could an attacker exploit the vulnerability?
An attacker could host a specially crafted Web site or HTML e-mail message that is designed to exploit this vulnerability through Internet Explorer and then persuade a user to view the Web site or HTML e-mail message. This can also include Web sites that accept user-provided content or advertisements, Web sites that host user-provided content or advertisements, and compromised Web sites. These Web sites could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or in an Instant Messenger request that takes users to the attacker's Web site. It could also be possible to display specially crafted Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.
What systems are primarily at risk from the vulnerability?
This vulnerability requires a user to be logged on and visiting a Web site for any malicious action to occur. Therefore, any systems where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability.
What does the update do?
The update removes the vulnerability by changing Windows so that it correctly parses the MHTML protocol.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CVE-2006-2766.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had seen examples of proof of concept code published publicly but had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.
Does applying this security update help protect customers from the code that has been published publicly that attempts to exploit this vulnerability?
Yes. This security update addresses the vulnerability that potentially could be exploited by using the published proof of concept code. The vulnerability that has been addressed has been assigned the Common Vulnerability and Exposure number CVE-2006-2766.
Security Update Information
Affected Software:
For information about the specific security update for your affected software, click the appropriate link:
Outlook Express 6 on Windows Server 2003 (all versions)
Prerequisites This security update requires Windows Server 2003 Service Pack 1.
Note The security updates for Microsoft Windows Server 2003 Service Pack 1 and Windows Server 2003 x64 Edition also apply to Microsoft Windows Server 2003 R2.
Inclusion in Future Service Packs: The update for this issue will be included in future Service Pack or Update Rollup.
Installation Information
This security update supports the following setup 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] | Displays 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 | Display 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 uninstallation. |
/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-kb920214-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 KB920214.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-kb920214-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.
To help reduce the chance that a reboot will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. 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%\$NTUninstallKB920214$\Spuninst folder.
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] | Displays 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 | Display 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 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.2757 | 26-Jul-2006 | 17:07 | 681,472 | SP1GDR |
Inetcomm.dll | 6.0.3790.2757 | 26-Jul-2006 | 17:40 | 681,472 | SP1QFE |
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.2757 | 26-Jul-2006 | 18:26 | 2,369,024 | IA-64 | SP1GDR |
Winetcomm.dl | 6.0.3790.2757 | 26-Jul-2006 | 18:26 | 681,472 | x86 | SP1GDR\WOW |
Inetcomm.dll | 6.0.3790.2757 | 26-Jul-2006 | 18:17 | 2,369,024 | IA-64 | SP1QFE |
Winetcomm.dl | 6.0.3790.2757 | 26-Jul-2006 | 18:17 | 681,472 | 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.2757 | 26-Jul-2006 | 18:24 | 1,159,168 | x64 | SP1GDR |
Winetcomm.dll | 6.0.3790.2757 | 26-Jul-2006 | 18:24 | 681,472 | x86 | SP1GDR\WOW |
Inetcomm.dll | 6.0.3790.2757 | 26-Jul-2006 | 18:16 | 1,159,168 | x64 | SP1QFE |
Winetcomm.dll | 6.0.3790.2757 | 26-Jul-2006 | 18:16 | 681,472 | x86 | SP1QFE\WOW |
Notes When you install these security updates 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 one of these files, the installer copies the RTMQFE files to your system. Otherwise, the installer copies the RTMGDR 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.
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.- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- 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.
- 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 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, 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, ; Windows Server 2003 R2, Standard x64 Edition; Windows Server 2003 R2, Enterprise x64 Edition; and Windows Server 2003 R2, Datacenter x64 Edition:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP2\KB920214\Filelist
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 920214 security update into the Windows installation source files.
Outlook Express 6 on Windows XP Service Pack 2 and Windows 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.
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] | Displays 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 | Display 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 uninstallation. |
/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-kb920214-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 KB920214.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-kb920214-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
To help reduce the chance that a reboot will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. 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%\$NTUninstallKB920214$\Spuninst folder.
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] | Displays 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 | Display 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.2962 | 27-Jul-2006 | 13:24 | 679,424 | SP2GDR |
Inetcomm.dll | 6.0.2900.2962 | 27-Jul-2006 | 13:29 | 679,424 | SP2QFE |
Windows XP Professional x64:
File Name | Version | Date | Time | Size | CPU | Folder |
---|---|---|---|---|---|---|
Inetcomm.dll | 6.0.3790.2757 | 26-Jul-2006 | 18:24 | 1,159,168 | x64 | SP1GDR |
Winetcomm.dll | 6.0.3790.2757 | 26-Jul-2006 | 18:24 | 681,472 | x86 | SP1GDR\WOW |
Inetcomm.dll | 6.0.3790.2757 | 26-Jul-2006 | 18:16 | 1,159,168 | x64 | SP1QFE |
Winetcomm.dll | 6.0.3790.2757 | 26-Jul-2006 | 18:16 | 681,472 | x86 | SP1QFE\WOW |
Notes When you install these security updates, 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.
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.Click Start, and then click Search.
In the Search Results pane, click All files and folders under Search Companion.
In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
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.
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.For Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB920214\Filelist
For Windows XP Professional x64 Edition:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP2\KB920214\Filelist
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 920214 security update into the Windows installation source files.
Other Information
Obtaining Other Security Updates:
Updates for other security issues are available at the following locations:
- Security updates are available at 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 Update Scanning 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 (August 8, 2006): Bulletin published.
Built at 2014-04-18T13:49:36Z-07:00