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

Microsoft Security Bulletin MS07-016 - Critical

Cumulative Security Update for Internet Explorer (928090)

Published: February 13, 2007 | Updated: February 21, 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 928090 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 928090.

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 when installed 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
  • Windows Internet Explorer 7 for Windows XP Service Pack 2 — Download the update
  • Windows Internet Explorer 7 for Windows XP Professional x64 Edition — Download the update
  • Windows Internet Explorer 7 for Windows Server 2003 Service Pack 1 — Download the update
  • Windows Internet Explorer 7 for Windows Server 2003 with SP1 for Itanium-based Systems — Download the update
  • Windows Internet Explorer 7 for Windows Server 2003 x64 Edition — Download the update

Non-Affected Components:

  • 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 two newly discovered, publicly and privately reported vulnerabilities. Each vulnerability is documented in its own subsection in the “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 when installed on Windows 2000 Service Pack 4Internet Explorer 6 for Windows XP Service Pack 2Internet Explorer 6 for Windows Server 2003 and Windows Server 2003 Service Pack 1Windows Internet Explorer 7 for Windows XP Service Pack 2Windows Internet Explorer 7 for Windows Server 2003 Service Pack 1
COM Object Instantiation Memory Corruption Vulnerability - CVE-2006-4697Remote Code ExecutionCriticalCriticalCriticalModerateImportantLow
COM Object Instantiation Memory Corruption Vulnerability - CVE-2007-0219Remote Code ExecutionCriticalCriticalCriticalModerateImportantLow
FTP Server Response Parsing Memory Corruption Vulnerability - CVE-2007-0217Remote Code ExecutionCriticalCriticalCriticalCriticalNoneNone
Aggregate Severity of All Vulnerabilities   Critical Critical Critical Critical Important Low

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

Why does this update address several reported security vulnerabilities? 
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers can install only this update.

What updates does this release replace? 
This security update replaces a prior security update. The 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 when installed on Windows 2000 Service Pack 4Internet Explorer 6 for Windows XP Service Pack 2Internet Explorer 6 for Windows Server 2003 and Windows Server 2003 Service Pack 1Windows Internet Explorer 7 for Windows XP Service Pack 2Windows Internet Explorer 7 for Windows Server 2003 Service Pack 1
MS06-072 ReplacedReplacedReplacedReplacedNot applicableNot applicable

What are the known issues that customers may experience when they install this security update? 
Microsoft Knowledge Base Article 928090 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 928090.

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, this update includes a defense-in-depth change to Internet Explorer. This defense-in-depth change helps mitigate the vulnerability addressed in Microsoft Security Bulletin MS06-045. The changes are also included in Windows Internet Explorer 7. Also included are security-related changes that were introduced in previous Internet Explorer bulletins.

Additionally, this update sets the kill bit for ActiveX controls previously addressed in Microsoft Security Bulletins:

  • The WMI Object Broker ActiveX control that is addressed in Microsoft Security Bulletin MS06-073: Vulnerability in Visual Studio 2005 Could Allow Remote Code Execution (925674):
    • 7F5B7F63-F06F-4331-8A26-339E03C0AE3D

Does this update contain any changes to functionality? 
Yes. Besides the changes that are listed in the "Vulnerability Details" section of this bulletin, this update includes the following changes in security functionality:

This security update includes changes to the Windows Internet Explorer 7 Phishing Filter. These changes where first introduced in the update discussed in Microsoft Knowledge Base Article 928089: “The computer may respond very slowly as the Phishing Filter evaluates Web page contents in Internet Explorer 7”

Note The update discussed in Microsoft Knowledge Base Article 928089 was made available to Windows Vista customers as a recommended update on Windows Update and Microsoft Update on January 30, 2007.

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

ProductMBSA 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

Note MBSA 1.2.1 does not support systems with Windows Internet Explorer 7 installed. MBSA 2.0 does support systems with Windows Internet Explorer 7 installed.

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

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.

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

For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about SUIT, visit the following Microsoft Web site. For more information about the limitations of SUIT, 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 (ITMU) 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 ITMU, 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.

COM Object Instantiation Memory Corruption Vulnerability - CVE-2006-4697:

A remote code execution vulnerability exists in the way Internet Explorer instantiates COM objects that are not intended to be instantiated in Internet Explorer. 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 COM Object Instantiation Memory Corruption Vulnerability - CVE-2006-4697:

  • 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, Web sites that accept or host user-provided content, or compromised Web sites and advertisement servers could contain specially crafted content that could exploit this vulnerability. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.
  • An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • By default, all supported versions of Microsoft Outlook and Microsoft Outlook Express open HTML e-mail messages in the Restricted sites zone. The Restricted sites zone helps reduce the number of successful attacks that exploit this vulnerability 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, 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 subsection of this vulnerability section for more information about Internet Explorer Enhanced Security Configuration.
  • COM Objects not intended to be instantiated in Internet Explorer are not included in the default allow-list for ActiveX controls in Windows Internet Explorer 7. Customers who are running Windows Internet Explorer 7 with default settings are therefore not at risk unless these COM Objects have been activated through the ActiveX opt-in feature in the Internet Zone. Customers who are upgrading to Windows Internet Explorer 7 and have enabled these COM objects in previous versions of Internet Explorer will have them enabled in Windows Internet Explorer 7. For more information on the ActiveX Opt-in feature and how to add ActiveX controls to the pre-approved list, see the product documentation.
  • Windows Internet Explorer 7 in Windows Vista is not affected by this vulnerability.

Workarounds for COM Object Instantiation Memory Corruption Vulnerability - CVE-2006-4697:

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

  • 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 this vulnerability 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 this vulnerability 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.

  • Prevent COM objects from running in Internet Explorer

    You can disable attempts to instantiate a COM object 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 {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}, 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\{ XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX }]
    "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.

    The Class Identifiers and corresponding files where the COM objects are contained are documented under “What does the update do?” in the “FAQ for COM Object Instantiation Memory Corruption Vulnerability - CVE-2006-4697” section.

    Impact of Workaround: There is no impact as long as the COM object is not intended to be used in Internet Explorer.

FAQ for COM Object Instantiation Memory Corruption Vulnerability - CVE-2006-4697:

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 tries to instantiate certain COM objects as ActiveX controls, the COM objects may corrupt the system state 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 that is designed to exploit this vulnerability 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 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 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 this vulnerability.

I am running Windows Internet Explorer 7. Does this mitigate this vulnerability? 
Yes. Customers who are running Windows Internet Explorer 7 with default settings, are not at risk unless these COM Objects have been activated through the ActiveX opt-in feature in the Internet Zone. Customers who are upgrading to Windows Internet Explorer 7 and have enabled these COM objects in previous versions of Internet Explorer will have them enabled in Windows Internet Explorer 7. For more information on the ActiveX Opt-in feature and how to add ActiveX controls to the pre-approved list, see the product documentation.

Windows Internet Explorer 7 in Windows Vista is not affected by this vulnerability.

What is the ActiveX opt-in feature in Windows Internet Explorer 7? 
Windows Internet Explorer 7 includes an ActiveX opt-in feature, which means that nearly all pre-installed ActiveX controls are off by default. Users are prompted by the Information Bar before they can instantiate a previously installed ActiveX control that has not yet been used on the Internet. This enables a user to permit or deny access on a control-by-control basis. For more information about this and other new features, see the Windows Internet Explorer 7 features page.

I am running Internet Explorer on Windows Server 2003. Does this mitigate this vulnerability? 
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. See the next FAQ in this section for more information about Internet Explorer Enhanced Security Configuration.

What is 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 administrator downloading and running malicious Web content on a server. Internet Explorer Enhanced Security Configuration reduces this threat by modifying numerous security-related settings, including Security and Advanced tab settings in Internet Options. Some of the key modifications include:

  • Security level for the Internet zone is set to High. This setting disables scripts, ActiveX components, Microsoft virtual machine (Microsoft VM) HTML content, 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, please consult the Managing Internet Explorer Enhanced Security Configuration guide, which can be found at the following Web site.

What does the update do? 
Because not all COM objects are designed to be accessed through Internet Explorer, this update sets the kill bit for a list of Class Identifiers (CLSIDs) for COM objects that have been found to exhibit similar behavior to the COM Object Instantiation Memory Corruption Vulnerability that is addressed in Microsoft Security Bulletin MS05-054. To help protect customers, this update prevents these CLSIDs from being instantiated in Internet Explorer. For more information about kill bits, see Microsoft Knowledge Base Article 240797.

The Class Identifiers and corresponding files where the COM objects are contained are as follows:

Class IdentifierFile
DA56F851-D3C5-11D3-844C-00C04F7A06E5Imjpcksid.dll
6E3197A3-BBC3-11D4-84C0-00C04F7A06E5Imjpskdic.dll

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CVE-2006-4697.

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.

COM Object Instantiation Memory Corruption Vulnerability - CVE-2007-0219:

A remote code execution vulnerability exists in the way Internet Explorer instantiates COM objects that are not intended to be instantiated in Internet Explorer. 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 COM Object Instantiation Memory Corruption Vulnerability - CVE-2007-0219:

  • 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, Web sites that accept or host user-provided content or compromised Web sites and advertisement servers could contain specially crafted content that could exploit this vulnerability. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.
  • An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • By default, all supported versions of Microsoft Outlook and Microsoft Outlook Express open HTML e-mail messages in the Restricted sites zone. The Restricted sites zone helps reduce the number of successful attacks that exploit this vulnerability 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, 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 subsection of this vulnerability section for more information about Internet Explorer Enhanced Security Configuration.
  • COM Objects not intended to be instantiated in Internet Explorer are not included in the default allow-list for ActiveX controls in Windows Internet Explorer 7. Customers who are running Windows Internet Explorer 7 with default settings, are therefore not at risk unless these COM Objects have been activated through the ActiveX opt-in feature in the Internet Zone. Customers who are upgrading to Windows Internet Explorer 7 and have enabled these COM objects in previous versions of Internet Explorer will have them enabled in Windows Internet Explorer 7. For more information on the ActiveX Opt-in feature and how to add ActiveX controls to the pre-approved list, see the product documentation.
  • Windows Internet Explorer 7 in Windows Vista is not affected by this vulnerability.

