Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Microsoft Security Bulletin MS06-067 - Critical

Cumulative Security Update for Internet Explorer (922760)

Published: November 14, 2006 | Updated: October 24, 2007

Version: 1.1

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: This bulletin replaces several prior security updates. See the frequently asked questions (FAQ) section of this bulletin for the complete list.

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

Tested Software and Security Update Download Locations:

Affected Software:

  • Microsoft Windows 2000 Service Pack 4
  • Microsoft Windows XP Service Pack 2
  • Microsoft Windows XP Professional x64 Edition
  • Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1
  • Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems
  • Microsoft Windows Server 2003 x64 Edition

Non-Affected Software:

  • Windows Vista

Tested Microsoft Windows Components:

Affected Components:

  • Microsoft Internet Explorer 5.01 Service Pack 4 on Windows 2000 Service Pack 4 — Download the update
  • Microsoft Internet Explorer 6 Service Pack 1 on Windows 2000 Service Pack 4 — Download the update
  • Microsoft Internet Explorer 6 for Windows XP Service Pack 2 — Download the update
  • Microsoft Internet Explorer 6 for Windows XP Professional x64 Edition — Download the update
  • Microsoft Internet Explorer 6 for Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 — Download the update
  • Microsoft Internet Explorer 6 for Windows Server 2003 for Itanium-based Systems and Windows Server 2003 with SP1 for Itanium-based Systems — Download the update
  • Microsoft Internet Explorer 6 for Windows Server 2003 x64 Edition — Download the update

Non-Affected Components:

  • Windows Internet Explorer 7 for Windows XP Service Pack 2
  • Windows Internet Explorer 7 for Windows XP Professional x64 Edition
  • Windows Internet Explorer 7 for Windows Server 2003 Service Pack 1
  • Windows Internet Explorer 7 for Windows Server 2003 with SP1 for Itanium-based Systems
  • Windows Internet Explorer 7 for Windows Server 2003 x64 Edition
  • Windows Internet Explorer 7 in Windows Vista

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

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

General Information

Executive Summary:

This update resolves several newly discovered, publicly and privately reported vulnerabilities. Each vulnerability is documented in its own “Vulnerability Details” section of this bulletin.

If a user is logged on with administrative user rights, an attacker who successfully exploited the most severe of these vulnerabilities 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 IdentifiersImpact of VulnerabilityInternet Explorer 5.01 Service Pack 4 on Windows 2000 Service Pack 4Internet Explorer 6 Service Pack 1 for Windows 2000 Service Pack 4Internet Explorer 6 for Windows XP Service Pack 2Internet Explorer 6 for Windows Server 2003Internet Explorer 6 for Windows Server 2003 Service Pack 1
DirectAnimation ActiveX Controls Memory Corruption Vulnerability - CVE-2006-4777Remote Code ExecutionCriticalCriticalCriticalModerateModerate
DirectAnimation ActiveX Controls Memory Corruption Vulnerability - CVE-2006-4446Remote Code ExecutionCriticalCriticalCriticalModerateModerate
HTML Rendering Memory Corruption Vulnerability - CVE-2006-4687Remote Code ExecutionNoneCriticalCriticalCriticalCritical
Aggregate Severity of All VulnerabilitiesCriticalCriticalCriticalCriticalCritical

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

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

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

  • The Windows XP Professional x64 Edition severity rating is the same as the Windows XP Service Pack 2 severity rating.
  • The Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.
  • The Windows Server 2003 with SP1 for Itanium-based Systems severity rating is the same as the Windows Server 2003 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.
  • The Internet Explorer 6 for Windows XP Professional x64 Edition severity rating is the same as the Internet Explorer 6 Service Pack 1 (all supported operating system versions earlier than Windows Server 2003) severity rating.
  • The Internet Explorer 6 for Windows Server 2003 for Itanium-based Systems and Windows Server 2003 x64 Edition severity rating is the same as the Internet Explorer 6 for Windows Server 2003 severity rating.

What updates does this release replace?
This security update replaces several prior security updates. The most recent security bulletin ID and affected operating systems are listed in the following table.

Bulletin IDInternet Explorer 5.01 Service Pack 4 on Windows 2000 Service Pack 4Internet Explorer 6 Service Pack 1 for Windows 2000 Service Pack 4Internet Explorer 6 for Windows Server 2003 Internet Explorer 6 for Windows Server 2003 Service Pack 1Internet Explorer 6 for Windows XP Service Pack 2
MS06-042ReplacedReplacedReplacedReplacedReplaced
MS06-065Not applicableNot applicableReplacedReplacedReplaced

Why did Microsoft revise this bulletin on October 24, 2007?
The bulletin text was updated to document that MS06-065 is replaced by this bulletin for Internet Explorer 6 for Windows Server 2003 and Windows Server 2003 Service Pack 1 and for Internet Explorer 6 for Windows XP Service Pack 2. This change affects the bulletin text only and does not affect the security update itself.

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

Does this update contain any security-related changes to functionality?
Yes. Besides the changes that are listed in the “Vulnerability Details” section of this bulletin, also included are security-related changes that were introduced in previous Internet Explorer bulletins.

This security update also sets kill bits for ActiveX controls included with WinZip 10.0, software available from WinZip Computing. WinZip Computing has released a security bulletin and an update that addresses a vulnerability in WinZip 10.0. This vulnerability exists in ActiveX controls that were never intended to be used in Internet Explorer. For more information and download locations, see the security bulletin from WinZip Computing. These kill bits are being set with the permission of the owner of the ActiveX controls. For more information about kill bits, see Microsoft Knowledge Base Article 240797. The class identifiers (CLSIDs) for this ActiveX control are:

  • {A09AE68F-B14D-43ED-B713-BA413F034904}
  • {F3834A2B-19CF-4A90-BE1D-ECC410D9DA09}

Does this update contain any other changes to functionality?
Yes. Besides the changes that are listed in the “Vulnerability Details” section of this bulletin, there are also changes not related to security that were introduced in previous Internet Explorer bulletins.

Like the security update included with MS06-042 this security update also replaces the compatibility patch released on April 11, 2006. That compatibility patch temporarily returned Internet Explorer to the previous functionality for handling ActiveX controls, to help enterprise customers who needed more time to prepare for the ActiveX update changes discussed in Microsoft Knowledge Base Article 912945. This security update replaces that compatibility patch, and makes the changes in Microsoft Knowledge Base Article 912945 permanent. For more information about these changes, see Microsoft Knowledge Base Article 912945 and the product documentation.

The changes were first introduced in updates for Windows XP Service Pack 2, Windows Server 2003 Service Pack 1, Windows XP Professional x64 Edition, Windows Server 2003 x64 Edition family, and Windows Server 2003 with Service Pack 1 for Itanium-based Systems on February 28, 2006. For more information about this update, see Microsoft Knowledge Base Article 912945.

The changes are also included in Microsoft Security Bulletin MS06-013 and subsequent security bulletins for Internet Explorer for the same versions of Windows.

What is the Internet Explorer Enhanced Security Configuration?
Internet Explorer Enhanced Security Configuration is a group of preconfigured Internet Explorer settings that reduce the likelihood of a user or an administrator downloading and running specially crafted Web content on a server. Internet Explorer Enhanced Security Configuration reduces this risk by modifying many security-related settings. This includes the settings on the Security tab and the Advanced tab in the Internet Options dialog box. Some of the important modifications include the following:

  • Security level for the Internet zone is set to High. This setting disables scripts, ActiveX controls, Microsoft Java Virtual Machine (MSJVM), and file downloads.
  • Automatic detection of intranet sites is disabled. This setting assigns all intranet Web sites and all Universal Naming Convention (UNC) paths that are not explicitly listed in the Local intranet zone to the Internet zone.
  • Install On Demand and non-Microsoft browser extensions are disabled. This setting prevents Web pages from automatically installing components and prevents non-Microsoft extensions from running.
  • Multimedia content is disabled. This setting prevents music, animations, and video clips from running.

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

Extended security update support for 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, and Windows Millennium Edition have reached the end of their support 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.

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

SoftwareMBSA 1.2.1MBSA 2.0
Microsoft Windows 2000 Service Pack 4YesYes
Microsoft Windows XP Service Pack 2YesYes
Microsoft Windows XP Professional x64 EditionNoYes
Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1YesYes
Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based SystemsNoYes
Microsoft Windows Server 2003 x64 Edition familyNoYes

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

For more detailed information, see Microsoft Knowledge Base Article 910723.

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.

SoftwareSMS 2.0SMS 2003
Microsoft Windows 2000 Service Pack 4YesYes
Microsoft Windows XP Service Pack 2YesYes
Microsoft Windows XP Professional x64 EditionNoYes
Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1YesYes
Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based SystemsNoYes
Microsoft Windows Server 2003 x64 Edition familyNoYes

SMS uses MBSA for detection. Therefore, SMS has the same limitation that is listed earlier in this bulletin related to software 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.

For more detailed information, see Microsoft Knowledge Base Article 910723.

DirectAnimation ActiveX Controls Memory Corruption Vulnerabilities - CVE-2006-4446 and CVE-2006-4777:

Remote code execution vulnerabilities exist in DirectAnimation ActiveX controls that could be exploited if the ActiveX controls are passed unexpected data. An attacker could exploit these vulnerabilities by constructing a specially crafted Web page that could potentially allow remote code execution if a user visited the specially crafted Web page. An attacker who successfully exploited these vulnerabilities could take complete control of an affected system.

Mitigating Factors for DirectAnimation ActiveX Controls Memory Corruption Vulnerabilities - CVE-2006-4446 and CVE-2006-4777:

  • In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit these vulnerabilities. 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 these vulnerabilities. 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 these vulnerabilities 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.
  • The Restricted sites zone helps reduce attacks that could try to exploit these vulnerabilities by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail. However, if a user clicks on a link within an e-mail they could still be vulnerable to this issue through the Web-based attack scenario.

    By default, Outlook Express 6, Outlook 2002, and Outlook 2003 open HTML e-mail messages in the Restricted sites zone. Additionally Outlook 2000 opens HTML e-mail messages in the Restricted sites zone if the Outlook E-mail Security Update has been installed. Outlook Express 5.5 Service Pack 2 opens HTML e-mail messages in the Restricted sites zone if Microsoft Security Bulletin MS04-018 has been installed.
  • By default, Internet Explorer on Windows Server 2003 runs in a restricted mode that is known as Enhanced Security Configuration. This mode sets the security level for the Internet zone to High. This is a mitigating factor for Web sites that have not been added to Internet Explorer Trusted sites zone. See the FAQ section of this security update for more information about Internet Explorer Enhanced Security Configuration

Workarounds for DirectAnimation ActiveX Controls Memory Corruption Vulnerability - CVE-2006-4446 and CVE-2006-4777:

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.

  • Prevent the Microsoft DirectAnimation Path ActiveX control from running in Internet Explorer

    You can help prevent attempts to instantiate this ActiveX control in Internet Explorer by setting the kill bit for the control in the registry.

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

    For detailed steps that you can use to prevent a control from running in Internet Explorer, see Microsoft Knowledge Base Article 240797. Follow these steps in this article to create a Compatibility Flags value in the registry to prevent a COM object from being instantiated in Internet Explorer.

    To set the kill bit for a CLSID with a value of {D7A7D7C3-D47F-11D0-89D3-00A0C90833E6}, paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension.

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{D7A7D7C3-D47F-11D0-89D3-00A0C90833E6}]
    "Compatibility Flags"=dword:00000400

    You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy. For more information about Group Policy, visit the following Microsoft Web sites:

    Group Policy collection

    What is Group Policy Object Editor?

    Core Group Policy tools and settings

    Note You must restart Internet Explorer for your changes to take effect.

    Impact of Workaround: Web sites that use the DirectAnimation Path ActiveX Controls may no longer display or function correctly.

    This workaround can also be used for all other CLSIDs for which kill bits are being set in this security update.

  • Configure Internet Explorer to prompt before running ActiveX Controls or disable ActiveX Controls in the Internet and Local intranet security zone

    You can help protect against these vulnerabilities by changing your Internet Explorer settings to prompt before running ActiveX controls. To do this, follow these steps:

    1. In Internet Explorer, click Internet Options on the Tools menu.
    2. Click the Security tab.
    3. Click Internet, and then click Custom Level.
    4. Under Settings, in the ActiveX controls and plug-ins section, under Run ActiveX controls and plug-ins, click Prompt or Disable, and then click OK.
    5. Click Local intranet, and then click Custom Level.
    6. Under Settings, in the ActiveX controls and plug-ins section, under Run ActiveX controls and plug-ins, click Prompt or Disable, and then click OK.
    7. Click OK two times to return to Internet Explorer.

    Impact of Workaround: There are side effects to prompting before running ActiveX controls. Many Web sites that are on the Internet or on an intranet use ActiveX to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX controls to provide menus, ordering forms, or even account statements. Prompting before running ActiveX controls is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run ActiveX controls. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone”.

    Add sites that you trust to the Internet Explorer Trusted sites zone

    After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.

    To do this, follow these steps:

    1. In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
    2. In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
    3. If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
    4. In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
    5. Repeat these steps for each site that you want to add to the zone.
    6. Click OK two times to accept the changes and return to Internet Explorer.

    Note Add any sites that you trust not to take malicious action on your computer. Two in particular that you may want to add are "*.windowsupdate.microsoft.com" and “*.update.microsoft.com” (without the quotation marks). These are the sites that will host the update, and it requires an ActiveX Control to install the update.

  • Set Internet and Local intranet security zone settings to “High” to prompt before running ActiveX Controls and Active Scripting in these zones

    You can help protect against these vulnerabilities by changing your settings for the Internet security zone to prompt before running ActiveX controls. You can do this by setting your browser security to High.

    To raise the browsing security level in Microsoft Internet Explorer, follow these steps:

    1. On the Internet Explorer Tools menu, click Internet Options.
    2. In the Internet Options dialog box, click the Security tab, and then click the Internet icon.
    3. Under Security level for this zone, move the slider to High. This sets the security level for all Web sites you visit to High.

    Note If no slider is visible, click Default Level, and then move the slider to High.

    Note Setting the level to High may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly even with the security setting set to High.

    Impact of Workaround: There are side effects to prompting before running ActiveX controls. Many Web sites that are on the Internet or on an intranet use ActiveX to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX controls to provide menus, ordering forms, or even account statements. Prompting before running ActiveX controls is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run ActiveX controls. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone”.

    Add sites that you trust to the Internet Explorer Trusted sites zone

    After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.

    To do this, follow these steps:

    1. In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
    2. In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
    3. If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
    4. In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
    5. Repeat these steps for each site that you want to add to the zone.
    6. Click OK two times to accept the changes and return to Internet Explorer.

    Note Add any sites that you trust not to take malicious action on your computer. Two in particular that you may want to add are "*.windowsupdate.microsoft.com" and “*.update.microsoft.com” (without the quotation marks). These are the sites that will host the update, and it requires an ActiveX Control to install the update.

FAQ for DirectAnimation ActiveX Controls Memory Corruption Vulnerabilities - CVE-2006-4446 and CVE-2006-4777:

What is the scope of the vulnerability?
These are remote code execution vulnerabilities. An attacker who successfully exploited these vulnerabilities could remotely 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.

What causes the vulnerability?
Remote code execution vulnerabilities exist in DirectAnimation ActiveX controls that could be exploited if the ActiveX controls are passed unexpected data. This could cause Internet Explorer to fail in a way that could allow code execution.

What is DirectAnimation?
DirectAnimation as a whole is a deprecated suite of development functionality. Microsoft recommends using more recent functions in Microsoft DirectX when developing Web applications and other software that needs advanced animation. After this security update is installed, Web applications and software that use DirectAnimation will not function as expected. One way of accessing the functionality that was exposed in the DirectAnimation suite was by using HTML+TIME 1.0.

What is HTML+TIME?
HTML+TIME (Timed Interactive Multimedia Extensions) adds timing and media synchronization support to HTML pages. HTML+TIME 1.0, which is a wrapper for DirectAnimation, is deprecated functionality and has been replaced by HTML+TIME 2.0. Customers who use HTML+TIME 1.0 are encouraged to use the Microsoft implementation of HTML+TIME 2.0 instead. After this security update is installed, Web applications and software that use HTML+TIME 1.0 will not function as expected.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited these vulnerabilities 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.

How could an attacker exploit the vulnerability?
An attacker could host a specially crafted Web site that is designed to exploit these vulnerabilities through Internet Explorer and then persuade a user to view the Web site. 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 these vulnerabilities. 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 that a user is logged on and visits 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 these vulnerabilities.

I am running Internet Explorer on Windows Server 2003. Does this mitigate these vulnerabilities?
Yes. By default, Internet Explorer on Windows Server 2003 runs in a restricted mode that is known as Enhanced Security Configuration. This mode sets the security level for the Internet zone to High. This is a mitigating factor for Web sites that have not been added to Internet Explorer Trusted sites zone.

What is the Internet Explorer Enhanced Security Configuration?
Internet Explorer Enhanced Security Configuration is a group of preconfigured Internet Explorer settings that reduce the likelihood of a user or of an administrator downloading and running specially crafted Web content on a server. Internet Explorer Enhanced Security Configuration reduces this risk by modifying many security-related settings. This includes the settings on the Security tab and the Advanced tab in the Internet Options dialog box. Some of the important modifications include the following:

  • Security level for the Internet zone is set to High. This setting disables scripts, ActiveX controls, Microsoft Java Virtual Machine (MSJVM), and file downloads.
  • Automatic detection of intranet sites is disabled. This setting assigns all intranet Web sites and all Universal Naming Convention (UNC) paths that are not explicitly listed in the Local intranet zone to the Internet zone.
  • Install On Demand and non-Microsoft browser extensions are disabled. This setting prevents Web pages from automatically installing components and prevents non-Microsoft extensions from running.
  • Multimedia content is disabled. This setting prevents music, animations, and video clips from running.

