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

Microsoft Security Bulletin MS05-054 - Critical

Cumulative Security Update for Internet Explorer (905915)

Published: December 13, 2005 | Updated: March 08, 2006

Version: 1.2

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 update replaces the update that is included with Microsoft Security Bulletin MS05-052. That update is also a cumulative update.

Caveats: Microsoft Knowledge Base Article 905915 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 905915.

This update does include hotfixes that have been released since the release of MS04-004 and MS04-025, but they will only be installed on systems that need them. Customers who have received hotfixes from Microsoft or from their support providers since the release of MS04-004 or MS04-025 should review the “I have received a hotfix from Microsoft or my support provider since the release of MS04-004. Is that hotfix included in this security update?” question in the FAQ section of this bulletin to determine how you can make sure that the necessary hotfixes are installed. Microsoft Knowledge Base Article 905915 also documents this in more detail.

Tested Software and Security Update Download Locations:

Affected Software:

  • Microsoft Windows 2000 Service Pack 4
  • Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2
  • Microsoft Windows XP Professional x64 Edition
  • Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1
  • Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based Systems
  • Microsoft Windows Server 2003 x64 Edition family
  • Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME) – Review the FAQ section of this bulletin for details about these operating systems.

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

Tested Microsoft Windows Components:

Affected Components:

  • Internet Explorer 5.01 Service Pack 4 on Microsoft Windows 2000 Service Pack 4 – Download the update
  • Internet Explorer 6 Service Pack 1 on Microsoft Windows 2000 Service Pack 4 or on Microsoft Windows XP Service Pack 1 – Download the update
  • Internet Explorer 6 for Microsoft Windows XP Service Pack 2 – Download the update
  • Internet Explorer 6 for Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 – Download the update
  • Internet Explorer 6 for Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems – Download the update
  • Internet Explorer 6 for Microsoft Windows Server 2003 x64 Edition – Download the update
  • Internet Explorer 6 for Microsoft Windows XP Professional x64 Edition – Download the update
  • Internet Explorer 5.5 Service Pack 2 on Microsoft Windows Millennium Edition – Review the FAQ section of this bulletin for details about this version.
  • Internet Explorer 6 Service Pack 1 on Microsoft Windows 98, on Microsoft Windows 98 SE, or on Microsoft Windows Millennium Edition – Review the FAQ section of this bulletin for details about this version.

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.

General Information

Executive Summary:

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

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

We recommend that customers apply the update immediately.

Severity Ratings and Vulnerability Identifiers:

Vulnerability IdentifiersImpact of VulnerabilityInternet Explorer 5.0 Service Pack 4Internet Explorer 5.5 Service Pack 2 on Windows MEInternet Explorer 6 Service Pack 1 (All supported operating system versions earlier than Windows Server 2003)Internet Explorer 6 for Windows Server 2003 and Windows Server 2003 Service Pack 1Internet Explorer 6 for Windows XP Service Pack 2
File Download Dialog Box Manipulation Vulnerability - CAN-2005-2829Remote Code ExecutionModerateModerateModerateLowModerate
HTTPS Proxy Vulnerability- CAN-2005-2830Information DisclosureModerateModerateModerateModerateModerate
COM Object Instantiation Memory Corruption Vulnerability - CAN-2005-2831Remote Code ExecutionCriticalCriticalCriticalModerateCritical
Mismatched Document Object Model Objects Memory Corruption Vulnerability - CAN-2005-1790Remote Code ExecutionCriticalCriticalCriticalModerateCritical
Aggregate Severity of All Vulnerabilities Critical Critical Critical Moderate Critical

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

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

  • The Internet Explorer 6 for Windows XP Professional x64 Edition severity rating is the same as the Internet Explorer 6 Service Pack 1 (All supported operating system versions earlier than Windows Server 2003) severity rating.
  • The Internet Explorer 6 for Microsoft Windows Server 2003 for Itanium-based Systems and Windows Server 2003 x64 Edition severity rating is the same as the Internet Explorer 6 for Windows Server 2003 severity rating.

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

Bulletin IDInternet Explorer 5.01 Service Pack 4Internet Explorer 5.5 Service Pack 2 on Windows MEInternet Explorer 6 Service Pack 1 (all versions earlier than Windows Server 2003)Internet Explorer 6 for Windows Server 2003 (including 64-Bit Edition)Internet Explorer 6 for Windows XP Service Pack 2
MS05-052 ReplacedReplacedReplacedReplacedReplaced

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

I have received a hotfix from Microsoft or my support provider since the release of MS04-004. Is that hotfix included in this security update?
Yes. When you install the security update that is intended for systems that are running Internet Explorer 6 Service Pack 1 on Microsoft Windows 2000 Service Pack 4 or on Microsoft Windows XP Service Pack 1, 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. However, the installer detects only hotfixes that were released since Microsoft Security Bulletin MS04-038 and Internet Explorer Update Rollup 873377 or Internet Explorer Update Rollup 889669.

See Microsoft Knowledge Base Article 905915 for additional information if you have to apply a hotfix that was released before Microsoft Security Bulletin MS04-038 on a system that has the MS05-054 update installed.

For Internet Explorer 6 for Microsoft Windows XP Service Pack 2 or for Windows Server 2003 or later, this security update contains hotfixes that were included with MS04-025 or later Internet Explorer security updates. However, the hotfix versions of the files that are included in this security update are installed only if you have previously installed an Internet Explorer hotfix to update any of the files that are listed in the “Security Update Information” section of this bulletin.

For Internet Explorer 5.01 Service Pack 4, Internet Explorer 5.5 Service Pack 2, and Internet Explorer 6 Service Pack 1 for Windows XP Service Pack 1 and Windows 2000 Service Pack 4, the MS05-054 security updates contain hotfixes that were included after MS04-004 up to and including the cumulative updates in MS05-054. The hotfix versions of the files that are included in this security update are installed regardless of whether you have previously installed an Internet Explorer hotfix to update any of the files that are listed in the “Security Update Information” section of this bulletin.

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 and in addition to changes that were introduced in previous Internet Explorer security bulletins, this update introduces the following changes:

  • This cumulative security update sets the kill bit for the First4Internet XCP uninstallation ActiveX control. For more information about this ActiveX control, visit the SONY BMG Web site. Older versions of this control have been found to contain a security vulnerability. To help protect customers who have this control installed, this update prevents older versions of this control from running in Internet Explorer. It does this by setting the kill bit for the older versions of this control that are no longer supported. This kill-bit is being set with the permission of the owner of the ActiveX control. For more information about kill bits, see Microsoft Knowledge Base Article 240797. The class identifiers (CLSIDs) for this ActiveX control are:
    • 4EA7C4C5-C5C0-4F5C-A008-8293505F71CC
    • 7965A6FD-B383-4658-A8E0-C78DCF2D0E63
    • 9A60A782-282B-4D69-9B2A-0945D588A125
    • 80E8743E-8AC5-46F1-96A0-59FA30740C51
  • This cumulative security update also includes the checks that were introduced in Microsoft Security Bulletin MS05-052 before a COM object is allowed to run in Internet Explorer. The intent of this change is to prevent COM objects that were not designed to be instantiated in Internet Explorer from being instantiated in Internet Explorer:
    • Microsoft Knowledge Base Article 909889:ActiveX controls may not load as expected in Internet Explorer due to defense in depth changes introduced in cumulative security update 896688 (MS05-052).
    • Microsoft Knowledge Base Article 909738: A Web page that contains a custom ActiveX control may not load as expected in Internet Explorer due to defense in depth changes introduced in cumulative security update 896688 (MS05-052).
  • This cumulative security update also includes defense-in-depth improvements to the kill-bit mechanism used by Internet Explorer when determining if it should instantiate an ActiveX control.

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

This update sets the kill bit for the Microsoft MciWndx ActiveX control. Internet Explorer no longer supports this control and this update prevents this control from running in Internet Explorer. For more information about kill bits, see Microsoft Knowledge Base Article 240797. The CLSID for this ActiveX control is 288F1523-FAC4-11CE-B16F-00AA0060D93D.