Workarounds for COM Object Instantiation Memory Corruption Vulnerability - CVE-2007-0219:

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

  • 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 this vulnerability 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 this vulnerability 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.

  • Prevent COM objects from running in Internet Explorer

    You can disable attempts to instantiate a COM object 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 {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}, 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\{ XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX }]
    "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.

    The Class Identifiers and corresponding files where the COM objects are contained are documented under “What does the update do?” in the “FAQ for COM Object Instantiation Memory Corruption Vulnerability - CVE-2006-4697” section.

    Impact of Workaround: There is no impact as long as the COM object is not intended to be used in Internet Explorer.

FAQ for COM Object Instantiation Memory Corruption Vulnerability - CVE-2007-0219:

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 tries to instantiate certain COM objects as ActiveX controls, the COM objects may corrupt the system state 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 that is designed to exploit this vulnerability 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 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 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 this vulnerability.

I am running Windows Internet Explorer 7. Does this mitigate this vulnerability? 
Yes. Customers who are running Windows Internet Explorer 7 with default settings, are not at risk unless these COM Objects have been activated through the ActiveX opt-in feature in the Internet Zone. Customers who are upgrading to Windows Internet Explorer 7 and have enabled these COM objects in previous versions of Internet Explorer will have them enabled in Windows Internet Explorer 7. For more information on the ActiveX Opt-in feature and how to add ActiveX controls to the pre-approved list, see the product documentation.

Windows Internet Explorer 7 in Windows Vista is not affected by this vulnerability.

What is the ActiveX opt-in feature in Windows Internet Explorer 7? 
Windows Internet Explorer 7 includes an ActiveX opt-in feature, which means that nearly all pre-installed ActiveX controls are off by default. Users are prompted by the Information Bar before they can instantiate a previously installed ActiveX control that has not yet been used on the Internet. This enables a user to permit or deny access on a control-by-control basis. For more information about this and other new features, see the Windows Internet Explorer 7 features page.

I am running Internet Explorer on Windows Server 2003. Does this mitigate this vulnerability? 
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. See the next FAQ in this section for more information about Internet Explorer Enhanced Security Configuration.

What is 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 administrator downloading and running malicious Web content on a server. Internet Explorer Enhanced Security Configuration reduces this threat by modifying numerous security-related settings, including Security and Advanced tab settings in Internet Options. Some of the key modifications include:

  • Security level for the Internet zone is set to High. This setting disables scripts, ActiveX components, Microsoft virtual machine (Microsoft VM) HTML content, 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, please consult the Managing Internet Explorer Enhanced Security Configuration guide, which can be found at the following Web site.

What does the update do? 
Because not all COM objects are designed to be accessed through Internet Explorer, this update sets the kill bit for a list of Class Identifiers (CLSIDs) for COM objects that have been found to exhibit similar behavior to the COM Object Instantiation Memory Corruption Vulnerability that is addressed in Microsoft Security Bulletin MS05-054. To help protect customers, this update prevents these CLSIDs from being instantiated in Internet Explorer. For more information about kill bits, see Microsoft Knowledge Base Article 240797.

The Class Identifiers and corresponding files where the COM objects are contained are as follows:

Class IdentifierFile
75C11604-5C51-48B2-B786-DF5E51D10EC9Msb1fren.dll
8422DAE3-9929-11CF-B8D3-004033373DA8Htmlmm.ocx
8422DAE7-9929-11CF-B8D3-004033373DA8Htmlmm.ocx
261F6572-578B-40A7-B72E-61B7261D9F0CBlnmgrps.dll
E56CCB42-598C-462D-9AD8-4FD5B4498C5DBlnmgrps.dll

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.

FTP Server Response Parsing Memory Corruption Vulnerability - CVE-2007-0217:

A remote code execution vulnerability exists in the way Internet Explorer interprets certain responses from FTP servers. An attacker could exploit the vulnerability by sending specially crafted FTP responses in an FTP session to the FTP client included in Internet Explorer. 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.

Mitigating Factors for FTP Server Response Parsing Memory Corruption Vulnerability - CVE-2007-0217:

  • In a Web-based attack scenario, an attacker would have to host an FTP server that would return these specially crafted FTP server responses to exploit this vulnerability. An attacker would have no way to force users to visit the site with the FTP server. Instead, an attacker would have to persuade them to visit the site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the attacker's site.
  • An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • By default, all supported versions of Microsoft Outlook and Microsoft Outlook Express open HTML e-mail messages in the Restricted sites zone. The Restricted sites zone helps reduce attacks that could try to exploit this vulnerability 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.

    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 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 subsection of this vulnerability section for more information about Internet Explorer Enhanced Security Configuration.

Workarounds for FTP Server Response Parsing Memory Corruption Vulnerability - CVE-2007-0217:

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.

  • 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 FTP Server Response Parsing Memory Corruption Vulnerability - CVE-2007-0217:

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

What causes the vulnerability? 
When Internet Explorer handles specially crafted FTP server responses 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 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? 
In a Web-based attack scenario, an attacker would have to host an FTP server that is used to attempt to exploit this vulnerability. An attacker would have no way to force users to visit an FTP server. Instead, an attacker would have to persuade them to visit the FTP server site, typically by getting them to click a link on a Web page, in an e-mail message, or in an Instant Messenger request that takes users to the attacker's Web site.

What systems are primarily at risk from the vulnerability? 
This vulnerability requires that a user is logged on and visits an FTP server using the FTP Client included in Internet Explorer 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 this vulnerability? 
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. See the next FAQ in this section for more information about Internet Explorer Enhanced Security Configuration.

What is 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 administrator downloading and running malicious Web content on a server. Internet Explorer Enhanced Security Configuration reduces this threat by modifying numerous security-related settings, including Security and Advanced tab settings in Internet Options. Some of the key modifications include:

  • Security level for the Internet zone is set to High. This setting disables scripts, ActiveX components, Microsoft virtual machine (Microsoft VM) HTML content, 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, please consult the Managing Internet Explorer Enhanced Security Configuration guide, which can be found at the following Web site.

What does the update do? 
The update removes the vulnerability by modifying the way Internet Explorer handles FTP server responses.

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 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
/help Displays the command-line options
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed
/forcerestart Restarts the computer after installation and 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.
/promptrestart Display a dialog box prompting the local user to allow a restart
Special Options
/overwriteoem Overwrites OEM files without prompting
/nobackup Does not back up files needed for uninstall
/forceappsclose Forces other programs to close when the computer shuts down
/log:path Allows the redirection of installation log files
/extract[:path] Extracts files without starting the Setup program
/ER Enables extended error reporting
/verbose Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. 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 one of the following commands at a command prompt for Windows 2000 Service Pack 4.

Internet Explorer 5.01 Service Pack 4:

IE5.01sp4-KB928090-Windows2000sp4-x86-enu /quiet

Internet Explorer 6.0 Service Pack 1:

IE6.0sp1-KB928090-Windows2000-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 KB928090-IE501SP4-20070125.120000.log or KB928090-IE6SP1-20070125.120000.log files respectively for any failure messages when they use this switch.

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

Internet Explorer 5.01 Service Pack 4:

IE5.01sp4-KB928090-Windows2000sp4-x86-enu /norestart

Internet Explorer 6.0 Service Pack 1:

IE6.0sp1-KB928090-Windows2000-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%\$NTUninstallKB928090-IE501SP4-20070125.120000$\Spuninst and %Windir%\$NTUninstallKB928090-IE6SP1-20070125.120000$\Spuninst folders respectively.

Supported Spuninst.exe Switches
SwitchDescription
/help Displays the command-line options
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed
/forcerestart Restarts the computer after installation and 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.
/promptrestart Display a dialog box prompting the local user to allow a restart
Special Options
/forceappsclose Forces other programs to close when the computer shuts down
/log:path Allows the redirection of installation log files

File Information

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

Internet Explorer 5.01 Service Pack 4 on Windows 2000 Service Pack 4 and on Small Business Server 2000:

File NameVersionDateTimeSize
Browseui.dll5.0.3849.50005-Jan-200722:19792,336
Danim.dll6.1.9.72906-Dec-200619:581,134,352
Iepeers.dll5.0.3849.50005-Jan-200722:22100,112
Inseng.dll5.0.3849.50005-Jan-200722:2374,000
Jsproxy.dll5.0.3849.50005-Jan-200722:2213,584
Mshtml.dll5.0.3849.50005-Jan-200722:222,303,248
Msrating.dll5.0.3849.50005-Jan-200722:21149,776
Pngfilt.dll5.0.3849.50005-Jan-200722:2248,912
Shdocvw.dll5.0.3849.50005-Jan-200722:191,104,656
Shlwapi.dll5.0.3900.712406-Jan-200700:17284,432
Url.dll5.50.4972.110011-Dec-200616:3284,240
Urlmon.dll5.0.3849.250025-Jan-200723:26425,232
Wininet.dll5.0.3849.50005-Jan-200722:22451,344

Internet Explorer 6 Service Pack 1 on Windows 2000 Service Pack 4 and on Small Business Server 2000:

File NameVersionDateTimeSizeFolder
Browseui.dll6.0.2800.190202-Jan-200717:331,017,856RTMGDR
Cdfview.dll6.0.2800.190202-Jan-200717:34143,360RTMGDR
Danim.dll6.3.1.14812-Dec-200621:551,054,208RTMGDR
Dxtmsft.dll6.3.2800.158902-Jan-200718:16351,744RTMGDR
Dxtrans.dll6.3.2800.158902-Jan-200718:16192,512RTMGDR
Iepeers.dll6.0.2800.158902-Jan-200718:16236,032RTMGDR
Inseng.dll6.0.2800.158902-Jan-200717:5169,632RTMGDR
Jsproxy.dll6.0.2800.158902-Jan-200717:5212,288RTMGDR
Mshtml.dll6.0.2800.158902-Jan-200718:162,704,896RTMGDR
Msrating.dll6.0.2800.190202-Jan-200717:34132,096RTMGDR
Mstime.dll6.0.2800.158902-Jan-200718:16498,176RTMGDR
Pngfilt.dll6.0.2800.158902-Jan-200718:1634,816RTMGDR
Shdocvw.dll6.0.2800.190202-Jan-200717:331,340,416RTMGDR
Shlwapi.dll6.0.2800.190202-Jan-200717:33402,944RTMGDR
Urlmon.dll6.0.2800.159125-Jan-200717:52462,336RTMGDR
Wininet.dll6.0.2800.158902-Jan-200717:52575,488RTMGDR
Browseui.dll6.0.2800.190202-Jan-200717:331,017,856RTMQFE
Cdfview.dll6.0.2800.190202-Jan-200717:33143,360RTMQFE
Danim.dll6.3.1.14812-Dec-200621:551,054,208RTMQFE
Dxtmsft.dll6.3.2800.159002-Jan-200718:18351,744RTMQFE
Dxtrans.dll6.3.2800.159002-Jan-200718:18192,512RTMQFE
Iepeers.dll6.0.2800.159002-Jan-200718:18236,544RTMQFE
Inseng.dll6.0.2800.159002-Jan-200717:4569,632RTMQFE
Jsproxy.dll6.0.2800.159002-Jan-200717:4512,288RTMQFE
Mshtml.dll6.0.2800.159002-Jan-200718:182,711,552RTMQFE
Msrating.dll6.0.2800.190202-Jan-200717:34132,096RTMQFE
Mstime.dll6.0.2800.159002-Jan-200718:18498,176RTMQFE
Pngfilt.dll6.0.2800.159002-Jan-200718:1838,912RTMQFE
Shdocvw.dll6.0.2800.190202-Jan-200717:331,340,416RTMQFE
Shlwapi.dll6.0.2800.190202-Jan-200717:33402,944RTMQFE
Urlmon.dll6.0.2800.159225-Jan-200717:48464,384RTMQFE
Wininet.dll6.0.2800.159002-Jan-200717:45587,776RTMQFE

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 one of the following registry keys.

Internet Explorer 5.01 Service Pack 4 on Windows 2000 Service Pack 4 and on Small Business Server 2000:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Internet Explorer 5.01\SP4\KB928090-IE501SP4-20070125.120000\Filelist

Internet Explorer 6 Service Pack 1 on Windows 2000 Service Pack 4 and on Small Business Server 2000:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Internet Explorer 6\SP1\KB928090-IE6SP1-20070125.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 928090 security update into the Windows installation source files.

Windows XP (all versions)

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
/help Displays the command-line options
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed
/forcerestart Restarts the computer after installation and 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.
/promptrestart Display a dialog box prompting the local user to allow a restart
Special Options
/overwriteoem Overwrites OEM files without prompting
/nobackup Does not back up files needed for uninstall
/forceappsclose Forces other programs to close when the computer shuts down
/log:path Allows the redirection of installation log files
/integrate:path Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path] Extracts files without starting the Setup program
/ER Enables extended error reporting
/verbose Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

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

Deployment Information

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

Internet Explorer 6 for Windows XP Service Pack 2:

Windowsxp-kb928090-x86-enu /quiet

Internet Explorer 7 for Windows XP Service Pack 2:

IE7-KB928090-WindowsXP-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 KB928090.log or KB928090-IE7.log file for any failure messages when they use this switch.

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

Internet Explorer 6 for Windows XP Service Pack 2:

Windowsxp-kb928090-x86-enu /norestart

Internet Explorer 7 for Windows XP Service Pack 2:

IE7-KB928090-WindowsXP-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%\$NTUninstallKB928090$\Spuninst and %Windir%\ie7updates\KB928090-IE7\spuninst folders.

Supported Spuninst.exe Switches
SwitchDescription
/help Displays the command-line options
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed
/forcerestart Restarts the computer after installation and 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.
/promptrestart Display a dialog box prompting the local user to allow a restart
Special Options
/forceappsclose Forces other programs to close when the computer shuts down
/log:path Allows the redirection of installation log files

File Information

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

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

File NameVersionDateTimeSizeFolder
Browseui.dll6.0.2900.305904-Jan-200713:361,023,488SP2GDR
Cdfview.dll6.0.2900.305904-Jan-200713:36151,040SP2GDR
Danim.dll6.3.1.14804-Jan-200713:361,054,208SP2GDR
Dxtmsft.dll6.3.2900.305904-Jan-200713:36357,888SP2GDR
Dxtrans.dll6.3.2900.305904-Jan-200713:36205,312SP2GDR
Extmgr.dll6.0.2900.305904-Jan-200713:3655,808SP2GDR
Iedw.exe5.1.2600.305904-Jan-200710:3618,432SP2GDR
Iepeers.dll6.0.2900.305904-Jan-200713:36251,392SP2GDR
Inseng.dll6.0.2900.305904-Jan-200713:3696,256SP2GDR
Jsproxy.dll6.0.2900.305904-Jan-200713:3616,384SP2GDR
Mshtml.dll6.0.2900.305904-Jan-200713:363,056,640SP2GDR
Mshtmled.dll6.0.2900.305904-Jan-200713:36448,512SP2GDR
Msrating.dll6.0.2900.305904-Jan-200713:36146,432SP2GDR
Mstime.dll6.0.2900.305904-Jan-200713:36532,480SP2GDR
Pngfilt.dll6.0.2900.305904-Jan-200713:3639,424SP2GDR
Shdocvw.dll6.0.2900.305904-Jan-200713:371,494,528SP2GDR
Shlwapi.dll6.0.2900.305904-Jan-200713:37474,112SP2GDR
Urlmon.dll6.0.2900.307225-Jan-200712:48615,424SP2GDR
Wininet.dll6.0.2900.305904-Jan-200713:37658,944SP2GDR
Xpsp3res.dll5.1.2600.305904-Jan-200710:25115,200SP2GDR
Browseui.dll6.0.2900.305904-Jan-200714:051,022,976SP2QFE
Cdfview.dll6.0.2900.305904-Jan-200714:05151,040SP2QFE
Danim.dll6.3.1.14804-Jan-200714:051,054,208SP2QFE
Dxtmsft.dll6.3.2900.305904-Jan-200714:05357,888SP2QFE
Dxtrans.dll6.3.2900.305904-Jan-200714:05205,312SP2QFE
Extmgr.dll6.0.2900.305904-Jan-200714:0555,808SP2QFE
Iedw.exe5.1.2600.305904-Jan-200711:0318,432SP2QFE
Iepeers.dll6.0.2900.305904-Jan-200714:05251,904SP2QFE
Inseng.dll6.0.2900.305904-Jan-200714:0596,256SP2QFE
Jsproxy.dll6.0.2900.305904-Jan-200714:0516,384SP2QFE
Mshtml.dll6.0.2900.305904-Jan-200714:053,062,272SP2QFE
Mshtmled.dll6.0.2900.305904-Jan-200714:05449,024SP2QFE
Msrating.dll6.0.2900.305904-Jan-200714:05146,432SP2QFE
Mstime.dll6.0.2900.305904-Jan-200714:05532,480SP2QFE
Pngfilt.dll6.0.2900.305904-Jan-200714:0539,424SP2QFE
Shdocvw.dll6.0.2900.305904-Jan-200714:051,498,112SP2QFE
Shlwapi.dll6.0.2900.305904-Jan-200714:05474,112SP2QFE
Urlmon.dll6.0.2900.307225-Jan-200712:24616,960SP2QFE
Wininet.dll6.0.2900.305904-Jan-200714:05665,088SP2QFE
Xpsp3res.dll5.1.2600.305904-Jan-200710:50248,320SP2QFE

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

File NameVersionDateTimeSize
Advpack.dll7.0.6000.1641409-Jan-200703:00124,928
Corpol.dll7.0.6000.1641409-Jan-200703:0117,408
Extmgr.dll7.0.6000.1641412-Jan-200717:27132,608
Ie4uinit.exe7.0.6000.1641409-Jan-200702:0856,832
Ieakeng.dll7.0.6000.1641409-Jan-200703:02153,088
Ieaksie.dll7.0.6000.1641409-Jan-200703:02230,400
Ieakui.dll7.0.6000.1641409-Jan-200703:02161,792
Ieapfltr.dll7.0.5825.009-Jan-200703:02383,488
Iedkcs32.dll17.0.6000.1641409-Jan-200703:02384,000
Ieframe.dll7.0.6000.1641412-Jan-200717:276,054,400
Ieframe.dll.mui7.0.6000.1641409-Jan-200703:07991,232
Iernonce.dll7.0.6000.1641409-Jan-200703:0244,544
Iertutil.dll7.0.6000.1641409-Jan-200703:02266,752
Ieudinit.exe7.0.6000.1641409-Jan-200702:0813,824
Iexplore.exe7.0.6000.1641409-Jan-200702:08623,616
Inetcpl.cpl7.0.6000.1641409-Jan-200703:021,823,744
Jsproxy.dll7.0.6000.1641412-Jan-200717:2727,136
Msfeeds.dll7.0.6000.1641412-Jan-200717:27458,752
Msfeedsbs.dll7.0.6000.1641412-Jan-200717:2751,712
Mshtml.dll7.0.6000.1641412-Jan-200717:273,580,416
Mshtmled.dll7.0.6000.1641412-Jan-200717:27477,696
Msrating.dll7.0.6000.1641409-Jan-200703:03193,024
Mstime.dll7.0.6000.1641412-Jan-200717:27670,720
Occache.dll7.0.6000.1641409-Jan-200703:04102,400
Url.dll7.0.6000.1641409-Jan-200703:04105,984
Urlmon.dll7.0.6000.1641412-Jan-200717:271,149,952
Webcheck.dll7.0.6000.1641412-Jan-200717:27232,960
Wininet.dll7.0.6000.1641412-Jan-200717:27822,784

Internet Explorer 6 for Windows XP Professional x64:

File NameVersionDateTimeSizeCPUFolder
Browseui.dll6.0.3790.285825-Jan-200719:371,605,120X64SP1GDR
Danim.dll6.3.1.14825-Jan-200719:371,989,120X64SP1GDR
Dxtmsft.dll6.3.3790.285825-Jan-200719:37561,664X64SP1GDR
Dxtrans.dll6.3.3790.285825-Jan-200719:37332,288X64SP1GDR
Iepeers.dll6.0.3790.285825-Jan-200719:37369,664X64SP1GDR
Jsproxy.dll6.0.3790.285825-Jan-200719:3724,064X64SP1GDR
Mshtml.dll6.0.3790.285825-Jan-200719:375,996,544X64SP1GDR
Mstime.dll6.0.3790.285825-Jan-200719:37900,608X64SP1GDR
Pngfilt.dll5.2.3790.285825-Jan-200719:3764,000X64SP1GDR
Shdocvw.dll6.0.3790.285825-Jan-200719:372,437,632X64SP1GDR
Shlwapi.dll6.0.3790.285825-Jan-200719:37621,568X64SP1GDR
Urlmon.dll6.0.3790.286925-Jan-200719:371,084,928X64SP1GDR
W03a2409.dll5.2.3790.284825-Jan-200719:374,608X64SP1GDR
Wininet.dll6.0.3790.285825-Jan-200719:371,187,840X64SP1GDR
Wbrowseui.dll6.0.3790.285825-Jan-200719:371,036,800x86SP1GDR\WOW
Wdanim.dll6.3.1.14825-Jan-200719:371,058,304x86SP1GDR\WOW
Wdxtmsft.dll6.3.3790.285825-Jan-200719:37363,008x86SP1GDR\WOW
Wdxtrans.dll6.3.3790.285825-Jan-200719:37212,480x86SP1GDR\WOW
Wiedw.exe5.2.3790.285825-Jan-200719:3717,920x86SP1GDR\WOW
Wiepeers.dll6.0.3790.285825-Jan-200719:37253,952x86SP1GDR\WOW
Wjsproxy.dll6.0.3790.285825-Jan-200719:3716,384x86SP1GDR\WOW
Wmshtml.dll6.0.3790.285825-Jan-200719:373,155,456x86SP1GDR\WOW
Wmstime.dll6.0.3790.285825-Jan-200719:37537,088x86SP1GDR\WOW
Wpngfilt.dll5.2.3790.285825-Jan-200719:3742,496x86SP1GDR\WOW
Wshdocvw.dll6.0.3790.285825-Jan-200719:371,514,496x86SP1GDR\WOW
Wshlwapi.dll6.0.3790.285825-Jan-200719:37321,536x86SP1GDR\WOW
Wurlmon.dll6.0.3790.286925-Jan-200719:37697,344x86SP1GDR\WOW
Ww03a2409.dll5.2.3790.284825-Jan-200719:374,096x86SP1GDR\WOW
Wwininet.dll6.0.3790.285825-Jan-200719:37662,528x86SP1GDR\WOW
Browseui.dll6.0.3790.285825-Jan-200719:311,605,120X64SP1QFE
Danim.dll6.3.1.14825-Jan-200719:311,989,120X64SP1QFE
Dxtmsft.dll6.3.3790.285825-Jan-200719:31561,664X64SP1QFE
Dxtrans.dll6.3.3790.285825-Jan-200719:31332,288X64SP1QFE
Iepeers.dll6.0.3790.285825-Jan-200719:31370,176X64SP1QFE
Jsproxy.dll6.0.3790.285825-Jan-200719:3124,064X64SP1QFE
Mshtml.dll6.0.3790.285825-Jan-200719:315,999,616X64SP1QFE
Mstime.dll6.0.3790.285825-Jan-200719:31900,608X64SP1QFE
Pngfilt.dll5.2.3790.285825-Jan-200719:3164,000X64SP1QFE
Shdocvw.dll6.0.3790.285825-Jan-200719:312,438,656X64SP1QFE
Shlwapi.dll6.0.3790.285825-Jan-200719:31621,568X64SP1QFE
Urlmon.dll6.0.3790.286925-Jan-200719:311,085,440X64SP1QFE
W03a2409.dll5.2.3790.284825-Jan-200719:3127,648X64SP1QFE
Wininet.dll6.0.3790.285825-Jan-200719:311,189,888X64SP1QFE
Wbrowseui.dll6.0.3790.285825-Jan-200719:311,036,800x86SP1QFE\WOW
Wdanim.dll6.3.1.14825-Jan-200719:311,058,304x86SP1QFE\WOW
Wdxtmsft.dll6.3.3790.285825-Jan-200719:31363,008x86SP1QFE\WOW
Wdxtrans.dll6.3.3790.285825-Jan-200719:31212,480x86SP1QFE\WOW
Wiedw.exe5.2.3790.285825-Jan-200719:3117,920x86SP1QFE\WOW
Wiepeers.dll6.0.3790.285825-Jan-200719:31253,952x86SP1QFE\WOW
Wjsproxy.dll6.0.3790.285825-Jan-200719:3116,384x86SP1QFE\WOW
Wmshtml.dll6.0.3790.285825-Jan-200719:313,157,504x86SP1QFE\WOW
Wmstime.dll6.0.3790.285825-Jan-200719:31537,088x86SP1QFE\WOW
Wpngfilt.dll5.2.3790.285825-Jan-200719:3142,496x86SP1QFE\WOW
Wshdocvw.dll6.0.3790.285825-Jan-200719:311,515,520x86SP1QFE\WOW
Wshlwapi.dll6.0.3790.285825-Jan-200719:31321,536x86SP1QFE\WOW
Wurlmon.dll6.0.3790.286925-Jan-200719:31697,344x86SP1QFE\WOW
Ww03a2409.dll5.2.3790.284825-Jan-200719:3127,136x86SP1QFE\WOW
Wwininet.dll6.0.3790.285825-Jan-200719:31666,112x86SP1QFE\WOW

Internet Explorer 7 for Windows XP Professional x64:

File NameVersionDateTimeSizeCPUFolder
Advpack.dll7.0.6000.1641409-Jan-200704:58161,280x64
Corpol.dll7.0.6000.1641409-Jan-200704:5922,016x64
Extmgr.dll7.0.6000.1641409-Jan-200704:59185,856x64
Ie4uinit.exe7.0.6000.1641409-Jan-200702:5768,608x64
Ieakeng.dll7.0.6000.1641409-Jan-200704:59195,584x64
Ieaksie.dll7.0.6000.1641409-Jan-200704:59267,264x64
Ieakui.dll7.0.6000.1641409-Jan-200704:59161,792x64
Ieapfltr.dll7.0.5825.009-Jan-200704:59424,448x64
Iedkcs32.dll17.0.6000.1641409-Jan-200704:59467,968x64
Ieframe.dll7.0.6000.1641409-Jan-200704:597,055,360x64
Ieframe.dll.mui7.0.6000.1641409-Jan-200705:06983,552x64
Iernonce.dll7.0.6000.1641409-Jan-200704:5957,344x64
Iertutil.dll7.0.6000.1641409-Jan-200704:59355,328x64
Ieudinit.exe7.0.6000.1641409-Jan-200702:5713,824x64
Iexplore.exe7.0.6000.1641409-Jan-200702:58675,328x64
Inetcpl.cpl7.0.6000.1641409-Jan-200705:002,021,888x64
Jsproxy.dll7.0.6000.1641409-Jan-200705:0032,256x64
Msfeeds.dll7.0.6000.1641409-Jan-200705:00553,472x64
Msfeedsbs.dll7.0.6000.1641409-Jan-200705:0075,264x64
Mshtml.dll7.0.6000.1641409-Jan-200705:005,662,720x64
Mshtmled.dll7.0.6000.1641409-Jan-200705:00757,760x64
Msrating.dll7.0.6000.1641409-Jan-200705:00242,176x64
Mstime.dll7.0.6000.1641409-Jan-200705:001,128,960x64
Occache.dll7.0.6000.1641409-Jan-200705:02148,480x64
Url.dll7.0.6000.1641409-Jan-200705:02108,544x64
Urlmon.dll7.0.6000.1641409-Jan-200705:021,417,216x64
Webcheck.dll7.0.6000.1641409-Jan-200705:03295,424x64
Wininet.dll7.0.6000.1641409-Jan-200705:031,019,392x64
Wadvpack.dll7.0.6000.1641409-Jan-200703:00124,928x86WOW
Wcorpol.dll7.0.6000.1641409-Jan-200703:0117,408x86WOW
Wextmgr.dll7.0.6000.1641409-Jan-200703:01132,608x86WOW
Wie4uinit.exe7.0.6000.1641409-Jan-200702:0856,832x86WOW
Wieakeng.dll7.0.6000.1641409-Jan-200703:02153,088x86WOW
Wieaksie.dll7.0.6000.1641409-Jan-200703:02230,400x86WOW
Wieakui.dll7.0.6000.1641409-Jan-200703:02161,792x86WOW
Wieapfltr.dll7.0.5825.009-Jan-200703:02383,488x86WOW
Wiedkcs32.dll17.0.6000.1641409-Jan-200703:02384,000x86WOW
Wieframe.dll7.0.6000.1641409-Jan-200703:026,054,400x86WOW
Wieframe.dll.mui7.0.6000.1641409-Jan-200703:07991,232x86WOW
Wiernonce.dll7.0.6000.1641409-Jan-200703:0244,544x86WOW
Wiertutil.dll7.0.6000.1641409-Jan-200703:02266,752x86WOW
Wieudinit.exe7.0.6000.1641409-Jan-200702:0813,824x86WOW
Wiexplore.exe7.0.6000.1641409-Jan-200702:08623,616x86WOW
Winetcpl.cpl7.0.6000.1641409-Jan-200703:021,823,744x86WOW
Wjsproxy.dll7.0.6000.1641409-Jan-200703:0227,136x86WOW
Wmsfeeds.dll7.0.6000.1641409-Jan-200703:02458,752x86WOW
Wmsfeedsbs.dll7.0.6000.1641409-Jan-200703:0251,712x86WOW
Wmshtml.dll7.0.6000.1641409-Jan-200703:023,580,416x86WOW
Wmshtmled.dll7.0.6000.1641409-Jan-200703:02477,696x86WOW
Wmsrating.dll7.0.6000.1641409-Jan-200703:03193,024x86WOW
Wmstime.dll7.0.6000.1641409-Jan-200703:03670,720x86WOW
Woccache.dll7.0.6000.1641409-Jan-200703:04102,400x86WOW
Wurl.dll7.0.6000.1641409-Jan-200703:04105,984x86WOW
Wurlmon.dll7.0.6000.1641409-Jan-200703:041,149,952x86WOW
Wwebcheck.dll7.0.6000.1641409-Jan-200703:04232,960x86WOW
Wwininet.dll7.0.6000.1641409-Jan-200703:05822,784x86WOW

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.

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

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB928090\Filelist