For more information regarding Internet Explorer Enhanced Security Configuration, see the guide, Managing Internet Explorer Enhanced Security Configuration, at the following Web site.

What does the update do?
The update removes support for the DirectAnimation Path ActiveX control in Internet Explorer by setting the kill bit for control. In addition, as a defense in depth measure, this update sets kill bits for DirectAnimation as a whole as it is a deprecated suite of development functionality. Microsoft recommends using Microsoft DirectX and HTML+TIME 2.0 when developing Web applications and other software.

The Class Identifiers and corresponding files where the DirectAnimation functionality is contained are as follows.

Class IdentifierFile
{D17506C3-6B26-11D0-8914-00C04FC2A0CA}Danim.dll
{C46C1BCE-3C52-11D0-9200-848C1D000000}Danim.dll
{C46C1BDE-3C52-11D0-9200-848C1D000000}Danim.dll
{C46C1BC1-3C52-11D0-9200-848C1D000000}Danim.dll
{C46C1BE2-3C52-11D0-9200-848C1D000000}Danim.dll
{C46C1BC6-3C52-11D0-9200-848C1D000000}Danim.dll
{C46C1BF0-3C52-11D0-9200-848C1D000000}Danim.dll
{C46C1BEC-3C52-11D0-9200-848C1D000000}Danim.dll
{50B4791F-4731-11D0-8912-00C04FC2A0CA}Danim.dll
{25B0F91C-D23D-11D0-9B85-00C04FC2F51D}Danim.dll
{C46C1BE0-3C52-11D0-9200-848C1D000000}Danim.dll
{C46C1BD4-3C52-11D0-9200-848C1D000000}Danim.dll
{C46C1BEE-3C52-11D0-9200-848C1D000000}Danim.dll
{C46C1BF2-3C52-11D0-9200-848C1D000000}Danim.dll
{C46C1BD2-3C52-11D0-9200-848C1D000000}Danim.dll
{C46C1BE6-3C52-11D0-9200-848C1D000000}Danim.dll
{C46C1BD6-3C52-11D0-9200-848C1D000000}Danim.dll
{9CDE7341-3C20-11D0-A330-00AA00B92C03}Danim.dll
{C46C1BF4-3C52-11D0-9200-848C1D000000}Danim.dll
{C46C1BD0-3C52-11D0-9200-848C1D000000}Danim.dll
{C46C1BC8-3C52-11D0-9200-848C1D000000}Danim.dll
{C46C1BD8-3C52-11D0-9200-848C1D000000}Danim.dll
{C46C1BE4-3C52-11D0-9200-848C1D000000}Danim.dll
{C46C1BC4-3C52-11D0-9200-848C1D000000}Danim.dll
{C46C1BCC-3C52-11D0-9200-848C1D000000}Danim.dll
{C46C1BDC-3C52-11D0-9200-848C1D000000}Danim.dll
{AF868304-AB0B-11D0-876A-00C04FC29D46}Danim.dll
{C46C1BCA-3C52-11D0-9200-848C1D000000}Danim.dll
{C46C1BDA-3C52-11D0-9200-848C1D000000}Danim.dll
{283807B5-2C60-11D0-A31D-00AA00B92C03}Danim.dll
{B6FFC24C-7E13-11D0-9B47-00C04FC2F51D}Danim.dll
{69AD90EF-1C20-11d1-8801-00C04FC29D46}Danim.dll
{D7A7D7C3-D47F-11D0-89D3-00A0C90833E6}Daxctle.ocx
{4F241DB1-EE9F-11D0-9824-006097C99E51}Daxctle.ocx
{B0A6BAE2-AAF0-11D0-A152-00A0C908DB96}Daxctle.ocx
{FD179533-D86E-11D0-89D6-00A0C90833E6}Daxctle.ocx
{369303C2-D7AC-11D0-89D5-00A0C90833E6}Daxctle.ocx
{BB339A46-7C49-11d2-9BF3-00C04FA34789}Lmrt.dll
{B1549E58-3894-11D2-BB7F-00A0C999C4C1}Lmrt.dll

When this security bulletin was issued, had these vulnerabilities been publicly disclosed?
Yes. These vulnerabilities have been publicly disclosed. They have been assigned Common Vulnerability and Exposure numbers CVE-2006-4446 and CVE-2006-4777. This security bulletin addresses the publicly disclosed vulnerabilities as well as additional issues discovered through internal investigations.

When this security bulletin was issued, had Microsoft received any reports that these vulnerabilities were being exploited?
Yes. When the security bulletin was released, Microsoft had received information that these vulnerabilities were being exploited.

Does applying this security update help protect customers from the code that has been published publicly that attempts to exploit these vulnerabilities?
Yes. This security update addresses the vulnerabilities that are currently being exploited. The vulnerabilities that have been addressed have been assigned the Common Vulnerability and Exposure number CVE-2006-4446 and CVE-2006-4777.

HTML Rendering Memory Corruption Vulnerability - CVE-2006-4687:

A remote code execution vulnerability exists in the way Internet Explorer interprets HTML with certain layout combinations. An attacker could exploit the vulnerability by constructing a specially crafted Web page that could potentially allow remote code execution if a user viewed the Web page. An attacker who successfully exploited this vulnerability could take complete control of an affected system.

Mitigating Factors for HTML Rendering Memory Corruption Vulnerability - CVE-2006-4687:

  • 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.
  • The Restricted sites zone helps reduce attacks that could try to exploit this vulnerability by preventing Active Scripting from being used when reading HTML e-mail messages. However, if a user clicks a link in an e-mail message, the user could still be vulnerable to this issue through the Web-based attack scenario.

    By default, Outlook Express 6, Outlook 2002, and Outlook 2003 open HTML e-mail messages in the Restricted sites zone. Additionally Outlook 2000 opens HTML e-mail messages in the Restricted sites zone if the Outlook E-mail Security Update has been installed. Outlook Express 5.5 Service Pack 2 opens HTML e-mail messages in the Restricted sites zone if Microsoft Security Bulletin MS04-018 has been installed.

    Note It cannot be ruled out that this vulnerability could be used in an exploit without Active Scripting. However, using Active Scripting significantly increases the chances of a successful exploit. As a result, this vulnerability has been given a severity rating of Critical on Windows Server 2003.
  • 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 of this security update for more information about Internet Explorer Enhanced Security Configuration.

Workarounds for HTML Rendering Memory Corruption Vulnerability - CVE-2006-4687:

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.

Note It cannot be ruled out that this vulnerability could be used in an exploit without Active Scripting. However, using Active Scripting significantly increases the chances of a successful exploit. As a result, this vulnerability has been given a severity rating of Critical on Windows Server 2003.

  • Configure Internet Explorer to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone

    You can help protect against this vulnerability by changing your settings to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone. To do this, follow these steps:

    1. In Internet Explorer, click Internet Options on the Tools menu.
    2. Click the Security tab.
    3. Click Internet, and then click Custom Level.
    4. Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK.
    5. Click Local intranet, and then click Custom Level.
    6. Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK.
    7. Click OK two times to return to Internet Explorer.

    Note Disabling Active Scripting in the Internet and Local intranet security zones may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly.

    Impact of Workaround: There are side effects to prompting before running Active Scripting. Many Web sites that are on the Internet or on an intranet use Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use Active Scripting to provide menus, ordering forms, or even account statements. Prompting before running Active Scripting is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run Active Scripting. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone”.

    Add sites that you trust to the Internet Explorer Trusted sites zone.

    After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.

    To do this, follow these steps:

    1. In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
    2. In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
    3. If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
    4. In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
    5. Repeat these steps for each site that you want to add to the zone.
    6. Click OK two times to accept the changes and return to Internet Explorer.

    Note Add any sites that you trust not to take malicious action on your computer. Two in particular that you may want to add are "*.windowsupdate.microsoft.com" and “*.update.microsoft.com” (without the quotation marks). These are the sites that will host the update, and it requires an ActiveX Control to install the update.

  • Set Internet and Local intranet security zone settings to “High” to prompt before running ActiveX Controls and Active Scripting in these zones

    You can help protect against this vulnerability by changing your settings for the Internet security zone to prompt before running ActiveX controls and Active Scripting. You can do this by setting your browser security to High.

    To raise the browsing security level in Microsoft Internet Explorer, follow these steps:

    1. On the Internet Explorer Tools menu, click Internet Options.
    2. In the Internet Options dialog box, click the Security tab, and then click the Internet icon.
    3. Under Security level for this zone, move the slider to High. This sets the security level for all Web sites you visit to High.

    Note If no slider is visible, click Default Level, and then move the slider to High.

    Note Setting the level to High may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly even with the security setting set to High.

    Impact of Workaround: There are side effects to prompting before running ActiveX Controls and Active Scripting. Many Web sites that are on the Internet or on an intranet use ActiveX or Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX Controls to provide menus, ordering forms, or even account statements. Prompting before running ActiveX Controls or Active Scripting is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run ActiveX Controls or Active Scripting. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone”

    Add sites that you trust to the Internet Explorer Trusted sites zone.

    After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.

    To do this, follow these steps:

    1. In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
    2. In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
    3. If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
    4. In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
    5. Repeat these steps for each site that you want to add to the zone.
    6. Click OK two times to accept the changes and return to Internet Explorer.

    Note Add any sites that you trust not to take malicious action on your computer. Two in particular that you may want to add are "*.windowsupdate.microsoft.com" and “*.update.microsoft.com” (without the quotation marks). These are the sites that will host the update, and it requires an ActiveX Control to install the update.

  • Read e-mail messages in plain text format if you are using Outlook 2002 or a later version, or Outlook Express 6 SP1 or a later version, to help protect yourself from the HTML e-mail attack vector.

    Microsoft Outlook 2002 users who have applied Office XP Service Pack 1 or a later version and Microsoft Outlook Express 6 users who have applied Internet Explorer 6 Service Pack 1 or a later version can enable this setting and view e-mail messages that are not digitally signed or e-mail messages that are not encrypted in plain text only.

    Digitally signed e-mail messages or encrypted e-mail messages are not affected by the setting and may be read in their original formats. For more information about how to enable this setting in Outlook 2002, see Microsoft Knowledge Base Article 307594.

    For information about this setting in Outlook Express 6, see Microsoft Knowledge Base Article 291387.

    Impact of Workaround: E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. Additionally:

    • The changes are applied to the preview pane and to open messages.
    • Pictures become attachments so that they are not lost.
    • Because the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.