Note This control is not marked safe for scripting and does not implement the IObjectSafety interface. At least one of these requirements must be met for an ActiveX Control to be allowed to run in Internet Explorer. For more information about the IObjectSafety interface requirement, see Microsoft Knowledge Base Article 216434 and Microsoft Knowledge Base Article 909738.

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

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

Are Windows 98, Windows 98 Second Edition, or Windows Millennium Edition critically affected by one or more of the vulnerabilities that are addressed in this security bulletin?
Yes. Windows 98, Windows 98 Second Edition, and Windows Millennium Edition are critically affected by the vulnerabilities that are addressed in this security bulletin. Critical security updates for these platforms are available, are provided as part of this security bulletin and can be downloaded only from the Microsoft Update Web site or from the Windows Update Web site. For more information about severity ratings, visit the following Web site.

Note Updates for localized versions of Microsoft Windows Millennium Edition that are not supported by Windows Update are available for download at the following download locations:

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’m still using one of these operating systems, what should I do?
Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, Windows 2000 Service Pack 2, and Windows 2000 Service Pack 3 have reached the end of their life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.

Customers who require additional support for Windows NT 4.0 SP6a and Windows 2000 Service Pack 3 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.

Security update support for Microsoft Windows XP 64-Bit Edition Service Pack 1 (Itanium) and Microsoft Windows XP 64-Bit Edition Version 2003 (Itanium) ended on June 30, 2005. I’m still using one of these operating systems, what should I do?
With the release of Windows XP Professional x64 Edition, Microsoft Windows XP 64-Bit Edition Service Pack 1 (Itanium) and Microsoft Windows XP 64-Bit Edition Version 2003 (Itanium) will no longer receive security update support. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. Microsoft will continue to fully support Windows Server 2003 for Itanium-based systems, Windows XP Professional x64 Edition, and Windows Server 2003 x64 Editions for 64-bit computing requirements. Microsoft continues to license and support Windows Server 2003 Enterprise and Datacenter editions for Itanium-based systems, and the 64-bit version of SQL Server 2000 Enterprise Edition. In the future, we will expand Itanium support to Visual Studio 2005, .NET Framework 2005, and SQL Server 2005.

Customers who require additional assistance about this issue must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for information about the available migration 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.

Can I use the Microsoft Baseline Security Analyzer (MBSA) 1.2.1 to determine whether this update is required?
Yes. MBSA 1.2.1 will determine whether this update is required. For more information about MBSA, visit the MBSA Web site.

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

Can I use Systems Management Server (SMS) to determine whether this update is required?
Yes. SMS can help detect and deploy this security update. For information about SMS, visit the SMS Web site.

Note As of this release, there is no longer an additional package that is specifically designed for SMS deployment for customers who use Windows 2000 Service Pack 4 or Windows XP Service Pack 1 and who also still have Windows NT 4.0 systems in their environment. The security update for Internet Explorer 6 Service Pack 1 for Microsoft Windows 2000 Service Pack 4 and Microsoft Windows XP Service Pack 1 can instead be deployed using SMS. This security update will only target Windows 2000 Service Pack 4 and Microsoft Windows XP Service Pack 1 systems.

The Security Update Inventory Tool can be used by SMS for detecting security updates that are offered by Windows Update, that are supported by Software Update Services, and other security updates that are supported by MBSA 1.2.1. For more information about the Security Update Inventory Tool, see the following Microsoft Web site. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460.

The SMS 2003 Inventory Tool for Microsoft Updates can be used by SMS for detecting security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 Inventory Tool for Microsoft Updates, see the following Microsoft Web site.

For more information about SMS, visit the SMS Web site.

File Download Dialog Box Manipulation Vulnerability - CAN-2005-2829:

A remote code execution vulnerability exists in the way Internet Explorer displays file download dialog boxes and accepts user input during interaction with a Web page. This interaction could be in the form of certain keystrokes that a user makes when visiting a Web page. A custom dialog box may also be positioned in front of a file download dialog box to make this more convincing. A user may also be persuaded to double-click an element of a Web page.

An attacker could exploit the vulnerability by constructing a malicious Web page that could potentially allow remote code execution if a user visited the malicious Web site. An attacker who successfully exploited this vulnerability could take complete control of an affected system. However, significant user interaction is required to exploit this vulnerability.

Mitigating Factors for File Download Dialog Box Manipulation Vulnerability - CAN-2005-2829:

  • In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's Web site. For an attack to be successful, a user would then have to interact with the Web site.
  • An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • The Restricted sites zone helps reduce attacks that could try to exploit this vulnerability by preventing Active Scripting and ActiveX Controls from being used when reading HTML e-mail messages. However, if a user clicks a link in an e-mail message, they could still be vulnerable to this issue through the Web-based attack scenario.

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

Workarounds for File Download Dialog Box Manipulation Vulnerability - CAN-2005-2829:

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 Active Scripting or disable Active Scripting in the Internet and Local intranet security zone

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

  1. In Internet Explorer, click Internet Options on the Tools menu.
  2. Click the Security tab.
  3. Click Internet, and then click Custom Level.
  4. Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK.
  5. Click Local intranet, and then click Custom Level.
  6. Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK.
  7. If you are prompted to confirm that you want to change these settings, click Yes.
  8. Click OK to return to Internet Explorer.

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

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

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

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

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

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

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

    Note Setting the level to High may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly even with the security setting set to High.
  4. Click Custom Level.
  5. Under Settings, in the Scripting section, under Active Scripting, click Prompt and then click OK.
  6. If you are prompted to confirm that you want to change these settings, click Yes.
  7. Click OK to return to Internet Explorer.

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

  • Restrict Web sites to only your trusted Web sites

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 Internet Explorer's 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, click Default Level, move the slider to Medium, and then click Sites.

    Note Setting the level to Medium is a suggested added precaution. It may cause some Web sites to work incorrectly if you have placed sites in the Trusted sites zone that require the default setting of Low.
  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.

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

FAQ for File Download Dialog Box Manipulation Vulnerability - CAN-2005-2829:

What is the scope of the vulnerability?
This is a remote code execution vulnerability that relies to a large extent on social engineering. 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. However, significant user interaction is required to exploit this vulnerability.

What causes the vulnerability?
This vulnerability relies to a large extent on social engineering and relies on the way that Internet Explorer displays file download dialog boxes and accepts user input during interaction with a Web page. This interaction could be in the form of certain keystrokes that a user makes when visiting a Web page. A custom dialog box may also be positioned in front of a file download dialog box to make this more convincing. A user may also be persuaded to double-click an element of a Web page.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system. In a Web-based attack scenario, an attacker would host a Web site that exploits this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. It could also be possible to display malicious Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.

How could an attacker exploit the vulnerability?
An attacker could host a malicious Web site that is designed to exploit this vulnerability and then persuade a user to view the Web site by using Internet Explorer. It should be noted that this vulnerability relies to a large extent on social engineering and that a user would need to interact with the attacker’s Web site.

What systems are primarily at risk from the vulnerability?
This vulnerability requires that a user is logged on and that the user visits and interacts with 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.

Are Windows 98, Windows 98 Second Edition, or Windows Millennium Edition critically affected by this vulnerability?
No. Although Windows 98, Windows 98 Second Edition, and Windows Millennium Edition do contain the affected component, the vulnerability is not critical because it requires significant user interaction. For more information about severity ratings, visit the following Web site.

What does the update do?
The update removes the vulnerability by making sure that the result of user interaction with a Web page or dialog box cannot be transferred to the file download dialog box.

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

HTTPS Proxy Vulnerability- CAN-2005-2830:

An information disclosure vulnerability exists in the way Internet Explorer behaves in certain situations where an HTTPS proxy server requires clients to use Basic authentication. This vulnerability could allow an attacker to read Web addresses in clear text sent from Internet Explorer to a proxy server despite the connection being an HTTPS connection.

Mitigating Factors for HTTPS Proxy Vulnerability- CAN-2005-2830:

  • This vulnerability only manifests itself if a client system is configured to use an authenticating proxy server that requires Basic authentication for HTTPS communications.
  • An attacker must be on the same network as the user.
  • An attacker would have no way of targeting this to a specific user. The information disclosure can happen only when a user uses an authenticating proxy server for HTTPS communications.