Internet Explorer 6 for Windows XP Professional x64 Edition:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP2\KB928090\Filelist

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

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP0\KB928090-IE7\Filelist

Internet Explorer 7 for Windows XP Professional x64 Edition:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP0\KB928090-IE7\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 928090 security update into the Windows installation source files.

Windows Server 2003 (all versions)

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

The security update for Windows Internet Explorer 7 for Windows Server 2003 Service Pack 1 requires Windows Server 2003 Service Pack 1.

Inclusion in Future Service Packs:
The update for this issue will be included in a future Service Pack or Update Rollup.

Installation Information

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/help Displays the command-line options
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed
/forcerestart Restarts the computer after installation and 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.
/promptrestart Display a dialog box prompting the local user to allow a restart
Special Options
/overwriteoem Overwrites OEM files without prompting
/nobackup Does not back up files needed for uninstall
/forceappsclose Forces other programs to close when the computer shuts down
/log:path Allows the redirection of installation log files
/integrate:path Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path] Extracts files without starting the Setup program
/ER Enables extended error reporting
/verbose Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

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

Deployment Information

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

Internet Explorer 6 for Windows Server 2003 and Windows Server 2003 Service Pack 1:

Windowsserver2003-kb928090-x86-enu /quiet

Internet Explorer 7 for Windows Server 2003 Service Pack 1:

IE7-KB928090-WindowsServer2003-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 KB928090.log file for any failure messages when they use this switch.

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

Internet Explorer 6 for Windows Server 2003 and Windows Server 2003 Service Pack 1:

Windowsserver2003-kb928090-x86-enu /norestart

Internet Explorer 7 for Windows Server 2003 Service Pack 1:

IE7-KB928090-WindowsServer2003-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%\$NTUninstallKB928090$\Spuninst and %Windir%\ie7updates\KB928090-IE7\spuninst folder.

Supported Spuninst.exe Switches
SwitchDescription
/help Displays the command-line options
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed
/forcerestart Restarts the computer after installation and 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.
/promptrestart Display a dialog box prompting the local user to allow a restart
Special Options
/forceappsclose Forces other programs to close when the computer shuts down
/log:path Allows the redirection of installation log files

File Information

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

Internet Explorer 6 for 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; and Windows Small Business Server 2003 R2:

File NameVersionDateTimeSizeFolder
Browseui.dll6.0.3790.63006-Jan-200711:291,057,280RTMGDR
Cdfview.dll6.0.3790.63006-Jan-200711:29147,968RTMGDR
Danim.dll6.3.1.14806-Jan-200711:29993,280RTMGDR
Digest.dll6.0.3790.63006-Jan-200711:2959,904RTMGDR
Dxtmsft.dll6.3.3790.63006-Jan-200711:29351,744RTMGDR
Dxtrans.dll6.3.3790.63006-Jan-200711:29205,312RTMGDR
Iepeers.dll6.0.3790.63006-Jan-200711:29238,592RTMGDR
Inseng.dll6.0.3790.63006-Jan-200711:2973,216RTMGDR
Jsproxy.dll6.0.3790.63006-Jan-200711:2914,848RTMGDR
Mshtml.dll6.0.3790.63006-Jan-200711:292,937,856RTMGDR
Mshtmled.dll6.0.3790.63006-Jan-200711:29454,144RTMGDR
Msrating.dll6.0.3790.63006-Jan-200711:29135,680RTMGDR
Mstime.dll6.0.3790.63006-Jan-200711:29504,832RTMGDR
Pngfilt.dll5.2.3790.63006-Jan-200711:2940,448RTMGDR
Shdocvw.dll6.0.3790.63006-Jan-200711:291,398,272RTMGDR
Shlwapi.dll6.0.3790.63006-Jan-200711:29287,744RTMGDR
Urlmon.dll6.0.3790.63925-Jan-200717:24528,896RTMGDR
Wininet.dll6.0.3790.63006-Jan-200711:29626,688RTMGDR
Browseui.dll6.0.3790.63006-Jan-200711:551,057,280RTMQFE
Cdfview.dll6.0.3790.63006-Jan-200711:55147,968RTMQFE
Danim.dll6.3.1.14806-Jan-200711:55993,280RTMQFE
Digest.dll6.0.3790.63006-Jan-200711:5559,904RTMQFE
Dxtmsft.dll6.3.3790.63006-Jan-200711:55352,256RTMQFE
Dxtrans.dll6.3.3790.63006-Jan-200711:55205,312RTMQFE
Iepeers.dll6.0.3790.63006-Jan-200711:55239,104RTMQFE
Inseng.dll6.0.3790.63006-Jan-200711:5573,216RTMQFE
Jsproxy.dll6.0.3790.63006-Jan-200711:5514,848RTMQFE
Mshtml.dll6.0.3790.63006-Jan-200711:552,939,904RTMQFE
Mshtmled.dll6.0.3790.63006-Jan-200711:55454,144RTMQFE
Msrating.dll6.0.3790.63006-Jan-200711:55135,680RTMQFE
Mstime.dll6.0.3790.63006-Jan-200711:55504,832RTMQFE
Pngfilt.dll5.2.3790.63006-Jan-200711:5540,448RTMQFE
Shdocvw.dll6.0.3790.63006-Jan-200711:551,399,808RTMQFE
Shlwapi.dll6.0.3790.63006-Jan-200711:55287,744RTMQFE
Urlmon.dll6.0.3790.63925-Jan-200717:22528,896RTMQFE
Wininet.dll6.0.3790.63006-Jan-200711:55631,296RTMQFE
Browseui.dll6.0.3790.285806-Jan-200712:091,036,800SP1GDR
Danim.dll6.3.1.14806-Jan-200712:091,058,304SP1GDR
Dxtmsft.dll6.3.3790.285806-Jan-200712:09363,008SP1GDR
Dxtrans.dll6.3.3790.285806-Jan-200712:09212,480SP1GDR
Iedw.exe5.2.3790.285805-Jan-200711:5517,920SP1GDR
Iepeers.dll6.0.3790.285806-Jan-200712:09253,952SP1GDR
Jsproxy.dll6.0.3790.285806-Jan-200712:0916,384SP1GDR
Mshtml.dll6.0.3790.285806-Jan-200712:093,155,456SP1GDR
Mstime.dll6.0.3790.285806-Jan-200712:09537,088SP1GDR
Pngfilt.dll5.2.3790.285806-Jan-200712:0942,496SP1GDR
Shdocvw.dll6.0.3790.285825-Jan-200719:011,514,496SP1GDR
Shlwapi.dll6.0.3790.285806-Jan-200712:09321,536SP1GDR
Urlmon.dll6.0.3790.286925-Jan-200717:36697,344SP1GDR
W03a2409.dll5.2.3790.284812-Dec-200610:234,096SP1GDR
Wininet.dll6.0.3790.285806-Jan-200712:09662,528SP1GDR
Browseui.dll6.0.3790.285806-Jan-200712:141,036,800SP1QFE
Danim.dll6.3.1.14806-Jan-200712:141,058,304SP1QFE
Dxtmsft.dll6.3.3790.285806-Jan-200712:14363,008SP1QFE
Dxtrans.dll6.3.3790.285806-Jan-200712:14212,480SP1QFE
Iedw.exe5.2.3790.285805-Jan-200712:3917,920SP1QFE
Iepeers.dll6.0.3790.285806-Jan-200712:14253,952SP1QFE
Jsproxy.dll6.0.3790.285806-Jan-200712:1416,384SP1QFE
Mshtml.dll6.0.3790.285806-Jan-200712:143,157,504SP1QFE
Mstime.dll6.0.3790.285806-Jan-200712:14537,088SP1QFE
Pngfilt.dll5.2.3790.285806-Jan-200712:1442,496SP1QFE
Shdocvw.dll6.0.3790.285806-Jan-200712:141,515,520SP1QFE
Shlwapi.dll6.0.3790.285806-Jan-200712:14321,536SP1QFE
Urlmon.dll6.0.3790.286925-Jan-200718:22697,344SP1QFE
W03a2409.dll5.2.3790.284812-Dec-200610:3227,136SP1QFE
Wininet.dll6.0.3790.285806-Jan-200712:14666,112SP1QFE

Internet Explorer 7 for 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; and Windows Small Business Server 2003 R2:

File NameVersionDateTimeSize
Advpack.dll7.0.6000.1641409-Jan-200703:00124,928
Corpol.dll7.0.6000.1641409-Jan-200703:0117,408
Extmgr.dll7.0.6000.1641409-Jan-200703:01132,608
Ie4uinit.exe7.0.6000.1641409-Jan-200702:0856,832
Ieakeng.dll7.0.6000.1641409-Jan-200703:02153,088
Ieaksie.dll7.0.6000.1641409-Jan-200703:02230,400
Ieakui.dll7.0.6000.1641409-Jan-200703:02161,792
Ieapfltr.dll7.0.5825.009-Jan-200703:02383,488
Iedkcs32.dll17.0.6000.1641409-Jan-200703:02384,000
Ieframe.dll7.0.6000.1641409-Jan-200703:026,054,400
Ieframe.dll.mui7.0.6000.1641409-Jan-200703:07991,232
Iernonce.dll7.0.6000.1641409-Jan-200703:0244,544
Iertutil.dll7.0.6000.1641409-Jan-200703:02266,752
Ieudinit.exe7.0.6000.1641409-Jan-200702:0813,824
Iexplore.exe7.0.6000.1641409-Jan-200702:08623,616
Inetcpl.cpl7.0.6000.1641409-Jan-200703:021,823,744
Jsproxy.dll7.0.6000.1641409-Jan-200703:0227,136
Msfeeds.dll7.0.6000.1641409-Jan-200703:02458,752
Msfeedsbs.dll7.0.6000.1641409-Jan-200703:0251,712
Mshtml.dll7.0.6000.1641409-Jan-200703:023,580,416
Mshtmled.dll7.0.6000.1641409-Jan-200703:02477,696
Msrating.dll7.0.6000.1641409-Jan-200703:03193,024
Mstime.dll7.0.6000.1641409-Jan-200703:03670,720
Occache.dll7.0.6000.1641409-Jan-200703:04102,400
Url.dll7.0.6000.1641409-Jan-200703:04105,984
Urlmon.dll7.0.6000.1641409-Jan-200703:041,149,952
Webcheck.dll7.0.6000.1641409-Jan-200703:04232,960
Wininet.dll7.0.6000.1641409-Jan-200703:05822,784
Updspapi.dll6.2.29.016-Nov-200622:10371,424