FAQ for HTML Rendering Memory Corruption Vulnerability - CVE-2006-4687:

What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could remotely 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.

What causes the vulnerability?
When Internet Explorer handles specially crafted HTML with certain HTML layout combinations it may corrupt system memory in such a way that an attacker could execute arbitrary code.

What might an attacker use the vulnerability to do?
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.

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 that a user is logged on and reading HTML e-mail messages or that a user is logged on and visits a Web site for any malicious action to occur. Therefore, any systems where HTML e-mail messages are read or where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability.

Note It cannot be ruled out that this vulnerability could be used in an exploit without Active Scripting. However, using Active Scripting significantly increases the chances of a successful exploit. As a result, this vulnerability has been given a severity rating of Critical on Windows Server 2003.

What does the update do?
The update removes the vulnerability by modifying the way that Internet Explorer decodes certain layout combinations in HTML.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure.

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.

Affected Software:

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

Windows Server 2003 (all versions)

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

Note The security updates for Microsoft Windows Server 2003, Microsoft Windows Server 2003 Service Pack 1, and Microsoft 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 a future Service Pack or Update Rollup.

Installation Information

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts the computer after installation and force 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.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/overwriteoemOverwrites OEM files without prompting
/nobackupDoes not back up files needed for uninstall
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows the redirection of installation log files
/integrate:pathIntegrates 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
/EREnables extended error reporting
/verboseEnables 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-kb922760-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 KB922760.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-kb922760-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

You must restart your system after you apply this security update.