Workarounds for HTTPS Proxy Vulnerability- CAN-2005-2830:

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.

  • Do not use authenticating proxy servers that require Basic Authentication as a proxy for HTTPS communication

You can help protect against this vulnerability by not having proxy servers that require Basic authentication in your enterprise. Alternatively, you can make sure that you do not use authenticating proxy servers as a proxy for HTTPS communication.

Impact of Workaround: Applications that require Basic authentication might not work as unexpected.

FAQ for HTTPS Proxy Vulnerability- CAN-2005-2830:

What is the scope of the vulnerability?
This is an information disclosure vulnerability. This vulnerability could allow an attacker to read Web addresses in clear text sent from Internet Explorer to a proxy server despite the connection being an HTTPS connection. This proxy server also must require that client systems use Basic authentication to the proxy server.

What causes the vulnerability?
This vulnerability manifests itself if a client system is configured to use an authenticating proxy server that requires Basic authentication for HTTPS communications.

What might an attacker use the vulnerability to do?
This vulnerability could allow an attacker to read Web addresses in clear text sent from Internet Explorer to a proxy server despite the connection being an HTTPS connection. This proxy server also must require that client systems use Basic authentication to the proxy server.

What is HTTPS and Basic Authentication?
HTTPS is a protocol that helps secure HTTP communications. In Internet Explorer, when you visit a Web site and a yellow lock icon appears in the lower-right corner of the browser window, the current session is protected by HTTPS.

Basic authentication means that credentials are sent to the proxy server in clear text or encoded by using Base64 encoding. Base64 encoding is not an encryption technique and considered to be equal to clear text. For more information about different authentication methods, see the product documentation.

What is a Proxy Server?
A proxy server is a server configured to act on behalf of assigned clients. When a client application makes a request for an object on the Internet, a proxy server on the private network responds by translating the request and passing it to the Internet. When a computer on the Internet responds, the proxy server passes that response back to the client application on the computer that made the request.

How could an attacker exploit the vulnerability?
An attacker could analyze network traffic between a client system and a proxy server that requires Basic authentication and that also handles HTTPS connections.

What systems are primarily at risk from the vulnerability?
This vulnerability requires that a user is logged on and that the user 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.

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

What does the update do?
The update removes the vulnerability by making sure that Internet Explorer uses the HTTPS connection to the proxy server when sending URLs.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability has been publicly disclosed.

COM Object Instantiation Memory Corruption Vulnerability - CAN-2005-2831:

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 malicious Web page that could potentially allow remote code execution if a user visited the malicious Web site. An attacker who successfully exploited this vulnerability could take complete control of an affected system.

Mitigating Factors for COM Object Instantiation Memory Corruption Vulnerability - CAN-2005-2831:

  • In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's Web site.
  • An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • The Restricted sites zone helps reduce attacks that could try to exploit this vulnerability by preventing ActiveX Controls from being used when reading HTML e-mail messages. However, if a user clicks a link in an e-mail message, they could still be vulnerable to this issue through the Web-based attack scenario.

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

Workarounds for COM Object Instantiation Memory Corruption Vulnerability - CAN-2005-2831:

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 settings to prompt before running ActiveX Controls or to disable ActiveX Controls in the Internet and Local intranet security zone. To do this, follow these steps:

  1. In Internet Explorer, click Internet Options on the Tools menu.
  2. Click the Security tab.
  3. Click Internet, and then click Custom Level.
  4. Under Settings, in the 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. If you are prompted to confirm that you want to change these settings, click Yes.
  8. Click OK to return to Internet Explorer.

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

Impact of Workaround: There are side effects to prompting before running 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 "Restrict Web sites to only your trusted Web sites" workaround.

  • Set Internet and Local intranet security zone settings to “High” to prompt before running ActiveX Controls 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.
  4. Click Custom Level.
  5. Under Settings, in the Scripting section, under Active Scripting, click Prompt and then click OK.
  6. If you are prompted to confirm that you want to change these settings, click Yes.
  7. Click OK 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 "Restrict Web sites to only your trusted Web sites" workaround.

  • Restrict Web sites to only your trusted Web sites

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 Internet Explorer's 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, click Default Level, move the slider to Medium, and then click Sites.

    Note Setting the level to Medium is a suggested added precaution. It may cause some Web sites to work incorrectly if you have placed sites in the Trusted sites zone that require the default setting of Low.
  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.

Add any sites that you trust not to take malicious action on your computer. One in particular that you may want to add is "*.windowsupdate.microsoft.com" (without the quotation marks). This is the site 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 about preventing a control from running in Internet Explorer, see Microsoft Knowledge Base Article 240797. Follow these steps and create a Compatibility Flags value in the registry to prevent a COM object from being instantiated in Internet Explorer.

For example, to set the kill bit for a CLSID in the Avifil32.dll, file that is included in this security update, paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension.


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{0002000D-0000-0000-C000-000000000046}]
"Compatibility Flags"=dword:00000400

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

Group Policy collection

What is Group Policy Object Editor?

Core Group Policy tools and settings

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

Impact of Workaround: 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 - CAN-2005-2831:

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 take complete control of the affected system. In a Web-based attack scenario, an attacker would host a Web site that exploits this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. It could also be possible to display malicious Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.

How could an attacker exploit the vulnerability?
An attacker could host a malicious Web site that is designed to exploit this vulnerability through Internet Explorer and then persuade a user to view the Web site.

What systems are primarily at risk from the vulnerability?
This vulnerability requires that a user is logged on and reading e-mail messages or that a user is logged on and visits a Web site for any malicious action to occur. Therefore, any systems where e-mail messages are read or where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability.

Are Windows 98, Windows 98 Second Edition or Windows Millennium Edition critically affected by this vulnerability?
Yes. Windows 98, Windows 98 Second Edition, and Windows Millennium Edition are critically affected by this vulnerability. The security updates are available from the Windows Update Web site. For more information about severity ratings, visit 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) in 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-052. 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 COM objects are as follows.

Class Identifier COM object
0002000D-0000-0000-C000-000000000046Avifil32.dll
ECABAFC0-7F19-11D2-978E-0000F8757E2AComsvcs.dll
ECABB0AB-7F19-11D2-978E-0000F8757E2AComsvcs.dll
3050F4F5-98B5-11CF-BB82-00AA00BDCE0BMshtmled.dll
00020421-0000-0000-C000-000000000046Ole2disp.dll
00020422-0000-0000-C000-000000000046Ole2disp.dll
00020423-0000-0000-C000-000000000046Ole2disp.dll
00020424-0000-0000-C000-000000000046Ole2disp.dll
00020425-0000-0000-C000-000000000046Ole2disp.dll
DF0B3D60-548F-101B-8E65-08002B2BD119Ole2disp.dll / Oleaut32.dll
0006F071-0000-0000-C000-000000000046Outllib.dll
2D2E24CB-0CD5-458F-86EA-3E6FA22C8E64Quartz.dll
51B4ABF3-748F-4E3B-A276-C828330E926AQuartz.dll
E4979309-7A32-495E-8A92-7B014AAD4961Quartz.dll
62EC9F22-5E30-11D2-97A1-00C04FB6DD9ARepodbc.dll
6E2270FB-F799-11CF-9227-00AA00A1EB95Repodbc.dll
6E227109-F799-11CF-9227-00AA00A1EB95Repodbc.dll
6E22710A-F799-11CF-9227-00AA00A1EB95Repodbc.dll
6E22710B-F799-11CF-9227-00AA00A1EB95Repodbc.dll
6E22710C-F799-11CF-9227-00AA00A1EB95Repodbc.dll
6E22710D-F799-11CF-9227-00AA00A1EB95Repodbc.dll
6E22710E-F799-11CF-9227-00AA00A1EB95Repodbc.dll
6E22710F-F799-11CF-9227-00AA00A1EB95Repodbc.dll
B1D4ED44-EE64-11D0-97E6-00C04FC30B4ARepodbc.dll
D675E22B-CAE9-11D2-AF7B-00C04F99179FRepodbc.dll
00021401-0000-0000-C000-000000000046Shell.dll

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