Internet Explorer 6 for 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.63025-Jan-200719:352,536,960IA-64RTMGDR
Cdfview.dll6.0.3790.63025-Jan-200719:35303,616IA-64RTMGDR
Digest.dll6.0.3790.63025-Jan-200719:35141,312IA-64RTMGDR
Dxtmsft.dll6.3.3790.63025-Jan-200719:35940,032IA-64RTMGDR
Dxtrans.dll6.3.3790.63025-Jan-200719:35585,728IA-64RTMGDR
Iepeers.dll6.0.3790.63025-Jan-200719:35675,840IA-64RTMGDR
Inseng.dll6.0.3790.63025-Jan-200719:35217,600IA-64RTMGDR
Jsproxy.dll6.0.3790.63025-Jan-200719:3536,864IA-64RTMGDR
Mshtml.dll6.0.3790.63025-Jan-200719:358,250,880IA-64RTMGDR
Mshtmled.dll6.0.3790.63025-Jan-200719:361,409,536IA-64RTMGDR
Msrating.dll6.0.3790.63025-Jan-200719:36387,584IA-64RTMGDR
Mstime.dll6.0.3790.63025-Jan-200719:361,666,560IA-64RTMGDR
Pngfilt.dll5.2.3790.63025-Jan-200719:36105,984IA-64RTMGDR
Shdocvw.dll6.0.3790.63025-Jan-200719:363,375,616IA-64RTMGDR
Shlwapi.dll6.0.3790.63025-Jan-200719:36740,352IA-64RTMGDR
Urlmon.dll6.0.3790.63925-Jan-200719:361,304,064IA-64RTMGDR
Wininet.dll6.0.3790.63025-Jan-200719:361,506,816IA-64RTMGDR
Wbrowseui.dll6.0.3790.63025-Jan-200719:361,057,280x86RTMGDR\WOW
Wcdfview.dll6.0.3790.63025-Jan-200719:36147,968x86RTMGDR\WOW
Wdanim.dll6.3.1.14825-Jan-200719:36993,280x86RTMGDR\WOW
Wdxtmsft.dll6.3.3790.63025-Jan-200719:36351,744x86RTMGDR\WOW
Wdxtrans.dll6.3.3790.63025-Jan-200719:36205,312x86RTMGDR\WOW
Wiepeers.dll6.0.3790.63025-Jan-200719:36238,592x86RTMGDR\WOW
Winseng.dll6.0.3790.63025-Jan-200719:3673,216x86RTMGDR\WOW
Wjsproxy.dll6.0.3790.63025-Jan-200719:3614,848x86RTMGDR\WOW
Wmshtml.dll6.0.3790.63025-Jan-200719:362,937,856x86RTMGDR\WOW
Wmshtmled.dll6.0.3790.63025-Jan-200719:36454,144x86RTMGDR\WOW
Wmsrating.dll6.0.3790.63025-Jan-200719:36135,680x86RTMGDR\WOW
Wmstime.dll6.0.3790.63025-Jan-200719:36504,832x86RTMGDR\WOW
Wpngfilt.dll5.2.3790.63025-Jan-200719:3640,448x86RTMGDR\WOW
Wshdocvw.dll6.0.3790.63025-Jan-200719:361,398,272x86RTMGDR\WOW
Wshlwapi.dll6.0.3790.63025-Jan-200719:36287,744x86RTMGDR\WOW
Wurlmon.dll6.0.3790.63925-Jan-200719:36528,896x86RTMGDR\WOW
Wwdigest.dll6.0.3790.63025-Jan-200719:3659,904x86RTMGDR\WOW
Wwininet.dll6.0.3790.63025-Jan-200719:36626,688x86RTMGDR\WOW
Browseui.dll6.0.3790.63025-Jan-200719:352,538,496IA-64RTMQFE
Cdfview.dll6.0.3790.63025-Jan-200719:35303,616IA-64RTMQFE
Digest.dll6.0.3790.63025-Jan-200719:35141,312IA-64RTMQFE
Dxtmsft.dll6.3.3790.63025-Jan-200719:35941,056IA-64RTMQFE
Dxtrans.dll6.3.3790.63025-Jan-200719:35586,752IA-64RTMQFE
Iepeers.dll6.0.3790.63025-Jan-200719:35678,912IA-64RTMQFE
Inseng.dll6.0.3790.63025-Jan-200719:35217,600IA-64RTMQFE
Jsproxy.dll6.0.3790.63025-Jan-200719:3536,864IA-64RTMQFE
Mshtml.dll6.0.3790.63025-Jan-200719:358,255,488IA-64RTMQFE
Mshtmled.dll6.0.3790.63025-Jan-200719:361,409,536IA-64RTMQFE
Msrating.dll6.0.3790.63025-Jan-200719:36387,584IA-64RTMQFE
Mstime.dll6.0.3790.63025-Jan-200719:361,666,560IA-64RTMQFE
Pngfilt.dll5.2.3790.63025-Jan-200719:36105,984IA-64RTMQFE
Shdocvw.dll6.0.3790.63025-Jan-200719:363,382,272IA-64RTMQFE
Shlwapi.dll6.0.3790.63025-Jan-200719:36740,352IA-64RTMQFE
Urlmon.dll6.0.3790.63925-Jan-200719:361,304,064IA-64RTMQFE
Wininet.dll6.0.3790.63025-Jan-200719:361,520,128IA-64RTMQFE
Wbrowseui.dll6.0.3790.63025-Jan-200719:361,057,280x86RTMQFE\WOW
Wcdfview.dll6.0.3790.63025-Jan-200719:36147,968x86RTMQFE\WOW
Wdanim.dll6.3.1.14825-Jan-200719:36993,280x86RTMQFE\WOW
Wdxtmsft.dll6.3.3790.63025-Jan-200719:36352,256x86RTMQFE\WOW
Wdxtrans.dll6.3.3790.63025-Jan-200719:36205,312x86RTMQFE\WOW
Wiepeers.dll6.0.3790.63025-Jan-200719:36239,104x86RTMQFE\WOW
Winseng.dll6.0.3790.63025-Jan-200719:3673,216x86RTMQFE\WOW
Wjsproxy.dll6.0.3790.63025-Jan-200719:3614,848x86RTMQFE\WOW
Wmshtml.dll6.0.3790.63025-Jan-200719:362,939,904x86RTMQFE\WOW
Wmshtmled.dll6.0.3790.63025-Jan-200719:36454,144x86RTMQFE\WOW
Wmsrating.dll6.0.3790.63025-Jan-200719:36135,680x86RTMQFE\WOW
Wmstime.dll6.0.3790.63025-Jan-200719:36504,832x86RTMQFE\WOW
Wpngfilt.dll5.2.3790.63025-Jan-200719:3640,448x86RTMQFE\WOW
Wshdocvw.dll6.0.3790.63025-Jan-200719:361,399,808x86RTMQFE\WOW
Wshlwapi.dll6.0.3790.63025-Jan-200719:36287,744x86RTMQFE\WOW
Wurlmon.dll6.0.3790.63925-Jan-200719:36528,896x86RTMQFE\WOW
Wwdigest.dll6.0.3790.63025-Jan-200719:3659,904x86RTMQFE\WOW
Wwininet.dll6.0.3790.63025-Jan-200719:36631,296x86RTMQFE\WOW
Browseui.dll6.0.3790.285825-Jan-200719:402,542,080IA-64SP1GDR
Dxtmsft.dll6.3.3790.285825-Jan-200719:401,009,152IA-64SP1GDR
Dxtrans.dll6.3.3790.285825-Jan-200719:40640,512IA-64SP1GDR
Iepeers.dll6.0.3790.285825-Jan-200719:40717,312IA-64SP1GDR
Jsproxy.dll6.0.3790.285825-Jan-200719:4045,568IA-64SP1GDR
Mshtml.dll6.0.3790.285825-Jan-200719:409,364,992IA-64SP1GDR
Mstime.dll6.0.3790.285825-Jan-200719:401,845,760IA-64SP1GDR
Pngfilt.dll5.2.3790.285825-Jan-200719:40116,736IA-64SP1GDR
Shdocvw.dll6.0.3790.285825-Jan-200719:403,678,208IA-64SP1GDR
Shlwapi.dll6.0.3790.285825-Jan-200719:40823,296IA-64SP1GDR
Urlmon.dll6.0.3790.286925-Jan-200719:401,615,872IA-64SP1GDR
W03a2409.dll5.2.3790.284825-Jan-200719:403,072IA-64SP1GDR
Wininet.dll6.0.3790.285825-Jan-200719:401,695,744IA-64SP1GDR
Wbrowseui.dll6.0.3790.285825-Jan-200719:401,036,800x86SP1GDR\WOW
Wdanim.dll6.3.1.14825-Jan-200719:401,058,304x86SP1GDR\WOW
Wdxtmsft.dll6.3.3790.285825-Jan-200719:40363,008x86SP1GDR\WOW
Wdxtrans.dll6.3.3790.285825-Jan-200719:40212,480x86SP1GDR\WOW
Wiedw.exe5.2.3790.285825-Jan-200719:4017,920x86SP1GDR\WOW
Wiepeers.dll6.0.3790.285825-Jan-200719:40253,952x86SP1GDR\WOW
Wjsproxy.dll6.0.3790.285825-Jan-200719:4016,384x86SP1GDR\WOW
Wmshtml.dll6.0.3790.285825-Jan-200719:403,155,456x86SP1GDR\WOW
Wmstime.dll6.0.3790.285825-Jan-200719:40537,088x86SP1GDR\WOW
Wpngfilt.dll5.2.3790.285825-Jan-200719:4042,496x86SP1GDR\WOW
Wshdocvw.dll6.0.3790.285825-Jan-200719:401,514,496x86SP1GDR\WOW
Wshlwapi.dll6.0.3790.285825-Jan-200719:40321,536x86SP1GDR\WOW
Wurlmon.dll6.0.3790.286925-Jan-200719:40697,344x86SP1GDR\WOW
Ww03a2409.dll5.2.3790.284825-Jan-200719:404,096x86SP1GDR\WOW
Wwininet.dll6.0.3790.285825-Jan-200719:40662,528x86SP1GDR\WOW
Browseui.dll6.0.3790.285825-Jan-200719:362,541,568IA-64SP1QFE
Dxtmsft.dll6.3.3790.285825-Jan-200719:361,009,152IA-64SP1QFE
Dxtrans.dll6.3.3790.285825-Jan-200719:36640,512IA-64SP1QFE
Iepeers.dll6.0.3790.285825-Jan-200719:36717,824IA-64SP1QFE
Jsproxy.dll6.0.3790.285825-Jan-200719:3645,568IA-64SP1QFE
Mshtml.dll6.0.3790.285825-Jan-200719:369,370,624IA-64SP1QFE
Mstime.dll6.0.3790.285825-Jan-200719:361,845,760IA-64SP1QFE
Pngfilt.dll5.2.3790.285825-Jan-200719:36116,736IA-64SP1QFE
Shdocvw.dll6.0.3790.285825-Jan-200719:363,680,256IA-64SP1QFE
Shlwapi.dll6.0.3790.285825-Jan-200719:36823,296IA-64SP1QFE
Urlmon.dll6.0.3790.286925-Jan-200719:361,616,384IA-64SP1QFE
W03a2409.dll5.2.3790.284825-Jan-200719:3626,112IA-64SP1QFE
Wininet.dll6.0.3790.285825-Jan-200719:361,701,376IA-64SP1QFE
Wbrowseui.dll6.0.3790.285825-Jan-200719:361,036,800x86SP1QFE\WOW
Wdanim.dll6.3.1.14825-Jan-200719:361,058,304x86SP1QFE\WOW
Wdxtmsft.dll6.3.3790.285825-Jan-200719:36363,008x86SP1QFE\WOW
Wdxtrans.dll6.3.3790.285825-Jan-200719:36212,480x86SP1QFE\WOW
Wiedw.exe5.2.3790.285825-Jan-200719:3617,920x86SP1QFE\WOW
Wiepeers.dll6.0.3790.285825-Jan-200719:36253,952x86SP1QFE\WOW
Wjsproxy.dll6.0.3790.285825-Jan-200719:3616,384x86SP1QFE\WOW
Wmshtml.dll6.0.3790.285825-Jan-200719:363,157,504x86SP1QFE\WOW
Wmstime.dll6.0.3790.285825-Jan-200719:36537,088x86SP1QFE\WOW
Wpngfilt.dll5.2.3790.285825-Jan-200719:3642,496x86SP1QFE\WOW
Wshdocvw.dll6.0.3790.285825-Jan-200719:361,515,520x86SP1QFE\WOW
Wshlwapi.dll6.0.3790.285825-Jan-200719:36321,536x86SP1QFE\WOW
Wurlmon.dll6.0.3790.286925-Jan-200719:36697,344x86SP1QFE\WOW
Ww03a2409.dll5.2.3790.284825-Jan-200719:3627,136x86SP1QFE\WOW
Wwininet.dll6.0.3790.285825-Jan-200719:36666,112x86SP1QFE\WOW