This security update does not support HotPatching. For more information about HotPatching see Microsoft Knowledge Base Article 897341.

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%\$NTUninstallKB922760$\Spuninst folder.

Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts the computer after installation and force 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.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows 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 NameVersionDateTimeSizeFolder
Browseui.dll6.0.3790.59420-Sep-200600:001,057,280RTMGDR
Cdfview.dll6.0.3790.59420-Sep-200600:00147,968RTMGDR
Danim.dll6.3.1.14820-Sep-200600:00993,280RTMGDR
Digest.dll6.0.3790.59420-Sep-200600:0059,904RTMGDR
Dxtmsft.dll6.3.3790.59420-Sep-200600:00351,744RTMGDR
Dxtrans.dll6.3.3790.59420-Sep-200600:00205,312RTMGDR
Iepeers.dll6.0.3790.59420-Sep-200600:00238,080RTMGDR
Inseng.dll6.0.3790.59420-Sep-200600:0073,216RTMGDR
Jsproxy.dll6.0.3790.59420-Sep-200600:0014,848RTMGDR
Mshtml.dll6.0.3790.59420-Sep-200600:002,936,832RTMGDR
Mshtmled.dll6.0.3790.59420-Sep-200600:00454,144RTMGDR
Msrating.dll6.0.3790.59420-Sep-200600:00135,680RTMGDR
Mstime.dll6.0.3790.59420-Sep-200600:00504,832RTMGDR
Pngfilt.dll5.2.3790.59420-Sep-200600:0040,448RTMGDR
Shdocvw.dll6.0.3790.58804-Sep-200606:091,398,272RTMGDR
Shlwapi.dll6.0.3790.59420-Sep-200600:00287,744RTMGDR
Urlmon.dll6.0.3790.59420-Sep-200600:00528,384RTMGDR
Wininet.dll6.0.3790.59420-Sep-200600:00626,176RTMGDR
Browseui.dll6.0.3790.55023-Jun-200620:541,057,280RTMQFE
Cdfview.dll6.0.3790.59420-Sep-200600:26147,968RTMQFE
Danim.dll6.3.1.14820-Sep-200600:26993,280RTMQFE
Digest.dll6.0.3790.59420-Sep-200600:2659,904RTMQFE
Dxtmsft.dll6.3.3790.59420-Sep-200600:26352,256RTMQFE
Dxtrans.dll6.3.3790.59420-Sep-200600:26205,312RTMQFE
Iepeers.dll6.0.3790.59420-Sep-200600:26239,104RTMQFE
Inseng.dll6.0.3790.59420-Sep-200600:2673,216RTMQFE
Jsproxy.dll6.0.3790.59420-Sep-200600:2614,848RTMQFE
Mshtml.dll6.0.3790.59420-Sep-200600:262,938,368RTMQFE
Mshtmled.dll6.0.3790.59420-Sep-200600:26454,144RTMQFE
Msrating.dll6.0.3790.59420-Sep-200600:26135,680RTMQFE
Mstime.dll6.0.3790.59420-Sep-200600:26504,832RTMQFE
Pngfilt.dll5.2.3790.59420-Sep-200600:2640,448RTMQFE
Shdocvw.dll6.0.3790.58804-Sep-200606:141,399,296RTMQFE
Shlwapi.dll6.0.3790.59420-Sep-200600:26287,744RTMQFE
Urlmon.dll6.0.3790.59420-Sep-200600:26528,384RTMQFE
Wininet.dll6.0.3790.59420-Sep-200600:26630,784RTMQFE
Browseui.dll6.0.3790.279520-Sep-200600:301,036,800SP1GDR
Danim.dll6.3.1.14820-Sep-200600:301,058,304SP1GDR
Dxtmsft.dll6.3.3790.279520-Sep-200600:30363,008SP1GDR
Dxtrans.dll6.3.3790.279520-Sep-200600:30212,480SP1GDR
Iedw.exe5.2.3790.279519-Sep-200609:5817,920SP1GDR
Iepeers.dll6.0.3790.279520-Sep-200600:30253,952SP1GDR
Jsproxy.dll6.0.3790.279520-Sep-200600:3016,384SP1GDR
Mshtml.dll6.0.3790.279520-Sep-200600:313,152,384SP1GDR
Mstime.dll6.0.3790.279520-Sep-200600:31537,088SP1GDR
Pngfilt.dll5.2.3790.279520-Sep-200600:3142,496SP1GDR
Shdocvw.dll6.0.3790.278304-Sep-200606:271,513,984SP1GDR
Shlwapi.dll6.0.3790.279520-Sep-200600:31321,536SP1GDR
Urlmon.dll6.0.3790.279520-Sep-200600:31696,320SP1GDR
W03a2409.dll5.2.3790.279519-Sep-200609:574,096SP1GDR
Wininet.dll6.0.3790.279520-Sep-200600:31662,528SP1GDR
Browseui.dll6.0.3790.279520-Sep-200600:351,036,800SP1QFE
Danim.dll6.3.1.14820-Sep-200600:351,058,304SP1QFE
Dxtmsft.dll6.3.3790.279520-Sep-200600:35363,008SP1QFE
Dxtrans.dll6.3.3790.279520-Sep-200600:35212,480SP1QFE
Iedw.exe5.2.3790.279519-Sep-200610:0917,920SP1QFE
Iepeers.dll6.0.3790.279520-Sep-200600:35253,952SP1QFE
Jsproxy.dll6.0.3790.279520-Sep-200600:3516,384SP1QFE
Mshtml.dll6.0.3790.279520-Sep-200600:353,154,432SP1QFE
Mstime.dll6.0.3790.279520-Sep-200600:35537,088SP1QFE
Pngfilt.dll5.2.3790.279520-Sep-200600:3542,496SP1QFE
Shdocvw.dll6.0.3790.278320-Sep-200601:541,515,008SP1QFE
Shlwapi.dll6.0.3790.279520-Sep-200600:35321,536SP1QFE
Urlmon.dll6.0.3790.279520-Sep-200600:35696,832SP1QFE
W03a2409.dll5.2.3790.279519-Sep-200609:5427,136SP1QFE
Wininet.dll6.0.3790.279520-Sep-200600:35665,600SP1QFE

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 NameVersionDateTimeSizeCPUFolder
Browseui.dll6.0.3790.59420-Sep-200602:252,536,960IA-64RTMGDR
Cdfview.dll6.0.3790.59420-Sep-200602:25303,616IA-64RTMGDR
Digest.dll6.0.3790.59420-Sep-200602:25141,312IA-64RTMGDR
Dxtmsft.dll6.3.3790.59420-Sep-200602:25940,032IA-64RTMGDR
Dxtrans.dll6.3.3790.59420-Sep-200602:25585,728IA-64RTMGDR
Iepeers.dll6.0.3790.59420-Sep-200602:25674,816IA-64RTMGDR
Inseng.dll6.0.3790.59420-Sep-200602:25217,600IA-64RTMGDR
Jsproxy.dll6.0.3790.59420-Sep-200602:2536,864IA-64RTMGDR
Mshtml.dll6.0.3790.59420-Sep-200602:258,248,832IA-64RTMGDR
Mshtmled.dll6.0.3790.59420-Sep-200602:261,409,536IA-64RTMGDR
Msrating.dll6.0.3790.59420-Sep-200602:26387,584IA-64RTMGDR
Mstime.dll6.0.3790.59420-Sep-200602:261,666,560IA-64RTMGDR
Pngfilt.dll5.2.3790.59420-Sep-200602:26105,984IA-64RTMGDR
Shdocvw.dll6.0.3790.58820-Sep-200602:263,375,104IA-64RTMGDR
Shlwapi.dll6.0.3790.59420-Sep-200602:26740,352IA-64RTMGDR
Urlmon.dll6.0.3790.59420-Sep-200602:261,302,016IA-64RTMGDR
Wininet.dll6.0.3790.59420-Sep-200602:261,506,304IA-64RTMGDR
Wbrowseui.dll6.0.3790.59420-Sep-200602:261,057,280x86RTMGDR\WOW
Wcdfview.dll6.0.3790.59420-Sep-200602:26147,968x86RTMGDR\WOW
Wdanim.dll6.3.1.14820-Sep-200602:26993,280x86RTMGDR\WOW
Wdxtmsft.dll6.3.3790.59420-Sep-200602:26351,744x86RTMGDR\WOW
Wdxtrans.dll6.3.3790.59420-Sep-200602:26205,312x86RTMGDR\WOW
Wiepeers.dll6.0.3790.59420-Sep-200602:26238,080x86RTMGDR\WOW
Winseng.dll6.0.3790.59420-Sep-200602:2673,216x86RTMGDR\WOW
Wjsproxy.dll6.0.3790.59420-Sep-200602:2614,848x86RTMGDR\WOW
Wmshtml.dll6.0.3790.59420-Sep-200602:262,936,832x86RTMGDR\WOW
Wmshtmled.dll6.0.3790.59420-Sep-200602:26454,144x86RTMGDR\WOW
Wmsrating.dll6.0.3790.59420-Sep-200602:26135,680x86RTMGDR\WOW
Wmstime.dll6.0.3790.59420-Sep-200602:26504,832x86RTMGDR\WOW
Wpngfilt.dll5.2.3790.59420-Sep-200602:2640,448x86RTMGDR\WOW
Wshdocvw.dll6.0.3790.58820-Sep-200602:261,398,272x86RTMGDR\WOW
Wshlwapi.dll6.0.3790.59420-Sep-200602:26287,744x86RTMGDR\WOW
Wurlmon.dll6.0.3790.59420-Sep-200602:26528,384x86RTMGDR\WOW
Wwdigest.dll6.0.3790.59420-Sep-200602:2659,904x86RTMGDR\WOW
Wwininet.dll6.0.3790.59420-Sep-200602:26626,176x86RTMGDR\WOW
Browseui.dll6.0.3790.55020-Sep-200602:252,538,496IA-64RTMQFE
Cdfview.dll6.0.3790.59420-Sep-200602:25303,616IA-64RTMQFE
Digest.dll6.0.3790.59420-Sep-200602:25141,312IA-64RTMQFE
Dxtmsft.dll6.3.3790.59420-Sep-200602:25941,056IA-64RTMQFE
Dxtrans.dll6.3.3790.59420-Sep-200602:25586,752IA-64RTMQFE
Iepeers.dll6.0.3790.59420-Sep-200602:25678,912IA-64RTMQFE
Inseng.dll6.0.3790.59420-Sep-200602:25217,600IA-64RTMQFE
Jsproxy.dll6.0.3790.59420-Sep-200602:2536,864IA-64RTMQFE
Mshtml.dll6.0.3790.59420-Sep-200602:258,253,440IA-64RTMQFE
Mshtmled.dll6.0.3790.59420-Sep-200602:261,409,536IA-64RTMQFE
Msrating.dll6.0.3790.59420-Sep-200602:26387,584IA-64RTMQFE
Mstime.dll6.0.3790.59420-Sep-200602:261,666,560IA-64RTMQFE
Pngfilt.dll5.2.3790.59420-Sep-200602:26105,984IA-64RTMQFE
Shdocvw.dll6.0.3790.58820-Sep-200602:263,381,248IA-64RTMQFE
Shlwapi.dll6.0.3790.59420-Sep-200602:26740,352IA-64RTMQFE
Urlmon.dll6.0.3790.59420-Sep-200602:261,302,016IA-64RTMQFE
Wininet.dll6.0.3790.59420-Sep-200602:261,519,616IA-64RTMQFE
Wbrowseui.dll6.0.3790.55020-Sep-200602:261,057,280x86RTMQFE\WOW
Wcdfview.dll6.0.3790.59420-Sep-200602:26147,968x86RTMQFE\WOW
Wdanim.dll6.3.1.14820-Sep-200602:26993,280x86RTMQFE\WOW
Wdxtmsft.dll6.3.3790.59420-Sep-200602:26352,256x86RTMQFE\WOW
Wdxtrans.dll6.3.3790.59420-Sep-200602:26205,312x86RTMQFE\WOW
Wiepeers.dll6.0.3790.59420-Sep-200602:26239,104x86RTMQFE\WOW
Winseng.dll6.0.3790.59420-Sep-200602:2673,216x86RTMQFE\WOW
Wjsproxy.dll6.0.3790.59420-Sep-200602:2614,848x86RTMQFE\WOW
Wmshtml.dll6.0.3790.59420-Sep-200602:262,938,368x86RTMQFE\WOW
Wmshtmled.dll6.0.3790.59420-Sep-200602:26454,144x86RTMQFE\WOW
Wmsrating.dll6.0.3790.59420-Sep-200602:26135,680x86RTMQFE\WOW
Wmstime.dll6.0.3790.59420-Sep-200602:26504,832x86RTMQFE\WOW
Wpngfilt.dll5.2.3790.59420-Sep-200602:2640,448x86RTMQFE\WOW
Wshdocvw.dll6.0.3790.58820-Sep-200602:261,399,296x86RTMQFE\WOW
Wshlwapi.dll6.0.3790.59420-Sep-200602:26287,744x86RTMQFE\WOW
Wurlmon.dll6.0.3790.59420-Sep-200602:26528,384x86RTMQFE\WOW
Wwdigest.dll6.0.3790.59420-Sep-200602:2659,904x86RTMQFE\WOW
Wwininet.dll6.0.3790.59420-Sep-200602:26630,784x86RTMQFE\WOW
Browseui.dll6.0.3790.279520-Sep-200602:302,542,080IA-64SP1GDR
Dxtmsft.dll6.3.3790.279520-Sep-200602:311,009,152IA-64SP1GDR
Dxtrans.dll6.3.3790.279520-Sep-200602:31640,512IA-64SP1GDR
Iepeers.dll6.0.3790.279520-Sep-200602:31717,312IA-64SP1GDR
Jsproxy.dll6.0.3790.279520-Sep-200602:3145,568IA-64SP1GDR
Mshtml.dll6.0.3790.279520-Sep-200602:319,358,848IA-64SP1GDR
Mstime.dll6.0.3790.279520-Sep-200602:311,845,760IA-64SP1GDR
Pngfilt.dll5.2.3790.279520-Sep-200602:31116,736IA-64SP1GDR
Shdocvw.dll6.0.3790.278320-Sep-200602:313,677,696IA-64SP1GDR
Shlwapi.dll6.0.3790.279520-Sep-200602:31823,296IA-64SP1GDR
Urlmon.dll6.0.3790.279520-Sep-200602:311,613,312IA-64SP1GDR
W03a2409.dll5.2.3790.279520-Sep-200602:313,072IA-64SP1GDR
Wininet.dll6.0.3790.279520-Sep-200602:311,695,232IA-64SP1GDR
Wbrowseui.dll6.0.3790.279520-Sep-200602:311,036,800x86SP1GDR\WOW
Wdanim.dll6.3.1.14820-Sep-200602:311,058,304x86SP1GDR\WOW
Wdxtmsft.dll6.3.3790.279520-Sep-200602:31363,008x86SP1GDR\WOW
Wdxtrans.dll6.3.3790.279520-Sep-200602:31212,480x86SP1GDR\WOW
Wiedw.exe5.2.3790.279520-Sep-200602:3117,920x86SP1GDR\WOW
Wiepeers.dll6.0.3790.279520-Sep-200602:31253,952x86SP1GDR\WOW
Wjsproxy.dll6.0.3790.279520-Sep-200602:3116,384x86SP1GDR\WOW
Wmshtml.dll6.0.3790.279520-Sep-200602:313,152,384x86SP1GDR\WOW
Wmstime.dll6.0.3790.279520-Sep-200602:31537,088x86SP1GDR\WOW
Wpngfilt.dll5.2.3790.279520-Sep-200602:3142,496x86SP1GDR\WOW
Wshdocvw.dll6.0.3790.278320-Sep-200602:311,513,984x86SP1GDR\WOW
Wshlwapi.dll6.0.3790.279520-Sep-200602:31321,536x86SP1GDR\WOW
Wurlmon.dll6.0.3790.279520-Sep-200602:31696,320x86SP1GDR\WOW
Ww03a2409.dll5.2.3790.279520-Sep-200602:314,096x86SP1GDR\WOW
Wwininet.dll6.0.3790.279520-Sep-200602:31662,528x86SP1GDR\WOW
Browseui.dll6.0.3790.279520-Sep-200602:402,541,568IA-64SP1QFE
Dxtmsft.dll6.3.3790.279520-Sep-200602:401,009,152IA-64SP1QFE
Dxtrans.dll6.3.3790.279520-Sep-200602:40640,512IA-64SP1QFE
Iepeers.dll6.0.3790.279520-Sep-200602:40717,824IA-64SP1QFE
Jsproxy.dll6.0.3790.279520-Sep-200602:4045,568IA-64SP1QFE
Mshtml.dll6.0.3790.279520-Sep-200602:409,360,896IA-64SP1QFE
Mstime.dll6.0.3790.279520-Sep-200602:401,845,760IA-64SP1QFE
Pngfilt.dll5.2.3790.279520-Sep-200602:40116,736IA-64SP1QFE
Shdocvw.dll6.0.3790.278320-Sep-200602:403,678,720IA-64SP1QFE
Shlwapi.dll6.0.3790.279520-Sep-200602:40823,296IA-64SP1QFE
Urlmon.dll6.0.3790.279520-Sep-200602:401,614,336IA-64SP1QFE
W03a2409.dll5.2.3790.279520-Sep-200602:4026,112IA-64SP1QFE
Wininet.dll6.0.3790.279520-Sep-200602:401,700,864IA-64SP1QFE
Wbrowseui.dll6.0.3790.279520-Sep-200602:401,036,800x86SP1QFE\WOW
Wdanim.dll6.3.1.14820-Sep-200602:401,058,304x86SP1QFE\WOW
Wdxtmsft.dll6.3.3790.279520-Sep-200602:40363,008x86SP1QFE\WOW
Wdxtrans.dll6.3.3790.279520-Sep-200602:40212,480x86SP1QFE\WOW
Wiedw.exe5.2.3790.279520-Sep-200602:4017,920x86SP1QFE\WOW
Wiepeers.dll6.0.3790.279520-Sep-200602:40253,952x86SP1QFE\WOW
Wjsproxy.dll6.0.3790.279520-Sep-200602:4016,384x86SP1QFE\WOW
Wmshtml.dll6.0.3790.279520-Sep-200602:403,154,432x86SP1QFE\WOW
Wmstime.dll6.0.3790.279520-Sep-200602:40537,088x86SP1QFE\WOW
Wpngfilt.dll5.2.3790.279520-Sep-200602:4042,496x86SP1QFE\WOW
Wshdocvw.dll6.0.3790.278320-Sep-200602:401,515,008x86SP1QFE\WOW
Wshlwapi.dll6.0.3790.279520-Sep-200602:40321,536x86SP1QFE\WOW
Wurlmon.dll6.0.3790.279520-Sep-200602:40696,832x86SP1QFE\WOW
Ww03a2409.dll5.2.3790.279520-Sep-200602:4027,136x86SP1QFE\WOW
Wwininet.dll6.0.3790.279520-Sep-200602:40665,600x86SP1QFE\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 NameVersionDateTimeSizeCPUFolder
Browseui.dll6.0.3790.279520-Sep-200602:291,604,608x64SP1GDR
Danim.dll6.3.1.14820-Sep-200602:291,989,120x64SP1GDR
Dxtmsft.dll6.3.3790.279520-Sep-200602:29561,664x64SP1GDR
Dxtrans.dll6.3.3790.279520-Sep-200602:30332,288x64SP1GDR
Iepeers.dll6.0.3790.279520-Sep-200602:30369,664x64SP1GDR
Jsproxy.dll6.0.3790.279520-Sep-200602:3024,064x64SP1GDR
Mshtml.dll6.0.3790.279520-Sep-200602:305,993,472x64SP1GDR
Mstime.dll6.0.3790.279520-Sep-200602:30900,608x64SP1GDR
Pngfilt.dll5.2.3790.279520-Sep-200602:3064,000x64SP1GDR
Shdocvw.dll6.0.3790.278320-Sep-200602:302,436,096x64SP1GDR
Shlwapi.dll6.0.3790.279520-Sep-200602:30621,568x64SP1GDR
Urlmon.dll6.0.3790.279520-Sep-200602:301,083,904x64SP1GDR
W03a2409.dll5.2.3790.279520-Sep-200602:304,608x64SP1GDR
Wininet.dll6.0.3790.279520-Sep-200602:301,187,840x64SP1GDR
Wbrowseui.dll6.0.3790.279520-Sep-200602:301,036,800x86SP1GDR\WOW
Wdanim.dll6.3.1.14820-Sep-200602:301,058,304x86SP1GDR\WOW
Wdxtmsft.dll6.3.3790.279520-Sep-200602:30363,008x86SP1GDR\WOW
Wdxtrans.dll6.3.3790.279520-Sep-200602:30212,480x86SP1GDR\WOW
Wiedw.exe5.2.3790.279520-Sep-200602:3017,920x86SP1GDR\WOW
Wiepeers.dll6.0.3790.279520-Sep-200602:30253,952x86SP1GDR\WOW
Wjsproxy.dll6.0.3790.279520-Sep-200602:3016,384x86SP1GDR\WOW
Wmshtml.dll6.0.3790.279520-Sep-200602:303,152,384x86SP1GDR\WOW
Wmstime.dll6.0.3790.279520-Sep-200602:30537,088x86SP1GDR\WOW
Wpngfilt.dll5.2.3790.279520-Sep-200602:3042,496x86SP1GDR\WOW
Wshdocvw.dll6.0.3790.278320-Sep-200602:301,513,984x86SP1GDR\WOW
Wshlwapi.dll6.0.3790.279520-Sep-200602:30321,536x86SP1GDR\WOW
Wurlmon.dll6.0.3790.279520-Sep-200602:30696,320x86SP1GDR\WOW
Ww03a2409.dll5.2.3790.279520-Sep-200602:304,096x86SP1GDR\WOW
Wwininet.dll6.0.3790.279520-Sep-200602:30662,528x86SP1GDR\WOW
Browseui.dll6.0.3790.279520-Sep-200602:211,604,608x64SP1QFE
Danim.dll6.3.1.14820-Sep-200602:211,989,120x64SP1QFE
Dxtmsft.dll6.3.3790.279520-Sep-200602:21561,664x64SP1QFE
Dxtrans.dll6.3.3790.279520-Sep-200602:21332,288x64SP1QFE
Iepeers.dll6.0.3790.279520-Sep-200602:21370,176x64SP1QFE
Jsproxy.dll6.0.3790.279520-Sep-200602:2124,064x64SP1QFE
Mshtml.dll6.0.3790.279520-Sep-200602:215,995,008x64SP1QFE
Mstime.dll6.0.3790.279520-Sep-200602:22900,608x64SP1QFE
Pngfilt.dll5.2.3790.279520-Sep-200602:2264,000x64SP1QFE
Shdocvw.dll6.0.3790.278320-Sep-200602:222,437,120x64SP1QFE
Shlwapi.dll6.0.3790.279520-Sep-200602:22621,568x64SP1QFE
Urlmon.dll6.0.3790.279520-Sep-200602:221,083,904x64SP1QFE
W03a2409.dll5.2.3790.279520-Sep-200602:2227,648x64SP1QFE
Wininet.dll6.0.3790.279520-Sep-200602:221,189,888x64SP1QFE
Wbrowseui.dll6.0.3790.279520-Sep-200602:221,036,800x86SP1QFE\WOW
Wdanim.dll6.3.1.14820-Sep-200602:221,058,304x86SP1QFE\WOW
Wdxtmsft.dll6.3.3790.279520-Sep-200602:22363,008x86SP1QFE\WOW
Wdxtrans.dll6.3.3790.279520-Sep-200602:22212,480x86SP1QFE\WOW
Wiedw.exe5.2.3790.279520-Sep-200602:2217,920x86SP1QFE\WOW
Wiepeers.dll6.0.3790.279520-Sep-200602:22253,952x86SP1QFE\WOW
Wjsproxy.dll6.0.3790.279520-Sep-200602:2216,384x86SP1QFE\WOW
Wmshtml.dll6.0.3790.279520-Sep-200602:223,154,432x86SP1QFE\WOW
Wmstime.dll6.0.3790.279520-Sep-200602:22537,088x86SP1QFE\WOW
Wpngfilt.dll5.2.3790.279520-Sep-200602:2242,496x86SP1QFE\WOW
Wshdocvw.dll6.0.3790.278320-Sep-200602:221,515,008x86SP1QFE\WOW
Wshlwapi.dll6.0.3790.279520-Sep-200602:22321,536x86SP1QFE\WOW
Wurlmon.dll6.0.3790.279520-Sep-200602:22696,832x86SP1QFE\WOW
Ww03a2409.dll5.2.3790.279520-Sep-200602:2227,136x86SP1QFE\WOW
Wwininet.dll6.0.3790.279520-Sep-200602:22665,600x86SP1QFE\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 RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, 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.

  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, 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; 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; 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\KB922760\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 922760 security update into the Windows installation source files.