How does this vulnerability relate to one of the vulnerabilities that are corrected by MS05-038 and MS05-052?
Both security bulletins address COM object Instantiation Memory Corruption vulnerabilities. However, this update also addresses new CLSIDs that were not addressed as part of MS05-038 and MS05-052. MS05-038 and MS05-052 help protect against exploitation of the CLSIDs that are discussed in those bulletins.

Mismatched Document Object Model Objects Memory Corruption Vulnerability - CAN-2005-1790:

A remote code execution vulnerability exists in the way Internet Explorer handles mismatched Document Object Model objects. An attacker could exploit the vulnerability by constructing a malicious Web page that could potentially allow remote code execution if a user visited the malicious Web site. An attacker who successfully exploited this vulnerability could take complete control of an affected system.

Mitigating Factors for Mismatched Document Object Model Objects Memory Corruption Vulnerability - CAN-2005-1790:

  • In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's Web site.
  • An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • The Restricted sites zone helps reduce attacks that could try to exploit this vulnerability by preventing ActiveX Controls from being used when reading HTML e-mail messages. However, if a user clicks a link in an e-mail message, they could still be vulnerable to this issue through the Web-based attack scenario.

    By default, Outlook Express 6, Outlook 2002, and Outlook 2003 open HTML e-mail messages in the Restricted sites zone. Additionally, Outlook 98, and Outlook 2000 open HTML e-mail messages in the Restricted sites zone if the Outlook E-mail Security Update has been installed. Outlook Express 5.5 Service Pack 2 opens HTML e-mail messages in the Restricted sites zone if Microsoft Security Bulletin MS04-018 has been installed.
  • By default, Internet Explorer on Windows Server 2003 runs in a restricted mode that is known as Enhanced Security Configuration. This mode mitigates this vulnerability. See the FAQ section of this bulletin for more information about Internet Explorer Enhanced Security Configuration.

Workarounds for Mismatched Document Object Model Objects Memory Corruption Vulnerability - CAN-2005-1790:

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 Active Scripting or disable Active Scripting in the Internet and Local intranet security zone

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

  1. In Internet Explorer, click Internet Options on the Tools menu.
  2. Click the Security tab.
  3. Click Internet, and then click Custom Level.
  4. Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK.
  5. Click Local intranet, and then click Custom Level.
  6. Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK.
  7. If you are prompted to confirm that you want to change these settings, click Yes.
  8. Click OK to return to Internet Explorer.

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

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

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

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

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

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

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

    Note Setting the level to High may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly even with the security setting set to High.
  4. Click Custom Level.
  5. Under Settings, in the Scripting section, under Active Scripting, click Prompt and then click OK.
  6. If you are prompted to confirm that you want to change these settings, click Yes.
  7. Click OK to return to Internet Explorer.

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

  • Restrict Web sites to only your trusted Web sites

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 Internet Explorer's 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, click Default Level, move the slider to Medium, and then click Sites.

    Note Setting the level to Medium is a suggested added precaution. It may cause some Web sites to work incorrectly if you have placed sites in the Trusted sites zone that require the default setting of Low.
  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.

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

FAQ for Mismatched Document Object Model Objects Memory Corruption Vulnerability - CAN-2005-1790:

What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could remotely take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability?
When Internet Explorer handles mismatched Document Object Model objects it may corrupt system memory in such a way that an attacker could execute arbitrary code.

For example, when Internet Explorer displays a Web page that contains an onLoad event that points to a Window object, system memory may be corrupted 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 take complete control of the affected system. In a Web-based attack scenario, an attacker would host a Web site that exploits this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. It could also be possible to display malicious Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.

How could an attacker exploit the vulnerability?
An attacker could host a malicious Web site that is designed to exploit this vulnerability through Internet Explorer and then persuade a user to view the Web site.

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.

Are Windows 98, Windows 98 Second Edition or Windows Millennium Edition critically affected by this vulnerability?
Yes. Windows 98, Windows 98 Second Edition, and Windows Millennium Edition are critically affected by this vulnerability. The security updates are available from the Windows Update Web site. For more information about severity ratings, visit the following Web site.

What does the update do?
The update removes the vulnerability by modifying the way that Internet Explorer handles Mismatched Document Object Model Objects.

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 CAN-2005-1790.

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

Does applying this security update help protect customers from the code that has been published publicly that attempts to exploit this vulnerability?
Yes. This security update addresses the vulnerability that is currently being exploited. The vulnerability that has been addressed has been assigned the Common Vulnerability and Exposure number CAN-2005-1790.

Affected Software:

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

Windows Server 2003 (all versions)

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

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 the following command at a command prompt for Windows Server 2003:

Windowsserver2003-kb905915-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 KB905915.log file for any failure messages when they use this switch.

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

Windowsserver2003-kb905915-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 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%\$NTUninstallKB905915$\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.

Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Datacenter Edition; Windows Server 2003, Enterprise Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; Windows Server 2003, Datacenter Edition with SP1; Windows Server 2003 R2, Web Edition; Windows Server 2003 R2, Standard Edition; Windows Server 2003 R2, Datacenter Edition; Windows Server 2003 R2, Enterprise Edition; Windows Small Business Server 2003 R2:

File NameVersionDateTimeSizeFolder
Browseui.dll6.0.3790.43907-Nov-200510:191,057,280RTMGDR
Cdfview.dll6.0.3790.43907-Nov-200510:19147,968RTMGDR
Danim.dll6.3.1.14807-Nov-200510:19993,280RTMGDR
Digest.dll6.0.3790.43907-Nov-200510:1959,904RTMGDR
Dxtrans.dll6.3.3790.43907-Nov-200510:19205,312RTMGDR
Iepeers.dll6.0.3790.43907-Nov-200510:19238,080RTMGDR
Inseng.dll6.0.3790.43907-Nov-200510:1973,216RTMGDR
Mshtml.dll6.0.3790.44924-Nov-200500:542,932,224RTMGDR
Mshtmled.dll6.0.3790.43907-Nov-200510:19454,144RTMGDR
Msrating.dll6.0.3790.43907-Nov-200510:19135,680RTMGDR
Mstime.dll6.0.3790.43907-Nov-200510:19503,296RTMGDR
Pngfilt.dll5.2.3790.43907-Nov-200510:1940,448RTMGDR
Shdocvw.dll6.0.3790.44901-Dec-200515:171,396,736RTMGDR
Shlwapi.dll6.0.3790.43907-Nov-200510:19287,744RTMGDR
Urlmon.dll6.0.3790.43907-Nov-200510:19526,848RTMGDR
Wininet.dll6.0.3790.43907-Nov-200510:19626,176RTMGDR
Browseui.dll6.0.3790.43907-Nov-200510:231,057,280RTMQFE
Cdfview.dll6.0.3790.43907-Nov-200510:23147,968RTMQFE
Danim.dll6.3.1.14807-Nov-200510:23993,280RTMQFE
Digest.dll6.0.3790.43907-Nov-200510:2359,904RTMQFE
Dxtrans.dll6.3.3790.43907-Nov-200510:23205,312RTMQFE
Iepeers.dll6.0.3790.43907-Nov-200510:23238,592RTMQFE
Inseng.dll6.0.3790.43907-Nov-200510:2373,216RTMQFE
Mshtml.dll6.0.3790.44924-Nov-200501:002,934,784RTMQFE
Mshtmled.dll6.0.3790.43907-Nov-200510:23454,144RTMQFE
Msrating.dll6.0.3790.43907-Nov-200510:23135,680RTMQFE
Mstime.dll6.0.3790.43907-Nov-200510:23503,296RTMQFE
Pngfilt.dll5.2.3790.43907-Nov-200510:2340,448RTMQFE
Shdocvw.dll6.0.3790.44901-Dec-200515:241,398,272RTMQFE
Shlwapi.dll6.0.3790.43907-Nov-200510:23287,744RTMQFE
Urlmon.dll6.0.3790.43907-Nov-200510:23526,848RTMQFE
Wininet.dll6.0.3790.43907-Nov-200510:23628,224RTMQFE
Browseui.dll6.0.3790.256407-Nov-200510:191,036,288SP1GDR
Danim.dll6.3.1.14807-Nov-200510:191,058,304SP1GDR
Dxtrans.dll6.3.3790.256407-Nov-200510:19212,480SP1GDR
Iedw.exe5.2.3790.256405-Nov-200501:4717,920SP1GDR
Iepeers.dll6.0.3790.256407-Nov-200510:19253,952SP1GDR
Mshtml.dll6.0.3790.257724-Nov-200501:063,112,448SP1GDR
Mstime.dll6.0.3790.256407-Nov-200510:19536,064SP1GDR
Pngfilt.dll5.2.3790.256407-Nov-200510:1942,496SP1GDR
Shdocvw.dll6.0.3790.258001-Dec-200515:131,513,472SP1GDR
Shlwapi.dll6.0.3790.256407-Nov-200510:19321,536SP1GDR
Urlmon.dll6.0.3790.256407-Nov-200510:19691,200SP1GDR
Wininet.dll6.0.3790.256407-Nov-200510:19662,528SP1GDR
Browseui.dll6.0.3790.256407-Nov-200510:351,036,288SP1QFE
Danim.dll6.3.1.14807-Nov-200510:351,058,304SP1QFE
Dxtrans.dll6.3.3790.256407-Nov-200510:35212,480SP1QFE
Iedw.exe5.2.3790.256405-Nov-200502:0017,920SP1QFE
Iepeers.dll6.0.3790.256407-Nov-200510:35253,952SP1QFE
Mshtml.dll6.0.3790.257724-Nov-200501:363,112,960SP1QFE
Mstime.dll6.0.3790.256407-Nov-200510:35536,064SP1QFE
Pngfilt.dll5.2.3790.256407-Nov-200510:3542,496SP1QFE
Shdocvw.dll6.0.3790.258001-Dec-200515:191,513,472SP1QFE
Shlwapi.dll6.0.3790.256407-Nov-200510:35321,536SP1QFE
Urlmon.dll6.0.3790.256407-Nov-200510:35691,200SP1QFE
Wininet.dll6.0.3790.256407-Nov-200510:35664,064SP1QFE
Updspapi.dll6.2.29.012-Oct-200523:15371,424

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.43924-Nov-200501:552,536,960IA-64RTMGDR
Cdfview.dll6.0.3790.43924-Nov-200501:55303,616IA-64RTMGDR
Digest.dll6.0.3790.43924-Nov-200501:55141,312IA-64RTMGDR
Dxtrans.dll6.3.3790.43924-Nov-200501:55585,728IA-64RTMGDR
Iepeers.dll6.0.3790.43924-Nov-200501:55674,816IA-64RTMGDR
Inseng.dll6.0.3790.43924-Nov-200501:55217,600IA-64RTMGDR
Mshtml.dll6.0.3790.44924-Nov-200501:558,238,592IA-64RTMGDR
Mshtmled.dll6.0.3790.43924-Nov-200501:551,409,536IA-64RTMGDR
Msrating.dll6.0.3790.43924-Nov-200501:55387,584IA-64RTMGDR
Mstime.dll6.0.3790.43924-Nov-200501:551,661,440IA-64RTMGDR
Pngfilt.dll5.2.3790.43924-Nov-200501:55105,984IA-64RTMGDR
Shdocvw.dll6.0.3790.44901-Dec-200504:253,371,520IA-64RTMGDR
Shlwapi.dll6.0.3790.43924-Nov-200501:55740,352IA-64RTMGDR
Urlmon.dll6.0.3790.43924-Nov-200501:551,297,408IA-64RTMGDR
Wininet.dll6.0.3790.43924-Nov-200501:551,506,304IA-64RTMGDR
Wbrowseui.dll6.0.3790.43924-Nov-200501:551,057,280x86RTMGDR\WOW
Wcdfview.dll6.0.3790.43924-Nov-200501:55147,968x86RTMGDR\WOW
Wdanim.dll6.3.1.14824-Nov-200501:55993,280x86RTMGDR\WOW
Wdxtrans.dll6.3.3790.43924-Nov-200501:55205,312x86RTMGDR\WOW
Wiepeers.dll6.0.3790.43924-Nov-200501:55238,080x86RTMGDR\WOW
Winseng.dll6.0.3790.43924-Nov-200501:5573,216x86RTMGDR\WOW
Wmshtml.dll6.0.3790.44924-Nov-200501:552,932,224x86RTMGDR\WOW
Wmshtmled.dll6.0.3790.43924-Nov-200501:55454,144x86RTMGDR\WOW
Wmsrating.dll6.0.3790.43924-Nov-200501:55135,680x86RTMGDR\WOW
Wmstime.dll6.0.3790.43924-Nov-200501:55503,296x86RTMGDR\WOW
Wpngfilt.dll5.2.3790.43924-Nov-200501:5540,448x86RTMGDR\WOW
Wshdocvw.dll6.0.3790.44901-Dec-200504:261,396,736x86RTMGDR\WOW
Wshlwapi.dll6.0.3790.43924-Nov-200501:55287,744x86RTMGDR\WOW
Wurlmon.dll6.0.3790.43924-Nov-200501:55526,848x86RTMGDR\WOW
Wwdigest.dll6.0.3790.43924-Nov-200501:5559,904x86RTMGDR\WOW
Wwininet.dll6.0.3790.43924-Nov-200501:55626,176x86RTMGDR\WOW
Browseui.dll6.0.3790.43924-Nov-200501:582,538,496IA-64RTMQFE
Cdfview.dll6.0.3790.43924-Nov-200501:58303,616IA-64RTMQFE
Digest.dll6.0.3790.43924-Nov-200501:58141,312IA-64RTMQFE
Dxtrans.dll6.3.3790.43924-Nov-200501:58586,752IA-64RTMQFE
Iepeers.dll6.0.3790.43924-Nov-200501:58678,400IA-64RTMQFE
Inseng.dll6.0.3790.43924-Nov-200501:58217,600IA-64RTMQFE
Mshtml.dll6.0.3790.44924-Nov-200501:588,242,176IA-64RTMQFE
Mshtmled.dll6.0.3790.43924-Nov-200501:581,409,536IA-64RTMQFE
Msrating.dll6.0.3790.43924-Nov-200501:58387,584IA-64RTMQFE
Mstime.dll6.0.3790.43924-Nov-200501:581,661,440IA-64RTMQFE
Pngfilt.dll5.2.3790.43924-Nov-200501:58105,984IA-64RTMQFE
Shdocvw.dll6.0.3790.44901-Dec-200504:273,375,616IA-64RTMQFE
Shlwapi.dll6.0.3790.43924-Nov-200501:58740,352IA-64RTMQFE
Urlmon.dll6.0.3790.43924-Nov-200501:581,297,408IA-64RTMQFE
Wininet.dll6.0.3790.43924-Nov-200501:581,510,400IA-64RTMQFE
Wbrowseui.dll6.0.3790.43924-Nov-200501:581,057,280x86RTMQFE\WOW
Wcdfview.dll6.0.3790.43924-Nov-200501:58147,968x86RTMQFE\WOW
Wdanim.dll6.3.1.14824-Nov-200501:58993,280x86RTMQFE\WOW
Wdxtrans.dll6.3.3790.43924-Nov-200501:58205,312x86RTMQFE\WOW
Wiepeers.dll6.0.3790.43924-Nov-200501:58238,592x86RTMQFE\WOW
Winseng.dll6.0.3790.43924-Nov-200501:5873,216x86RTMQFE\WOW
Wmshtml.dll6.0.3790.44924-Nov-200501:582,934,784x86RTMQFE\WOW
Wmshtmled.dll6.0.3790.43924-Nov-200501:58454,144x86RTMQFE\WOW
Wmsrating.dll6.0.3790.43924-Nov-200501:58135,680x86RTMQFE\WOW
Wmstime.dll6.0.3790.43924-Nov-200501:58503,296x86RTMQFE\WOW
Wpngfilt.dll5.2.3790.43924-Nov-200501:5840,448x86RTMQFE\WOW
Wshdocvw.dll6.0.3790.44901-Dec-200504:291,398,272x86RTMQFE\WOW
Wshlwapi.dll6.0.3790.43924-Nov-200501:58287,744x86RTMQFE\WOW
Wurlmon.dll6.0.3790.43924-Nov-200501:58526,848x86RTMQFE\WOW
Wwdigest.dll6.0.3790.43924-Nov-200501:5859,904x86RTMQFE\WOW
Wwininet.dll6.0.3790.43924-Nov-200501:58628,224x86RTMQFE\WOW
Browseui.dll6.0.3790.256424-Nov-200501:532,546,688IA-64SP1GDR
Dxtrans.dll6.3.3790.256424-Nov-200501:53641,024IA-64SP1GDR
Iepeers.dll6.0.3790.256424-Nov-200501:53718,336IA-64SP1GDR
Mshtml.dll6.0.3790.257724-Nov-200501:539,290,240IA-64SP1GDR
Mstime.dll6.0.3790.256424-Nov-200501:531,843,200IA-64SP1GDR
Pngfilt.dll5.2.3790.256424-Nov-200501:53116,736IA-64SP1GDR
Shdocvw.dll6.0.3790.258001-Dec-200504:343,679,232IA-64SP1GDR
Shlwapi.dll6.0.3790.256424-Nov-200501:53824,320IA-64SP1GDR
Urlmon.dll6.0.3790.256424-Nov-200501:531,604,608IA-64SP1GDR
Wininet.dll6.0.3790.256424-Nov-200501:531,697,792IA-64SP1GDR
Wbrowseui.dll6.0.3790.256424-Nov-200501:531,036,288x86SP1GDR\WOW
Wdanim.dll6.3.1.14824-Nov-200501:531,058,304x86SP1GDR\WOW
Wdxtrans.dll6.3.3790.256424-Nov-200501:53212,480x86SP1GDR\WOW
Wiedw.exe5.2.3790.256424-Nov-200501:5317,920x86SP1GDR\WOW
Wiepeers.dll6.0.3790.256424-Nov-200501:53253,952x86SP1GDR\WOW
Wmshtml.dll6.0.3790.257724-Nov-200501:533,112,448x86SP1GDR\WOW
Wmstime.dll6.0.3790.256424-Nov-200501:53536,064x86SP1GDR\WOW
Wpngfilt.dll5.2.3790.256424-Nov-200501:5342,496x86SP1GDR\WOW
Wshdocvw.dll6.0.3790.258001-Dec-200504:341,513,472x86SP1GDR\WOW
Wshlwapi.dll6.0.3790.256424-Nov-200501:53321,536x86SP1GDR\WOW
Wurlmon.dll6.0.3790.256424-Nov-200501:53691,200x86SP1GDR\WOW
Wwininet.dll6.0.3790.256424-Nov-200501:53662,528x86SP1GDR\WOW
Browseui.dll6.0.3790.256424-Nov-200502:002,546,688IA-64SP1QFE
Dxtrans.dll6.3.3790.256424-Nov-200502:00641,024IA-64SP1QFE
Iepeers.dll6.0.3790.256424-Nov-200502:00718,336IA-64SP1QFE
Mshtml.dll6.0.3790.257724-Nov-200502:009,291,776IA-64SP1QFE
Mstime.dll6.0.3790.256424-Nov-200502:001,843,200IA-64SP1QFE
Pngfilt.dll5.2.3790.256424-Nov-200502:00116,736IA-64SP1QFE
Shdocvw.dll6.0.3790.258001-Dec-200504:373,680,256IA-64SP1QFE
Shlwapi.dll6.0.3790.256424-Nov-200502:00824,320IA-64SP1QFE
Urlmon.dll6.0.3790.256424-Nov-200502:001,604,608IA-64SP1QFE
Wininet.dll6.0.3790.256424-Nov-200502:001,700,352IA-64SP1QFE
Wbrowseui.dll6.0.3790.256424-Nov-200502:001,036,288x86SP1QFE\WOW
Wdanim.dll6.3.1.14824-Nov-200502:001,058,304x86SP1QFE\WOW
Wdxtrans.dll6.3.3790.256424-Nov-200502:00212,480x86SP1QFE\WOW
Wiedw.exe5.2.3790.256424-Nov-200502:0017,920x86SP1QFE\WOW
Wiepeers.dll6.0.3790.256424-Nov-200502:00253,952x86SP1QFE\WOW
Wmshtml.dll6.0.3790.257724-Nov-200502:003,112,960x86SP1QFE\WOW
Wmstime.dll6.0.3790.256424-Nov-200502:00536,064x86SP1QFE\WOW
Wpngfilt.dll5.2.3790.256424-Nov-200502:0042,496x86SP1QFE\WOW
Wshdocvw.dll6.0.3790.258001-Dec-200504:391,513,472x86SP1QFE\WOW
Wshlwapi.dll6.0.3790.256424-Nov-200502:00321,536x86SP1QFE\WOW
Wurlmon.dll6.0.3790.256424-Nov-200502:00691,200x86SP1QFE\WOW
Wwininet.dll6.0.3790.256424-Nov-200502:00664,064x86SP1QFE\WOW
Updspapi.dll6.2.29.012-Oct-200523:15638,688IA-64

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.256424-Nov-200501:531,604,096SP1GDR
Danim.dll6.3.1.14824-Nov-200501:531,989,120SP1GDR
Dxtrans.dll6.3.3790.256424-Nov-200501:53332,288SP1GDR
Iepeers.dll6.0.3790.256424-Nov-200501:53369,664SP1GDR
Mshtml.dll6.0.3790.257724-Nov-200501:535,934,592SP1GDR
Mstime.dll6.0.3790.256424-Nov-200501:53898,560SP1GDR
Pngfilt.dll5.2.3790.256424-Nov-200501:5364,000SP1GDR
Shdocvw.dll6.0.3790.258001-Dec-200504:352,434,048SP1GDR
Shlwapi.dll6.0.3790.256424-Nov-200501:53621,568SP1GDR
Urlmon.dll6.0.3790.256424-Nov-200501:531,076,736SP1GDR
Wininet.dll6.0.3790.256424-Nov-200501:531,187,840SP1GDR
Wbrowseui.dll6.0.3790.256424-Nov-200501:531,036,288x86SP1GDR\WOW
Wdanim.dll6.3.1.14824-Nov-200501:531,058,304x86SP1GDR\WOW
Wdxtrans.dll6.3.3790.256424-Nov-200501:53212,480x86SP1GDR\WOW
Wiedw.exe5.2.3790.256424-Nov-200501:5317,920x86SP1GDR\WOW
Wiepeers.dll6.0.3790.256424-Nov-200501:53253,952x86SP1GDR\WOW
Wmshtml.dll6.0.3790.257724-Nov-200501:533,112,448x86SP1GDR\WOW
Wmstime.dll6.0.3790.256424-Nov-200501:53536,064x86SP1GDR\WOW
Wpngfilt.dll5.2.3790.256424-Nov-200501:5342,496x86SP1GDR\WOW
Wshdocvw.dll6.0.3790.258001-Dec-200504:341,513,472x86SP1GDR\WOW
Wshlwapi.dll6.0.3790.256424-Nov-200501:53321,536x86SP1GDR\WOW
Wurlmon.dll6.0.3790.256424-Nov-200501:53691,200x86SP1GDR\WOW
Wwininet.dll6.0.3790.256424-Nov-200501:53662,528x86SP1GDR\WOW
Browseui.dll6.0.3790.256424-Nov-200501:551,604,096SP1QFE
Danim.dll6.3.1.14824-Nov-200501:551,989,120SP1QFE
Dxtrans.dll6.3.3790.256424-Nov-200501:55332,288SP1QFE
Iepeers.dll6.0.3790.256424-Nov-200501:55369,664SP1QFE
Mshtml.dll6.0.3790.257724-Nov-200501:555,935,616SP1QFE
Mstime.dll6.0.3790.256424-Nov-200501:55898,560SP1QFE
Pngfilt.dll5.2.3790.256424-Nov-200501:5564,000SP1QFE
Shdocvw.dll6.0.3790.258001-Dec-200504:402,434,560SP1QFE
Shlwapi.dll6.0.3790.256424-Nov-200501:55621,568SP1QFE
Urlmon.dll6.0.3790.256424-Nov-200501:551,076,736SP1QFE
Wininet.dll6.0.3790.256424-Nov-200501:551,187,840SP1QFE
Wbrowseui.dll6.0.3790.256424-Nov-200501:551,036,288x86SP1QFE\WOW
Wdanim.dll6.3.1.14824-Nov-200501:551,058,304x86SP1QFE\WOW
Wdxtrans.dll6.3.3790.256424-Nov-200501:55212,480x86SP1QFE\WOW
Wiedw.exe5.2.3790.256424-Nov-200501:5517,920x86SP1QFE\WOW
Wiepeers.dll6.0.3790.256424-Nov-200501:55253,952x86SP1QFE\WOW
Wmshtml.dll6.0.3790.257724-Nov-200501:553,112,960x86SP1QFE\WOW
Wmstime.dll6.0.3790.256424-Nov-200501:55536,064x86SP1QFE\WOW
Wpngfilt.dll5.2.3790.256424-Nov-200501:5542,496x86SP1QFE\WOW
Wshdocvw.dll6.0.3790.258001-Dec-200504:391,513,472x86SP1QFE\WOW
Wshlwapi.dll6.0.3790.256424-Nov-200501:55321,536x86SP1QFE\WOW
Wurlmon.dll6.0.3790.256424-Nov-200501:55691,200x86SP1QFE\WOW
Wwininet.dll6.0.3790.256424-Nov-200501:55664,064x86SP1QFE\WOW
Updspapi.dll6.2.29.012-Oct-200523:14462,048

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.

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