Internet Explorer 7 for 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
Advpack.dll7.0.6000.1641410-Jan-200722:57283,136IA-64
Corpol.dll7.0.6000.1641410-Jan-200723:0049,152IA-64
Extmgr.dll7.0.6000.1641410-Jan-200723:01307,200IA-64
Ie4uinit.exe7.0.6000.1641410-Jan-200722:58110,080IA-64
Ieakeng.dll7.0.6000.1641410-Jan-200722:58385,536IA-64
Ieaksie.dll7.0.6000.1641410-Jan-200722:58503,296IA-64
Ieakui.dll7.0.6000.1641410-Jan-200722:25161,792IA-64
Ieapfltr.dll7.0.5825.010-Jan-200719:071,075,712IA-64
Iedkcs32.dll17.0.6000.1641410-Jan-200722:58747,520IA-64
Ieframe.dll7.0.6000.1641410-Jan-200723:0011,534,848IA-64
Ieframe.dll.mui7.0.6000.1641410-Jan-200722:59980,992IA-64
Iernonce.dll7.0.6000.1641410-Jan-200722:5799,840IA-64
Iertutil.dll7.0.6000.1641410-Jan-200722:54539,648IA-64
Ieudinit.exe7.0.6000.1641410-Jan-200722:5730,720IA-64
Iexplore.exe7.0.6000.1641410-Jan-200723:01746,496IA-64
Inetcpl.cpl7.0.6000.1641410-Jan-200723:012,383,360IA-64
Jsproxy.dll7.0.6000.1641410-Jan-200723:0081,920IA-64
Msfeeds.dll7.0.6000.1641410-Jan-200722:56957,952IA-64
Msfeedsbs.dll7.0.6000.1641410-Jan-200722:56136,704IA-64
Mshtml.dll7.0.6000.1641410-Jan-200722:599,965,568IA-64
Mshtmled.dll7.0.6000.1641410-Jan-200722:551,518,592IA-64
Msrating.dll7.0.6000.1641410-Jan-200723:01479,232IA-64
Mstime.dll7.0.6000.1641410-Jan-200722:562,229,760IA-64
Occache.dll7.0.6000.1641410-Jan-200723:01258,048IA-64
Url.dll7.0.6000.1641410-Jan-200723:01130,048IA-64
Urlmon.dll7.0.6000.1641410-Jan-200723:002,518,528IA-64
Webcheck.dll7.0.6000.1641410-Jan-200723:01636,416IA-64
Wininet.dll7.0.6000.1641410-Jan-200723:001,858,048IA-64
Updspapi.dll6.2.29.016-Nov-200622:10638,688IA-64
Wadvpack.dll7.0.6000.1641409-Jan-200703:00124,928x86WOW
Wcorpol.dll7.0.6000.1641409-Jan-200703:0117,408x86WOW
Wextmgr.dll7.0.6000.1641409-Jan-200703:01132,608x86WOW
Wie4uinit.exe7.0.6000.1641409-Jan-200702:0856,832x86WOW
Wieakeng.dll7.0.6000.1641409-Jan-200703:02153,088x86WOW
Wieaksie.dll7.0.6000.1641409-Jan-200703:02230,400x86WOW
Wieakui.dll7.0.6000.1641409-Jan-200703:02161,792x86WOW
Wieapfltr.dll7.0.5825.009-Jan-200703:02383,488x86WOW
Wiedkcs32.dll17.0.6000.1641409-Jan-200703:02384,000x86WOW
Wieframe.dll7.0.6000.1641409-Jan-200703:026,054,400x86WOW
Wieframe.dll.mui7.0.6000.1641409-Jan-200703:07991,232x86WOW
Wiernonce.dll7.0.6000.1641409-Jan-200703:0244,544x86WOW
Wiertutil.dll7.0.6000.1641409-Jan-200703:02266,752x86WOW
Wieudinit.exe7.0.6000.1641409-Jan-200702:0813,824x86WOW
Wiexplore.exe7.0.6000.1641409-Jan-200702:08623,616x86WOW
Winetcpl.cpl7.0.6000.1641409-Jan-200703:021,823,744x86WOW
Wjsproxy.dll7.0.6000.1641409-Jan-200703:0227,136x86WOW
Wmsfeeds.dll7.0.6000.1641409-Jan-200703:02458,752x86WOW
Wmsfeedsbs.dll7.0.6000.1641409-Jan-200703:0251,712x86WOW
Wmshtml.dll7.0.6000.1641409-Jan-200703:023,580,416x86WOW
Wmshtmled.dll7.0.6000.1641409-Jan-200703:02477,696x86WOW
Wmsrating.dll7.0.6000.1641409-Jan-200703:03193,024x86WOW
Wmstime.dll7.0.6000.1641409-Jan-200703:03670,720x86WOW
Woccache.dll7.0.6000.1641409-Jan-200703:04102,400x86WOW
Wurl.dll7.0.6000.1641409-Jan-200703:04105,984x86WOW
Wurlmon.dll7.0.6000.1641409-Jan-200703:041,149,952x86WOW
Wwebcheck.dll7.0.6000.1641409-Jan-200703:04232,960x86WOW
Wwininet.dll7.0.6000.1641409-Jan-200703:05822,784x86WOW