Windows XP Service Pack 2 (all versions) and Windows XP Professional x64 Edition

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

Note For Windows XP Professional x64 Edition, this security update is the same as the Windows Server 2003 x64 Edition security update.

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
SwitchDescription
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts the computer after installation and force 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.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/overwriteoemOverwrites OEM files without prompting
/nobackupDoes not back up files needed for uninstall
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows the redirection of installation log files
/integrate:pathIntegrates 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
/EREnables extended error reporting
/verboseEnables 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-kb922760-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 KB922760.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-kb922760-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

You must restart your system after you apply this security update.

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%\$NTUninstallKB922760$\Spuninst folder.

Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts the computer after installation and force 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.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows 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 Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:

File NameVersionDateTimeSizeFolder
Browseui.dll6.0.2900.299514-Sep-200608:391,022,976SP2GDR
Cdfview.dll6.0.2900.299514-Sep-200608:39151,040SP2GDR
Danim.dll6.3.1.14814-Sep-200608:391,054,208SP2GDR
Dxtmsft.dll6.3.2900.299514-Sep-200608:39357,888SP2GDR
Dxtrans.dll6.3.2900.299514-Sep-200608:39205,312SP2GDR
Extmgr.dll6.0.2900.299514-Sep-200608:3955,808SP2GDR
Iedw.exe5.1.2600.299513-Sep-200608:5218,432SP2GDR
Iepeers.dll6.0.2900.299514-Sep-200608:39251,392SP2GDR
Inseng.dll6.0.2900.299514-Sep-200608:3996,256SP2GDR
Jsproxy.dll6.0.2900.299514-Sep-200608:3916,384SP2GDR
Mshtml.dll6.0.2900.299514-Sep-200608:393,054,592SP2GDR
Mshtmled.dll6.0.2900.299514-Sep-200608:39448,512SP2GDR
Msrating.dll6.0.2900.299514-Sep-200608:39146,432SP2GDR
Mstime.dll6.0.2900.299514-Sep-200608:39532,480SP2GDR
Pngfilt.dll6.0.2900.299514-Sep-200608:3939,424SP2GDR
Shdocvw.dll6.0.2900.298704-Sep-200606:081,494,016SP2GDR
Shlwapi.dll6.0.2900.299514-Sep-200608:39474,112SP2GDR
Urlmon.dll6.0.2900.299514-Sep-200608:39613,888SP2GDR
Wininet.dll6.0.2900.299514-Sep-200608:39658,944SP2GDR
Xpsp3res.dll5.1.2600.299513-Sep-200608:44115,200SP2GDR
Browseui.dll6.0.2900.299514-Sep-200608:311,022,976SP2QFE
Cdfview.dll6.0.2900.299514-Sep-200608:31151,040SP2QFE
Danim.dll6.3.1.14814-Sep-200608:311,054,208SP2QFE
Dxtmsft.dll6.3.2900.299514-Sep-200608:31357,888SP2QFE
Dxtrans.dll6.3.2900.299514-Sep-200608:31205,312SP2QFE
Extmgr.dll6.0.2900.299514-Sep-200608:3155,808SP2QFE
Iedw.exe5.1.2600.299513-Sep-200609:1018,432SP2QFE
Iepeers.dll6.0.2900.299514-Sep-200608:31251,904SP2QFE
Inseng.dll6.0.2900.299514-Sep-200608:3196,256SP2QFE
Jsproxy.dll6.0.2900.299514-Sep-200608:3115,872SP2QFE
Mshtml.dll6.0.2900.299514-Sep-200608:313,058,688SP2QFE
Mshtmled.dll6.0.2900.299514-Sep-200608:31448,512SP2QFE
Msrating.dll6.0.2900.299514-Sep-200608:31146,432SP2QFE
Mstime.dll6.0.2900.299514-Sep-200608:31532,480SP2QFE
Pngfilt.dll6.0.2900.299514-Sep-200608:3139,424SP2QFE
Shdocvw.dll6.0.2900.298704-Sep-200606:121,497,088SP2QFE
Shlwapi.dll6.0.2900.299514-Sep-200608:31474,112SP2QFE
Urlmon.dll6.0.2900.299514-Sep-200608:31615,936SP2QFE
Wininet.dll6.0.2900.299514-Sep-200608:31664,576SP2QFE
Xpsp3res.dll5.1.2600.299513-Sep-200608:56210,944SP2QFE