Verifying that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

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

  • Registry Key Verification

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

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

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP2\KB905915\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 905915 security update into the Windows installation source files.

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

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, 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 the following command at a command prompt for Microsoft Windows XP:

Windowsxp-kb905915-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 KB905915.log file for any failure messages when they use this switch.

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

Windowsxp-kb905915-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%\$NTUninstallKB905915$\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.

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 NameVersionDateTimeSizeCPUFolder
Browseui.dll6.0.2900.280224-Nov-200501:061,022,464x86SP2GDR
Cdfview.dll6.0.2900.278121-Oct-200503:39151,040x86SP2GDR
Danim.dll6.3.1.14805-Nov-200503:161,054,208x86SP2GDR
Dxtrans.dll6.3.2900.278121-Oct-200503:39205,312x86SP2GDR
Extmgr.dll6.0.2900.278121-Oct-200503:3955,808x86SP2GDR
Iedw.exe5.1.2600.278121-Oct-200501:4518,432x86SP2GDR
Iepeers.dll6.0.2900.278121-Oct-200503:39251,392x86SP2GDR
Inseng.dll6.0.2900.278121-Oct-200503:3996,256x86SP2GDR
Mshtml.dll6.0.2900.280224-Nov-200501:063,015,680x86SP2GDR
Mshtmled.dll6.0.2900.278121-Oct-200503:39448,512x86SP2GDR
Msrating.dll6.0.2900.278121-Oct-200503:39146,432x86SP2GDR
Mstime.dll6.0.2900.278121-Oct-200503:39530,944SP2GDR
Pngfilt.dll6.0.2900.278121-Oct-200503:3939,424x86SP2GDR
Shdocvw.dll6.0.2900.280501-Dec-200503:591,492,480x86SP2GDR
Shlwapi.dll6.0.2900.278121-Oct-200503:39473,600x86SP2GDR
Urlmon.dll6.0.2900.279005-Nov-200503:16609,280x86SP2GDR
Wininet.dll6.0.2900.278121-Oct-200503:39658,432x86SP2GDR
Browseui.dll6.0.2900.280224-Nov-200501:071,022,464x86SP2QFE
Cdfview.dll6.0.2900.278121-Oct-200503:38151,040x86SP2QFE
Danim.dll6.3.1.14805-Nov-200503:341,054,208x86SP2QFE
Dxtrans.dll6.3.2900.278121-Oct-200503:38205,312x86SP2QFE
Extmgr.dll6.0.2900.278121-Oct-200503:3855,808x86SP2QFE
Iedw.exe5.1.2600.278121-Oct-200501:5418,432x86SP2QFE
Iepeers.dll6.0.2900.278121-Oct-200503:38251,904x86SP2QFE
Inseng.dll6.0.2900.278121-Oct-200503:3896,256x86SP2QFE
Mshtml.dll6.0.2900.280224-Nov-200501:073,018,240x86SP2QFE
Mshtmled.dll6.0.2900.278121-Oct-200503:38448,512x86SP2QFE
Msrating.dll6.0.2900.278121-Oct-200503:38146,432x86SP2QFE
Mstime.dll6.0.2900.278121-Oct-200503:38530,944SP2QFE
Pngfilt.dll6.0.2900.278121-Oct-200503:3839,424x86SP2QFE
Shdocvw.dll6.0.2900.280501-Dec-200504:051,495,040x86SP2QFE
Shlwapi.dll6.0.2900.278121-Oct-200503:38474,112x86SP2QFE
Urlmon.dll6.0.2900.279005-Nov-200503:34610,304x86SP2QFE
Wininet.dll6.0.2900.278121-Oct-200503:38661,504x86SP2QFE
Updspapi.dll6.2.29.012-Oct-200523:12371,424x86