Internet Explorer 6 for 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.285825-Jan-200719:371,605,120X64SP1GDR
Danim.dll6.3.1.14825-Jan-200719:371,989,120X64SP1GDR
Dxtmsft.dll6.3.3790.285825-Jan-200719:37561,664X64SP1GDR
Dxtrans.dll6.3.3790.285825-Jan-200719:37332,288X64SP1GDR
Iepeers.dll6.0.3790.285825-Jan-200719:37369,664X64SP1GDR
Jsproxy.dll6.0.3790.285825-Jan-200719:3724,064X64SP1GDR
Mshtml.dll6.0.3790.285825-Jan-200719:375,996,544X64SP1GDR
Mstime.dll6.0.3790.285825-Jan-200719:37900,608X64SP1GDR
Pngfilt.dll5.2.3790.285825-Jan-200719:3764,000X64SP1GDR
Shdocvw.dll6.0.3790.285825-Jan-200719:372,437,632X64SP1GDR
Shlwapi.dll6.0.3790.285825-Jan-200719:37621,568X64SP1GDR
Urlmon.dll6.0.3790.286925-Jan-200719:371,084,928X64SP1GDR
W03a2409.dll5.2.3790.284825-Jan-200719:374,608X64SP1GDR
Wininet.dll6.0.3790.285825-Jan-200719:371,187,840X64SP1GDR
Wbrowseui.dll6.0.3790.285825-Jan-200719:371,036,800x86SP1GDR\WOW
Wdanim.dll6.3.1.14825-Jan-200719:371,058,304x86SP1GDR\WOW
Wdxtmsft.dll6.3.3790.285825-Jan-200719:37363,008x86SP1GDR\WOW
Wdxtrans.dll6.3.3790.285825-Jan-200719:37212,480x86SP1GDR\WOW
Wiedw.exe5.2.3790.285825-Jan-200719:3717,920x86SP1GDR\WOW
Wiepeers.dll6.0.3790.285825-Jan-200719:37253,952x86SP1GDR\WOW
Wjsproxy.dll6.0.3790.285825-Jan-200719:3716,384x86SP1GDR\WOW
Wmshtml.dll6.0.3790.285825-Jan-200719:373,155,456x86SP1GDR\WOW
Wmstime.dll6.0.3790.285825-Jan-200719:37537,088x86SP1GDR\WOW
Wpngfilt.dll5.2.3790.285825-Jan-200719:3742,496x86SP1GDR\WOW
Wshdocvw.dll6.0.3790.285825-Jan-200719:371,514,496x86SP1GDR\WOW
Wshlwapi.dll6.0.3790.285825-Jan-200719:37321,536x86SP1GDR\WOW
Wurlmon.dll6.0.3790.286925-Jan-200719:37697,344x86SP1GDR\WOW
Ww03a2409.dll5.2.3790.284825-Jan-200719:374,096x86SP1GDR\WOW
Wwininet.dll6.0.3790.285825-Jan-200719:37662,528x86SP1GDR\WOW
Browseui.dll6.0.3790.285825-Jan-200719:311,605,120X64SP1QFE
Danim.dll6.3.1.14825-Jan-200719:311,989,120X64SP1QFE
Dxtmsft.dll6.3.3790.285825-Jan-200719:31561,664X64SP1QFE
Dxtrans.dll6.3.3790.285825-Jan-200719:31332,288X64SP1QFE
Iepeers.dll6.0.3790.285825-Jan-200719:31370,176X64SP1QFE
Jsproxy.dll6.0.3790.285825-Jan-200719:3124,064X64SP1QFE
Mshtml.dll6.0.3790.285825-Jan-200719:315,999,616X64SP1QFE
Mstime.dll6.0.3790.285825-Jan-200719:31900,608X64SP1QFE
Pngfilt.dll5.2.3790.285825-Jan-200719:3164,000X64SP1QFE
Shdocvw.dll6.0.3790.285825-Jan-200719:312,438,656X64SP1QFE
Shlwapi.dll6.0.3790.285825-Jan-200719:31621,568X64SP1QFE
Urlmon.dll6.0.3790.286925-Jan-200719:311,085,440X64SP1QFE
W03a2409.dll5.2.3790.284825-Jan-200719:3127,648X64SP1QFE
Wininet.dll6.0.3790.285825-Jan-200719:311,189,888X64SP1QFE
Wbrowseui.dll6.0.3790.285825-Jan-200719:311,036,800x86SP1QFE\WOW
Wdanim.dll6.3.1.14825-Jan-200719:311,058,304x86SP1QFE\WOW
Wdxtmsft.dll6.3.3790.285825-Jan-200719:31363,008x86SP1QFE\WOW
Wdxtrans.dll6.3.3790.285825-Jan-200719:31212,480x86SP1QFE\WOW
Wiedw.exe5.2.3790.285825-Jan-200719:3117,920x86SP1QFE\WOW
Wiepeers.dll6.0.3790.285825-Jan-200719:31253,952x86SP1QFE\WOW
Wjsproxy.dll6.0.3790.285825-Jan-200719:3116,384x86SP1QFE\WOW
Wmshtml.dll6.0.3790.285825-Jan-200719:313,157,504x86SP1QFE\WOW
Wmstime.dll6.0.3790.285825-Jan-200719:31537,088x86SP1QFE\WOW
Wpngfilt.dll5.2.3790.285825-Jan-200719:3142,496x86SP1QFE\WOW
Wshdocvw.dll6.0.3790.285825-Jan-200719:311,515,520x86SP1QFE\WOW
Wshlwapi.dll6.0.3790.285825-Jan-200719:31321,536x86SP1QFE\WOW
Wurlmon.dll6.0.3790.286925-Jan-200719:31697,344x86SP1QFE\WOW
Ww03a2409.dll5.2.3790.284825-Jan-200719:3127,136x86SP1QFE\WOW
Wwininet.dll6.0.3790.285825-Jan-200719:31666,112x86SP1QFE\WOW

Internet Explorer 7 for 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
Advpack.dll7.0.6000.1641409-Jan-200704:58161,280x64
Corpol.dll7.0.6000.1641409-Jan-200704:5922,016x64
Extmgr.dll7.0.6000.1641409-Jan-200704:59185,856x64
Ie4uinit.exe7.0.6000.1641409-Jan-200702:5768,608x64
Ieakeng.dll7.0.6000.1641409-Jan-200704:59195,584x64
Ieaksie.dll7.0.6000.1641409-Jan-200704:59267,264x64
Ieakui.dll7.0.6000.1641409-Jan-200704:59161,792x64
Ieapfltr.dll7.0.5825.009-Jan-200704:59424,448x64
Iedkcs32.dll17.0.6000.1641409-Jan-200704:59467,968x64
Ieframe.dll7.0.6000.1641409-Jan-200704:597,055,360x64
Ieframe.dll.mui7.0.6000.1641409-Jan-200705:06983,552x64
Iernonce.dll7.0.6000.1641409-Jan-200704:5957,344x64
Iertutil.dll7.0.6000.1641409-Jan-200704:59355,328x64
Ieudinit.exe7.0.6000.1641409-Jan-200702:5713,824x64
Iexplore.exe7.0.6000.1641409-Jan-200702:58675,328x64
Inetcpl.cpl7.0.6000.1641409-Jan-200705:002,021,888x64
Jsproxy.dll7.0.6000.1641409-Jan-200705:0032,256x64
Msfeeds.dll7.0.6000.1641409-Jan-200705:00553,472x64
Msfeedsbs.dll7.0.6000.1641409-Jan-200705:0075,264x64
Mshtml.dll7.0.6000.1641409-Jan-200705:005,662,720x64
Mshtmled.dll7.0.6000.1641409-Jan-200705:00757,760x64
Msrating.dll7.0.6000.1641409-Jan-200705:00242,176x64
Mstime.dll7.0.6000.1641409-Jan-200705:001,128,960x64
Occache.dll7.0.6000.1641409-Jan-200705:02148,480x64
Url.dll7.0.6000.1641409-Jan-200705:02108,544x64
Urlmon.dll7.0.6000.1641409-Jan-200705:021,417,216x64
Webcheck.dll7.0.6000.1641409-Jan-200705:03295,424x64
Wininet.dll7.0.6000.1641409-Jan-200705:031,019,392x64
Wadvpack.dll7.0.6000.1641409-Jan-200703:00124,928x86WOW
Wcorpol.dll7.0.6000.1641409-Jan-200703:0117,408x86WOW
Wextmgr.dll7.0.6000.1641409-Jan-200703:01132,608x86WOW
Wie4uinit.exe7.0.6000.1641409-Jan-200702:0856,832x86WOW
Wieakeng.dll7.0.6000.1641409-Jan-200703:02153,088x86WOW
Wieaksie.dll7.0.6000.1641409-Jan-200703:02230,400x86WOW
Wieakui.dll7.0.6000.1641409-Jan-200703:02161,792x86WOW
Wieapfltr.dll7.0.5825.009-Jan-200703:02383,488x86WOW
Wiedkcs32.dll17.0.6000.1641409-Jan-200703:02384,000x86WOW
Wieframe.dll7.0.6000.1641409-Jan-200703:026,054,400x86WOW
Wieframe.dll.mui7.0.6000.1641409-Jan-200703:07991,232x86WOW
Wiernonce.dll7.0.6000.1641409-Jan-200703:0244,544x86WOW
Wiertutil.dll7.0.6000.1641409-Jan-200703:02266,752x86WOW
Wieudinit.exe7.0.6000.1641409-Jan-200702:0813,824x86WOW
Wiexplore.exe7.0.6000.1641409-Jan-200702:08623,616x86WOW
Winetcpl.cpl7.0.6000.1641409-Jan-200703:021,823,744x86WOW
Wjsproxy.dll7.0.6000.1641409-Jan-200703:0227,136x86WOW
Wmsfeeds.dll7.0.6000.1641409-Jan-200703:02458,752x86WOW
Wmsfeedsbs.dll7.0.6000.1641409-Jan-200703:0251,712x86WOW
Wmshtml.dll7.0.6000.1641409-Jan-200703:023,580,416x86WOW
Wmshtmled.dll7.0.6000.1641409-Jan-200703:02477,696x86WOW
Wmsrating.dll7.0.6000.1641409-Jan-200703:03193,024x86WOW
Wmstime.dll7.0.6000.1641409-Jan-200703:03670,720x86WOW
Woccache.dll7.0.6000.1641409-Jan-200703:04102,400x86WOW
Wurl.dll7.0.6000.1641409-Jan-200703:04105,984x86WOW
Wurlmon.dll7.0.6000.1641409-Jan-200703:041,149,952x86WOW
Wwebcheck.dll7.0.6000.1641409-Jan-200703:04232,960x86WOW
Wwininet.dll7.0.6000.1641409-Jan-200703:05822,784x86WOW

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.

Internet Explorer 6 for 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\KB928090\Filelist

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

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP0\KB928090-IE7\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 928090 security update into the Windows installation source files.

Other Information

Acknowledgments

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

  • H D Moore of BreakingPoint Systems for reporting five class identifiers documented in the COM Object Instantiation Memory Corruption Vulnerability (CVE-2007-0219).
  • iDefense for reporting the FTP Server Response Parsing Memory Corruption Vulnerability (CVE-2007-0217).

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 (February 13, 2007): Bulletin published.
  • V1.1 (February 21, 2007): Bulletin revised to correct installation verification keys for Windows Internet Explorer 7. Removal information for Windows Server 2003 updated with correct folder.

Built at 2014-04-18T13:49:36Z-07:00

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