Windows XP Professional x64:

File NameVersionDateTimeSizeCPUFolder
Browseui.dll6.0.3790.279520-Sep-200602:291,604,608x64SP1GDR
Danim.dll6.3.1.14820-Sep-200602:291,989,120x64SP1GDR
Dxtmsft.dll6.3.3790.279520-Sep-200602:29561,664x64SP1GDR
Dxtrans.dll6.3.3790.279520-Sep-200602:30332,288x64SP1GDR
Iepeers.dll6.0.3790.279520-Sep-200602:30369,664x64SP1GDR
Jsproxy.dll6.0.3790.279520-Sep-200602:3024,064x64SP1GDR
Mshtml.dll6.0.3790.279520-Sep-200602:305,993,472x64SP1GDR
Mstime.dll6.0.3790.279520-Sep-200602:30900,608x64SP1GDR
Pngfilt.dll5.2.3790.279520-Sep-200602:3064,000x64SP1GDR
Shdocvw.dll6.0.3790.278320-Sep-200602:302,436,096x64SP1GDR
Shlwapi.dll6.0.3790.279520-Sep-200602:30621,568x64SP1GDR
Urlmon.dll6.0.3790.279520-Sep-200602:301,083,904x64SP1GDR
W03a2409.dll5.2.3790.279520-Sep-200602:304,608x64SP1GDR
Wininet.dll6.0.3790.279520-Sep-200602:301,187,840x64SP1GDR
Wbrowseui.dll6.0.3790.279520-Sep-200602:301,036,800x86SP1GDR\WOW
Wdanim.dll6.3.1.14820-Sep-200602:301,058,304x86SP1GDR\WOW
Wdxtmsft.dll6.3.3790.279520-Sep-200602:30363,008x86SP1GDR\WOW
Wdxtrans.dll6.3.3790.279520-Sep-200602:30212,480x86SP1GDR\WOW
Wiedw.exe5.2.3790.279520-Sep-200602:3017,920x86SP1GDR\WOW
Wiepeers.dll6.0.3790.279520-Sep-200602:30253,952x86SP1GDR\WOW
Wjsproxy.dll6.0.3790.279520-Sep-200602:3016,384x86SP1GDR\WOW
Wmshtml.dll6.0.3790.279520-Sep-200602:303,152,384x86SP1GDR\WOW
Wmstime.dll6.0.3790.279520-Sep-200602:30537,088x86SP1GDR\WOW
Wpngfilt.dll5.2.3790.279520-Sep-200602:3042,496x86SP1GDR\WOW
Wshdocvw.dll6.0.3790.278320-Sep-200602:301,513,984x86SP1GDR\WOW
Wshlwapi.dll6.0.3790.279520-Sep-200602:30321,536x86SP1GDR\WOW
Wurlmon.dll6.0.3790.279520-Sep-200602:30696,320x86SP1GDR\WOW
Ww03a2409.dll5.2.3790.279520-Sep-200602:304,096x86SP1GDR\WOW
Wwininet.dll6.0.3790.279520-Sep-200602:30662,528x86SP1GDR\WOW
Browseui.dll6.0.3790.279520-Sep-200602:211,604,608x64SP1QFE
Danim.dll6.3.1.14820-Sep-200602:211,989,120x64SP1QFE
Dxtmsft.dll6.3.3790.279520-Sep-200602:21561,664x64SP1QFE
Dxtrans.dll6.3.3790.279520-Sep-200602:21332,288x64SP1QFE
Iepeers.dll6.0.3790.279520-Sep-200602:21370,176x64SP1QFE
Jsproxy.dll6.0.3790.279520-Sep-200602:2124,064x64SP1QFE
Mshtml.dll6.0.3790.279520-Sep-200602:215,995,008x64SP1QFE
Mstime.dll6.0.3790.279520-Sep-200602:22900,608x64SP1QFE
Pngfilt.dll5.2.3790.279520-Sep-200602:2264,000x64SP1QFE
Shdocvw.dll6.0.3790.278320-Sep-200602:222,437,120x64SP1QFE
Shlwapi.dll6.0.3790.279520-Sep-200602:22621,568x64SP1QFE
Urlmon.dll6.0.3790.279520-Sep-200602:221,083,904x64SP1QFE
W03a2409.dll5.2.3790.279520-Sep-200602:2227,648x64SP1QFE
Wininet.dll6.0.3790.279520-Sep-200602:221,189,888x64SP1QFE
Wbrowseui.dll6.0.3790.279520-Sep-200602:221,036,800x86SP1QFE\WOW
Wdanim.dll6.3.1.14820-Sep-200602:221,058,304x86SP1QFE\WOW
Wdxtmsft.dll6.3.3790.279520-Sep-200602:22363,008x86SP1QFE\WOW
Wdxtrans.dll6.3.3790.279520-Sep-200602:22212,480x86SP1QFE\WOW
Wiedw.exe5.2.3790.279520-Sep-200602:2217,920x86SP1QFE\WOW
Wiepeers.dll6.0.3790.279520-Sep-200602:22253,952x86SP1QFE\WOW
Wjsproxy.dll6.0.3790.279520-Sep-200602:2216,384x86SP1QFE\WOW
Wmshtml.dll6.0.3790.279520-Sep-200602:223,154,432x86SP1QFE\WOW
Wmstime.dll6.0.3790.279520-Sep-200602:22537,088x86SP1QFE\WOW
Wpngfilt.dll5.2.3790.279520-Sep-200602:2242,496x86SP1QFE\WOW
Wshdocvw.dll6.0.3790.278320-Sep-200602:221,515,008x86SP1QFE\WOW
Wshlwapi.dll6.0.3790.279520-Sep-200602:22321,536x86SP1QFE\WOW
Wurlmon.dll6.0.3790.279520-Sep-200602:22696,832x86SP1QFE\WOW
Ww03a2409.dll5.2.3790.279520-Sep-200602:2227,136x86SP1QFE\WOW
Wwininet.dll6.0.3790.279520-Sep-200602:22665,600x86SP1QFE\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 RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, 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.

  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 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\KB922760\Filelist