Windows XP Professional x64:

File NameVersionDateTimeSizeCPUFolder
Browseui.dll6.0.3790.256424-Nov-200501:531,604,096SP1GDR
Danim.dll6.3.1.14824-Nov-200501:531,989,120SP1GDR
Dxtrans.dll6.3.3790.256424-Nov-200501:53332,288SP1GDR
Iepeers.dll6.0.3790.256424-Nov-200501:53369,664SP1GDR
Mshtml.dll6.0.3790.257724-Nov-200501:535,934,592SP1GDR
Mstime.dll6.0.3790.256424-Nov-200501:53898,560SP1GDR
Pngfilt.dll5.2.3790.256424-Nov-200501:5364,000SP1GDR
Shdocvw.dll6.0.3790.256424-Nov-200501:532,433,536SP1GDR
Shlwapi.dll6.0.3790.256424-Nov-200501:53621,568SP1GDR
Urlmon.dll6.0.3790.256424-Nov-200501:531,076,736SP1GDR
Wininet.dll6.0.3790.256424-Nov-200501:531,187,840SP1GDR
Wbrowseui.dll6.0.3790.256424-Nov-200501:531,036,288x86SP1GDR\WOW
Wdanim.dll6.3.1.14824-Nov-200501:531,058,304x86SP1GDR\WOW
Wdxtrans.dll6.3.3790.256424-Nov-200501:53212,480x86SP1GDR\WOW
Wiedw.exe5.2.3790.256424-Nov-200501:5317,920x86SP1GDR\WOW
Wiepeers.dll6.0.3790.256424-Nov-200501:53253,952x86SP1GDR\WOW
Wmshtml.dll6.0.3790.257724-Nov-200501:533,112,448x86SP1GDR\WOW
Wmstime.dll6.0.3790.256424-Nov-200501:53536,064x86SP1GDR\WOW
Wpngfilt.dll5.2.3790.256424-Nov-200501:5342,496x86SP1GDR\WOW
Wshdocvw.dll6.0.3790.256424-Nov-200501:531,512,960x86SP1GDR\WOW
Wshlwapi.dll6.0.3790.256424-Nov-200501:53321,536x86SP1GDR\WOW
Wurlmon.dll6.0.3790.256424-Nov-200501:53691,200x86SP1GDR\WOW
Wwininet.dll6.0.3790.256424-Nov-200501:53662,528x86SP1GDR\WOW
Browseui.dll6.0.3790.256424-Nov-200501:551,604,096SP1QFE
Danim.dll6.3.1.14824-Nov-200501:551,989,120SP1QFE
Dxtrans.dll6.3.3790.256424-Nov-200501:55332,288SP1QFE
Iepeers.dll6.0.3790.256424-Nov-200501:55369,664SP1QFE
Mshtml.dll6.0.3790.257724-Nov-200501:555,935,616SP1QFE
Mstime.dll6.0.3790.256424-Nov-200501:55898,560SP1QFE
Pngfilt.dll5.2.3790.256424-Nov-200501:5564,000SP1QFE
Shdocvw.dll6.0.3790.256424-Nov-200501:552,434,048SP1QFE
Shlwapi.dll6.0.3790.256424-Nov-200501:55621,568SP1QFE
Urlmon.dll6.0.3790.256424-Nov-200501:551,076,736SP1QFE
Wininet.dll6.0.3790.256424-Nov-200501:551,187,840SP1QFE
Wbrowseui.dll6.0.3790.256424-Nov-200501:551,036,288x86SP1QFE\WOW
Wdanim.dll6.3.1.14824-Nov-200501:551,058,304x86SP1QFE\WOW
Wdxtrans.dll6.3.3790.256424-Nov-200501:55212,480x86SP1QFE\WOW
Wiedw.exe5.2.3790.256424-Nov-200501:5517,920x86SP1QFE\WOW
Wiepeers.dll6.0.3790.256424-Nov-200501:55253,952x86SP1QFE\WOW
Wmshtml.dll6.0.3790.257724-Nov-200501:553,112,960x86SP1QFE\WOW
Wmstime.dll6.0.3790.256424-Nov-200501:55536,064x86SP1QFE\WOW
Wpngfilt.dll5.2.3790.256424-Nov-200501:5542,496x86SP1QFE\WOW
Wshdocvw.dll6.0.3790.256424-Nov-200501:551,513,472x86SP1QFE\WOW
Wshlwapi.dll6.0.3790.256424-Nov-200501:55321,536x86SP1QFE\WOW
Wurlmon.dll6.0.3790.256424-Nov-200501:55691,200x86SP1QFE\WOW
Wwininet.dll6.0.3790.256424-Nov-200501:55664,064x86SP1QFE\WOW
Updspapi.dll6.2.29.024-Nov-200501:58462,048

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.

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