Windows XP Professional x64 Edition:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP2\KB922760\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 922760 security update into the Windows installation source files.

Internet Explorer 6 Service Pack 1 for Windows 2000 (all versions)

Prerequisites
To install the Internet Explorer 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).

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
SwitchDescription
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts the computer after installation and force 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.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/overwriteoemOverwrites OEM files without prompting
/nobackupDoes not back up files needed for uninstall
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows the redirection of installation log files
/extract[:path]Extracts files without starting the Setup program
/EREnables extended error reporting
/verboseEnables 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. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

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:

IE6.0sp1-KB922760-Windows-2000-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 KB922760-IE6SP1-20061018.120000.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:

IE6.0sp1-KB922760-Windows-2000-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

You must restart your system after you apply this security update.

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%\$NTUninstallKB922760-IE6SP1-20061018.120000$\Spuninst folder.

Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts the computer after installation and force 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.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows 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 2000 Service Pack 4 and Small Business Server 2000:

File NameVersionDateTimeSizeFolder
Browseui.dll6.0.2800.189516-Oct-200621:511,017,856RTMGDR
Cdfview.dll6.0.2800.189516-Oct-200621:51143,360RTMGDR
Danim.dll6.3.1.14814-Sep-200608:311,054,208RTMGDR
Dxtmsft.dll6.3.2800.157816-Oct-200620:30351,744RTMGDR
Dxtrans.dll6.3.2800.157816-Oct-200620:30192,512RTMGDR
Iepeers.dll6.0.2800.157816-Oct-200620:30236,032RTMGDR
Inseng.dll6.0.2800.157816-Oct-200620:3069,632RTMGDR
Jsproxy.dll6.0.2800.157816-Oct-200620:3112,288RTMGDR
Mshtml.dll6.0.2800.157816-Oct-200620:302,703,360RTMGDR
Msrating.dll6.0.2800.189516-Oct-200621:52132,096RTMGDR
Mstime.dll6.0.2800.157816-Oct-200620:30498,176RTMGDR
Pngfilt.dll6.0.2800.157816-Oct-200620:3034,816RTMGDR
Shdocvw.dll6.0.2800.189516-Oct-200621:511,340,416RTMGDR
Shlwapi.dll6.0.2800.189516-Oct-200621:51402,944RTMGDR
Urlmon.dll6.0.2800.157816-Oct-200620:31461,824RTMGDR
Wininet.dll6.0.2800.157816-Oct-200620:32575,488RTMGDR
Browseui.dll6.0.2800.189516-Oct-200621:511,017,856RTMQFE
Cdfview.dll6.0.2800.189516-Oct-200621:51143,360RTMQFE
Danim.dll6.3.1.14814-Sep-200608:311,054,208RTMQFE
Dxtmsft.dll6.3.2800.157916-Oct-200620:27351,744RTMQFE
Dxtrans.dll6.3.2800.157916-Oct-200620:26192,512RTMQFE
Iepeers.dll6.0.2800.157916-Oct-200620:27236,544RTMQFE
Inseng.dll6.0.2800.157916-Oct-200620:2769,632RTMQFE
Jsproxy.dll6.0.2800.157916-Oct-200620:2812,288RTMQFE
Mshtml.dll6.0.2800.157916-Oct-200620:262,710,528RTMQFE
Msrating.dll6.0.2800.189516-Oct-200621:52132,096RTMQFE
Mstime.dll6.0.2800.157916-Oct-200620:26498,176RTMQFE
Pngfilt.dll6.0.2800.157916-Oct-200620:2738,912RTMQFE
Shdocvw.dll6.0.2800.189516-Oct-200621:511,340,416RTMQFE
Shlwapi.dll6.0.2800.189516-Oct-200621:51402,944RTMQFE
Urlmon.dll6.0.2800.157916-Oct-200620:28463,872RTMQFE
Wininet.dll6.0.2800.157916-Oct-200620:28587,776RTMQFE

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 RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, 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.

  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\Internet Explorer 6\SP1\KB922760-IE6SP1-20061018.120000\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 922760 security update into the Windows installation source files.

Internet Explorer 5.01 Service Pack 4 on Windows 2000 (all versions)

Prerequisites
For Windows 2000, this security update requires Service Pack 4 (SP4). For Small Business Server 2000, this security update requires 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
SwitchDescription
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts the computer after installation and force 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.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/overwriteoemOverwrites OEM files without prompting
/nobackupDoes not back up files needed for uninstall
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows the redirection of installation log files
/extract[:path]Extracts files without starting the Setup program
/EREnables extended error reporting
/verboseEnables 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. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

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:

IE5.01sp4-KB922760-Windows2000sp4-x86-ENU.exe /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 KB922760-IE501SP4-20060918.104713.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:

IE5.01sp4-KB922760-Windows2000sp4-x86-ENU.exe /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

You must restart your system after you apply this security update.

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%\$NTUninstallKB922760-IE501SP4-20060918.104713$\Spuninst folder.

Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts the computer after installation and force 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.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows 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 2000 Service Pack 4 and Small Business Server 2000:

File NameVersionDateTimeSize
Browseui.dll5.0.3828.270027-Apr-200518:05792,848
Danim.dll6.1.9.72928-Oct-200506:191,134,352
Iepeers.dll5.0.3830.170018-Jun-200502:23100,112
Inseng.dll5.0.3828.270027-Apr-200518:0774,000
Jsproxy.dll5.0.3840.280028-Apr-200618:4513,584
Mshtml.dll5.0.3842.300030-Jun-200617:362,302,224
Msrating.dll5.0.3828.270027-Apr-200518:06149,776
Pngfilt.dll5.0.3828.270027-Apr-200518:0748,912
Shdocvw.dll5.0.3841.110011-May-200619:511,100,560
Shlwapi.dll5.0.3900.706825-Aug-200507:13284,432
Url.dll5.50.4952.270027-Apr-200518:3384,240
Urlmon.dll5.0.3844.300031-Aug-200604:28424,208
Wininet.dll5.0.3842.230023-Jun-200617:47451,344

Note This security update contains the same files as the security update included with Microsoft Security Bulletin MS06-042. In addition, this security update sets kill bits for the vulnerabilities that affect these Windows versions.

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\Internet Explorer 5.01\SP4\KB922760-IE501SP4-20060918.104713\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 922760 security update into the Windows installation source files.

Other Information

Acknowledgments

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

Obtaining Other Security Updates:

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

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:

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 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 (November 14, 2006): Bulletin published.
  • V1.1 (October 24, 2007): Bulletin revised to include MS06-065 as a bulletin that is replaced by this bulletin.

Built at 2014-04-16T02:39:51Z-07:00

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.