Verifying that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

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

  • File Version Verification

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

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

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

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

Windows XP 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\KB905915\Filelist

Windows XP Professional x64 Edition:

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

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

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

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

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

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

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

Installation Information

This security update supports the following setup switches.

Supported Security Update Installation Switches
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 the following command at a command prompt for Windows XP Service Pack 1:

IE6.0sp1-KB905915-Windows-2000-XP-x86-enu /quiet

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

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

IE6.0sp1-KB905915-Windows-2000-XP-x86-enu /norestart

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

Restart Requirement

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%\$NTUninstallKB905915-IE6SP1-20051122.175908$\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.

Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows 2000 Service Pack 4 and Small Business Server 2000:

File NameVersionDateTimeSizeFolder
Browseui.dll6.0.2800.169218-Jun-200507:161,017,856RTMGDR
Cdfview.dll6.0.2800.161208-Dec-200401:43143,360RTMGDR
Danim.dll6.3.1.14821-Oct-200503:08986,112RTMGDR
Dxtrans.dll6.3.2800.152521-Oct-200520:49192,512RTMGDR
Iepeers.dll6.0.2800.149618-Feb-200520:43236,032RTMGDR
Inseng.dll6.0.2800.146926-Aug-200417:5369,632RTMGDR
Mshtml.dll6.0.2800.152823-Nov-200500:492,700,288RTMGDR
Msrating.dll6.0.2800.162324-Feb-200519:54132,096RTMGDR
Mstime.dll6.0.2800.152521-Oct-200520:49496,640RTMGDR
Pngfilt.dll6.0.2800.150527-Apr-200517:5334,816RTMGDR
Shdocvw.dll6.0.2800.176221-Oct-200523:171,339,392RTMGDR
Shlwapi.dll6.0.2800.174001-Sep-200501:49409,088RTMGDR
Urlmon.dll6.0.2800.152521-Oct-200520:51459,776RTMGDR
Wininet.dll6.0.2800.152521-Oct-200520:51575,488RTMGDR
Browseui.dll6.0.2800.169218-Jun-200507:161,017,856RTMQFE
Cdfview.dll6.0.2800.161208-Dec-200401:43143,360RTMQFE
Danim.dll6.3.1.14821-Oct-200503:08986,112RTMQFE
Dxtrans.dll6.3.2800.152621-Oct-200521:02192,512RTMQFE
Iepeers.dll6.0.2800.149718-Feb-200520:44236,544RTMQFE
Inseng.dll6.0.2800.147524-Sep-200422:0769,632RTMQFE
Mshtml.dll6.0.2800.152923-Nov-200500:482,706,944RTMQFE
Msrating.dll6.0.2800.162324-Feb-200519:54132,096RTMQFE
Mstime.dll6.0.2800.152621-Oct-200521:02496,640RTMQFE
Pngfilt.dll6.0.2800.150627-Apr-200517:5038,912RTMQFE
Shdocvw.dll6.0.2800.176221-Oct-200523:171,339,392RTMQFE
Shlwapi.dll6.0.2800.174001-Sep-200501:49409,088RTMQFE
Urlmon.dll6.0.2800.152621-Oct-200521:03458,240RTMQFE
Wininet.dll6.0.2800.152621-Oct-200521:04586,752RTMQFE
Updspapi.dll6.2.29.028-Jun-200517:23371,424

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

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

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

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

Verifying that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

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

  • File Version Verification

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

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

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

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

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

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

Prerequisites
For Windows 2000, this security update requires Service Pack 4 (SP4). For Small Business Server 2000, this security update requires Small Business Server 2000 Service Pack 1a (SP1a) or Small Business Server 2000 running with Windows 2000 Server Service Pack 4 (SP4).

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

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

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

Installation Information

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/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 the following command at a command prompt for Windows 2000 Service Pack 4:

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

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

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

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

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

Restart Requirement

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%\$NTUninstallKB905915-IE501SP4-20051122.191609$\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.

Windows 2000 Service Pack 4 and Small Business Server 2000:

File NameVersionDateTimeSize
Browseui.dll5.0.3828.270027-Apr-200518:05792,848
Danim.dll6.1.9.72928-Oct-200506:191,134,352
Iepeers.dll5.0.3830.170018-Jun-200502:23100,112
Inseng.dll5.0.3828.270027-Apr-200518:0874,000
Mshtml.dll5.0.3835.220023-Nov-200501:132,299,664
Msrating.dll5.0.3828.270027-Apr-200518:06149,776
Pngfilt.dll5.0.3828.270027-Apr-200518:0748,912
Shdocvw.dll5.0.3830.170018-Jun-200500:321,100,048
Shlwapi.dll5.0.3900.706825-Aug-200507:13284,432
Url.dll5.50.4952.270027-Apr-200518:3384,240
Urlmon.dll5.0.3834.240024-Oct-200522:33423,696
Wininet.dll5.0.3834.240024-Oct-200522:33451,344
Updspapi.dll6.2.29.028-Jun-200517:23371,424

Verifying that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

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

  • File Version Verification

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

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

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

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

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Internet Explorer 5.01\SP4\KB905915-IE501SP4-20051122.191609\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 905915 security update into the Windows installation source files.

Other Information

Acknowledgments

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

  • Will Dormann of CERT/CC for reporting several class identifiers documented in the COM Object Instantiation Memory Corruption Vulnerability (CAN-2005-2831).
  • Andreas Sandblad and Jakob Balle of Secunia for reporting the File Download Dialog Box Manipulation Vulnerability - (CAN-2005-2829).
  • Berend-Jan Wever for working with us on the Mismatched Document Object Model Objects Memory Corruption Vulnerability - (CAN-2005-1790)

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 Scanning Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.

Disclaimer:

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

Revisions:

  • V1.0 (December 13, 2005): Bulletin published
  • V1.1 (February 1, 2006): Bulletin revised to call out that defense-in-depth improvements have also been made to the kill-bit mechanism.
  • V1.2 (March 8, 2006): Bulletin revised to add acknowledgment for CAN-2005-1790.

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.