Computer Security
[EN] securityvulns.ru no-pyccku


Related information

  Multiple Microsoft Internet Explorer browser security vulnerabilities

  "Drop to STARTUP Folder II" published on 2005/02/08

  [Full Disclosure] Using DHTML XSS to launch HHCTRL exploit

  [Full-Disclosure] Secunia Research: Microsoft Internet Explorer Multiple Vulnerabilities

  [Full-Disclosure] Secunia Research: Microsoft Internet Explorer "createControlRa
nge()" Memory Corruption

From:MICROSOFT <secure_(at)_microsoft.com>
Date:09.02.2005
Subject:Microsoft Security Bulletin MS05-014 Cumulative Security Update for Internet Explorer (867282)

Microsoft Security Bulletin MS05-014
Cumulative Security Update for Internet Explorer (867282)

Issued: February 8, 2005
Version: 1.0

Summary
Who should read this document: Customers who use Microsoft Windows

Impact of Vulnerability: Remote Code Execution

Maximum Severity Rating: Critical

Recommendation: Customers should apply the update immediately.

Security Update Replacement This update replaces the update that is included with Microsoft Security Bulletin MS04-038. That update is also a cumulative update. This update also replaces the update that is included with Microsoft Security Bulletin MS04-040. That update is also a cumulative update for Internet Explorer 6 Service Pack 1.

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

This update does include hotfixes that have been released since the release of MS04-004 or 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 FAQ “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?” in the FAQ section for this update to determine how to ensure that the necessary hotfixes are installed. Microsoft Knowledge Base Article 867282 also documents this in more detail.

Important: The update for the “Drag-and-Drop Vulnerability” (CAN-2005-0053) comes in two parts. It is addressed in part in this security bulletin. This security bulletin, together with security bulletin MS05-008, makes up the update for CAN-2005-0053. These updates do not have to be installed in any particular order. However, we recommend that you install both updates.

Tested Software and Security Update Download Locations:

Affected Software:

• Microsoft Windows 2000 Service Pack 3 and Microsoft Windows 2000 Service Pack 4

• Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2

• Microsoft Windows XP 64-Bit Edition Service Pack 1 (Itanium)

• Microsoft Windows XP 64-Bit Edition Version 2003 (Itanium)

• Microsoft Windows Server 2003

• Microsoft Windows Server 2003 for Itanium-based Systems

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


Tested Microsoft Windows Components:

Affected Components:

• Internet Explorer 5.01 Service Pack 3 (SP3) on Windows 2000 Service Pack 3: Download the update

• Internet Explorer 5.01 Service Pack 4 on Windows 2000 Service Pack 4: 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 2000 Service Pack 3, on Microsoft Windows 2000 Service Pack 4, or on Microsoft Windows XP Service Pack 1: Download the update

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

• Internet Explorer 6 for Windows XP Service Pack 1 (64-Bit Edition): Download the update

• Internet Explorer 6 for Windows Server 2003: Download the update

• Internet Explorer 6 for Windows Server 2003 64-Bit Edition and Windows XP 64-Bit Edition Version 2003: Download the update

• Internet Explorer 6 for Windows XP Service Pack 2: Download the update


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

Top of section
General Information
Executive Summary

Executive Summary:

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

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

We recommend that customers apply the update immediately.

Severity Ratings and Vulnerability Identifiers:

Vulnerability Identifiers Impact of Vulnerability Internet Explorer 5.01 Service Pack 3 and Service Pack 4 Internet Explorer 5.5 Service Pack 2 on Windows ME Internet 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
Drag and Drop Vulnerability - CAN-2005-0053
Remote Code Execution
Important
Not Critical
Important
Moderate
Important

URL Decoding Zone Spoofing Vulnerability - CAN-2005-0054
Remote Code Execution
Critical
Critical
Critical
Moderate
Important

DHTML Method Heap Memory Corruption Vulnerability - CAN-2005-0055
Remote Code Execution
Critical
Critical
Critical
Critical
Critical

Channel Definition Format (CDF) Cross Domain Vulnerability - CAN-2005-0056
Remote Code Execution
Moderate
Not Critical
Moderate
Low
Low

Aggregate Severity of All Vulnerabilities
 
Critical
Critical
Critical
Critical
Critical


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

Top of section
Frequently asked questions (FAQ) related to this security update

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

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

Bulletin ID Internet Explorer 5.01 SP3, SP4 Internet Explorer 5.5 SP2 Internet 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 on Windows XP Service Pack 2
MS04-038
Replaced
Replaced
Replaced
Replaced
Replaced

MS04-040
Not Applicable
Not Applicable
Replaced
Not Applicable
Not Applicable


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 intended for systems running Internet Explorer 6 Service Pack 1 on Microsoft Windows 2000 Service Pack 3, 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 only detects hotfixes released since Microsoft Security Bulletin MS04-038 and Internet Explorer update rollup 873377 or Internet Explorer update rollup 889669.

See Microsoft Knowledge Base Article 867282 for additional information if you need to apply a hotfix released before Microsoft Security Bulletin MS04-038 on a system with the MS05-014 update installed.

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

• This update sets the kill bit for the Microsoft ActiveX Image Control 1.0. This control implements support for dynamically changing images on a Web page. Internet Explorer no longer supports this control. This control has been found to contain a security vulnerability. To help protect customers who have this control installed, this update prevents the control from running in Internet Explorer. It does this by setting the kill bit for the control. For more information about kill bits, see Microsoft Knowledge Base Article 240797. The CLSID for this ActiveX control is {D4A97620-8E8F-11CF-93CD-00AA00C08FDF}.

• Like the previous Internet Explorer cumulative security updates that have been released since MS04-004, this update includes a change to the functionality of a clear-text authentication feature in Internet Explorer. The update removes Internet Explorer’s support for handling user names and passwords in HTTP URLs, in HTTP with Secure Sockets Layer (SSL) URLs, or in HTTPS URLs. The following URL syntax is no longer supported in Internet Explorer or in Windows Explorer after you install this software update:

http(s)://username:[email protected]/resource.ext

For more information about this change, please see Microsoft Knowledge Base Article 834489.

• This update includes a registry change supporting the part of update for the “Drag-and-Drop Vulnerability” (CAN-2005-0053) available in security bulletin MS05-008. The new registry entry is: HKLM\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\4\180b

This new registry value is a new DWORD value set to 1.

• This update also includes a registry key which is a list of valid file types that Internet Explorer will allow drag and drop events on: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\
Internet Settings\AllowedDragImageExts

For more information about this registry key see FAQ “Can I add or remove file types to this list of allowed file types?” in the section “FAQ for Drag-and-Drop Vulnerability - CAN-2005-0053:” in this bulletin.


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

• Like the previous Internet Explorer cumulative security updates that have been released since MS03-004, this update causes the window.showHelp( ) control to no longer work if you have not applied the HTML Help update. If you have installed the updated HTML Help control from Microsoft Knowledge Base Article 811630, you will still be able to use HTML Help functionality after you install this update.

• Like the previous Internet Explorer cumulative security update, MS04-004, this update prevents you from visiting Web sites that have "username:[email protected]" URLs for XMLHTTP. We have created an update to MSXML that addresses this issue specifically for XMLHTTP. For more information, see Microsoft Knowledge Base Article 832414.


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

• Slovenian – Download the update

• Slovakian – Download the update


I am still using Windows XP, but extended security update support ended on September 30th, 2004. What should I do?

The original version of Windows XP, generally known as Windows XP Gold or Windows XP Release to Manufacturing (RTM) version, reached the end of its extended security update support life cycle on September 30, 2004.

It should be a priority for customers who have this operating system version to migrate to supported operating system versions to prevent potential exposure to vulnerabilities. For more information about the Windows Service Pack Product Lifecycle, visit the Microsoft Support Lifecycle Web site. For more information about the Windows Product Lifecycle, visit the Microsoft Support Lifecycle Web site.

For more information, see the Windows Operating System Product Support Lifecycle FAQ.

I am still using Windows 2000 Service Pack 2, but extended security update support ended on June 30, 2004. What should I do?

Windows 2000 Service Pack 2 reached the end of its extended support life cycle as previously documented. It should be a priority for customers who have this operating system version to migrate to supported operating system versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the Microsoft Support Lifecycle Web site. For more information about the extended security update support period for this operating system version, visit the Microsoft Product Support Services Web site.

For more information, see the Windows Operating System Product Support Lifecycle FAQ.

Extended security update support for Microsoft Windows NT 4.0 Workstation Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. Extended security update support for Microsoft Windows NT 4.0 Server Service Pack 6a ended on December 31, 2004. I’m still using one of these operating systems, what should I do?

Windows NT 4.0 Workstation Service Pack 6a, Windows NT 4.0 Server Service Pack 6a, and Windows 2000 Service Pack 2 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 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.

Why are the command line installation switches different for Windows 2000 and Windows XP operating systems for this release when compared to MS04-025: Cumulative Security Update for Internet Explorer?
Starting with MS04-038, the packages for Windows 2000 and Windows XP Service Pack 1 use a new installation technology, Update.exe. Therefore, the installation options are different from previous releases. Also, as part of the change to the Update.exe installation technology, the Knowledge Base Article number of this update will no longer be displayed in the About Internet Explorer dialog box in Internet Explorer. For more information about the command line switches that are that are available for this release, please see the “Security Update Information” section of this bulletin. For more information about Update.exe, visit the following Microsoft Web site.

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

Note This release includes an update for Internet Explorer 6 Service Pack 1 designed for Windows 2000 and Windows XP Service Pack 1. If you are still managing Windows NT 4.0 systems in your enterprise and are using MBSA, a software updates scan will show this update as applicable on Windows NT 4.0 systems. However, the security update is only intended for the supported operating systems mentioned in the Affected Software section of this bulletin.

Note After April 20, 2004, the Mssecure.xml file that is used by MBSA 1.1.1 and earlier versions is no longer being updated with new security bulletin data. Therefore, scans that are performed after that date by using MBSA 1.1.1 or earlier will be incomplete. All users should upgrade to MBSA 1.2 because it provides more accurate security update detection and supports additional products. Users can download MBSA 1.2.1 from the MBSA Web site. For more information about MBSA support, visit the following Microsoft Baseline Security Analyzer (MBSA) 1.2.1 Q&A 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 This release includes a package for Internet Explorer 6 Service Pack 1 designed for Windows 2000 and Windows XP Service Pack 1. This package uses the Update.exe installation technology discussed in FAQ “Why are the command line installation switches different for Windows 2000 and Windows XP operating systems for this release when compared to MS04-025: Cumulative Security Update for Internet Explorer?”. If you are still managing Windows NT 4.0 systems in your enterprise using SMS, a software updates scan will show this update as applicable on Windows NT 4.0 systems, but these packages are designed to only enable installation on the supported operating systems mentioned in the Affected Software section of this bulletin. For more information, please see Microsoft Knowledge Base Article 892937 and FAQ “Extended security update support for Microsoft Windows NT 4.0 Workstation Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. Extended security update support for Microsoft Windows NT 4.0 Server Service Pack 6a ended on December 31, 2004. I’m still using one of these operating systems, what should I do?” for this security update.

Top of section
Vulnerability Details

Drag-and-Drop Vulnerability - CAN-2005-0053

A privilege elevation vulnerability exists in Internet Explorer because of the way that Internet Explorer handles drag-and-drop events. An attacker could exploit the vulnerability by constructing a malicious Web page. This malicious Web page could potentially allow an attacker to save a file on the user’s system if a user visited a malicious Web site or viewed a malicious e-mail message. An attacker who successfully exploited this vulnerability could take complete control of an affected system. However, user interaction is required to exploit this vulnerability.

Mitigating Factors for Drag-and-Drop Vulnerability - CAN-2005-0053:

• 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 could also attempt to compromise a Web site to have it display a Web page with malicious content. An attacker would have no way to force users to visit a 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 or to a site that has been compromised by the attacker.

• An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

• By default, Microsoft Outlook Express 6, Outlook 2000, Outlook 2002, and Outlook 2003 open HTML e-mail messages in the Restricted sites zone. 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. The Restricted sites zone helps reduce attacks that could try to exploit this vulnerability.

The risk of attack from the HTML e-mail vector can be significantly reduced if you meet all the following conditions:

• Install the update that is included with Microsoft Security Bulletin MS03-040 or a later Cumulative Security Update for Internet Explorer.

• Use Microsoft Outlook Express 6 or a later version in its default configuration, or use Microsoft Outlook 2000 Service Pack 2 or a later version in its default


• 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 vulnerability for more information about Internet Explorer Enhanced Security Configuration.


Top of section
Workarounds for Drag-and-Drop Vulnerability - CAN-2005-0053:

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.

• Disable “Drag and Drop or copy and paste files” in Internet Explorer

Disable “Drag and Drop or copy and paste files” in Internet Explorer by following these steps:

1.
Obtain and install the MS04-038 Cumulative Security Update for Internet Explorer. This security update must be installed for these configuration steps to be effective.

2.
Disable the Drag and drop or copy and paste files option in the Internet and Intranet Web content zones. Disable the Drag and drop or copy and paste files option in the Internet and local intranet zone. To do this, follow these steps:

1.
In Internet Explorer, click Internet Options on the Tools menu, and then click the Security tab.

2.
In the Select a Web content zone to specify its security settings box, click Internet, and then click Custom Level.

3.
In the Settings box, locate the Drag and drop or copy and paste files option under Miscellaneous. Make a note of your current setting.

4.
Under Drag and drop or copy and paste files, click Disable, and then click OK.

5.
Click Yes, and then click OK two times.


Note Repeat these steps for the local intranet zone by clicking Local intranet instead of Internet in step 2. These steps are also outlined in Microsoft Knowledge Base Article 888534 where steps on how to restore your previous drag and drop or copy and paste files setting are outlined.


• 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 high security setting.

Alternatively, you can change your settings to prompt before running ActiveX controls only. 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.

5.
In the Scripting section, under Active Scripting, click Prompt, and then click OK.

6.
Click Local intranet, and then click Custom Level.

7.
Under Settings, in the ActiveX controls and plug-ins section, under Run ActiveX controls and plug-ins, click Prompt.

8.
In the Scripting section, under Active Scripting, click Prompt.

9.
Click OK two times to return to Internet Explorer.


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

3.
If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.

4.
In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.

5.
Repeat these steps for each site that you want to add to the zone.

6.
Click OK two times to accept the changes and return to Internet Explorer.


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.

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

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

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

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

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

• The changes are applied to the preview pane and to open messages.

• Pictures become attachments so that they are not lost.

• Because the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.



Top of section
FAQ for Drag-and-Drop Vulnerability - CAN-2005-0053:

What is the scope of the vulnerability?
This vulnerability involves drag and drop events in Internet Explorer. An attacker who successfully exploited this vulnerability could cause an executable file to be saved on the user's system. The user would not receive a dialog box requesting approval for the download. To exploit this vulnerability, an attacker would have to host a malicious Web site that contained a Web page that was designed to exploit this vulnerability and then persuade a user to visit that site. If the user took certain actions on that Web page, executable files of the attacker's choice could be saved in specified locations on the user's system.

What causes the vulnerability?
Drag-and-Drop technology incorrectly validates some dynamic HTML (DHTML) events. This vulnerability permits a file to be downloaded to the user's system after the user clicks a link.

What are DHMTL events?
DHTML events are special actions that are provided by the DHTML Object Model. These events can be used in script code to add dynamic content to a Web site. For more information about DHTML events, see the product documentation.

How could an attacker exploit the vulnerability?
An attacker who successfully exploited this vulnerability could save code of their choice to the user's local file system. Although this code could not be run through this vulnerability directly, the operating system might open the file if it is saved to a sensitive location, or a user may open the file inadvertently and cause the attacker's code to run.

What systems are primarily at risk from the vulnerability?
This vulnerability requires that a user is logged on and reading e-mail or visiting Web sites for any malicious action to occur. Therefore, any systems where e-mail is read or where Internet Explorer is used frequently, such as users’ workstations or terminal servers, are at the most risk from this vulnerability. Systems that are not typically used to read e-mail or to visit Web sites, such as most server systems, are at a reduced risk.

I am running Internet Explorer on Windows Server 2003. Does this mitigate this vulnerabilitiy?
Yes. 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.

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

• Security level for the Internet zone is set to High. This setting disables scripts, ActiveX controls, Microsoft Java Virtual Machine (MSJVM), HTML content, and file downloads.

• Automatic detection of intranet sites is disabled. This setting assigns all intranet Web sites and all Universal Naming Convention (UNC) paths that are not explicitly listed in the Local intranet zone to the Internet zone.

• Install On Demand and non-Microsoft browser extensions are disabled. This setting prevents Web pages from automatically installing components and prevents non-Microsoft extensions from running.

• Multimedia content is disabled. This setting prevents music, animations, and video clips from running.


What does the update do?
The update removes the vulnerability by modifying the way that Internet Explorer validates some drag and drop events. The update also includes a list of valid file types that Internet Explorer will allow drag and drop events on.

Can I add or remove file types to this list of allowed file types?
Yes. You can allow Internet Explorer drag and drop events on other file types. You can also further restrict what file types you want Internet Explorer to allow drag and drop events on. To do this, edit the following registry key.

Warning When you do this, be very selective and allow only file types that you must.

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.

To allow drag and drop of additional file types:

1.
Click Start, click Run, type Regedit in the Open box, and then click OK.

2.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\
Internet Settings\AllowedDragImageExts

3.
On the Edit menu, point to New, and then click DWORD Value.

4.
Type the file extension, for instance, .aif, and then press ENTER.

5.
Right-click the newly created DWORD value, change the Value Data field to 1, and then press ENTER.

Note The Value Data field of a newly created registry value is by default 0 (zero).


To disallow drag and drop of certain file types:

1.
Click Start, click Run, type Regedit in the Open box, and then click OK.

2.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\
Internet Settings\AllowedDragImageExts

3.
Remove DWORD Value for which you do not wish to allow Internet Explorer drag and drop functionality.

Note It is recommended that you back up this registry key before performing this operation.


When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability has been publicly disclosed. This vulnerability has been assigned Common Vulnerability and Exposure number CAN-2005-0053.

Note The update for the “Drag-and-Drop Vulnerability” - CAN-2005-0053 also addresses the following publicly disclosed variations: CAN-2004-0985, CAN-2004-0839, and CAN-2003-1027.

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 tries to exploit this vulnerability?
Yes. This security update addresses the vulnerability and its variations that are currently being exploited. The vulnerability that has been addressed has been assigned the Common Vulnerability and Exposure number CAN-2005-0053.

Top of section
Top of section
URL Decoding Zone Spoofing Vulnerability - CAN-2005-0054

A remote code execution vulnerability exists in Internet Explorer because of the way that it handles certain encoded URLs. An attacker could exploit the vulnerability by constructing a malicious URL. This malicious URL could potentially allow remote code execution if a user visited a malicious Web site or viewed a malicious e-mail message. The URL could be made to look like a link to another Web site in an attempt to trick a user into clicking it. 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 URL Decoding Zone Spoofing Vulnerability - CAN-2005-0054:

• 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 could also attempt to compromise a Web site to have it display a Web page with malicious content. An attacker would have no way to force users to visit a 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 or to a site that has been compromised by the attacker.

• An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

• By default, Microsoft Outlook Express 6, Outlook 2000, Outlook 2002, and Outlook 2003 open HTML e-mail messages in the Restricted sites zone. 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. The Restricted sites zone helps reduce attacks that could try to exploit this vulnerability.

The risk of attack from the HTML e-mail vector can be significantly reduced if you meet all the following conditions:

• Install the update that is included with Microsoft Security Bulletin MS03-040 or a later Cumulative Security Update for Internet Explorer.

• Use Microsoft Outlook Express 6 or a later version in its default configuration, or use Microsoft Outlook 2000 Service Pack 2 or a later version in its default configuration.


• 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 security update for more information about Internet Explorer Enhanced Security Configuration.

• Windows XP Service Pack 2 introduced a security enhancement known as the Local Machine zone lockdown. This security enhancement mitigates this vulnerability. See the FAQ section of this security update for more information about Local Machine zone lockdown.


Top of section
Workarounds for URL Decoding Zone Spoofing Vulnerability - CAN-2005-0054:

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.

• 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, and then click Sites.

3.
If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.

4.
In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.

5.
Repeat these steps for each site that you want to add to the zone.

6.
Click OK two times to accept the changes and return to Internet Explorer.


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.

• Install the update that is described in Microsoft Security Bulletin MS04-018 if you are using Outlook Express 5.5 SP2.

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.

Customers who use one or more of these products could be at a reduced risk from an e-mail-borne attack that tries to exploit this vulnerability unless the user clicks a malicious link in the e-mail message.

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

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

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

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

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

• The changes are applied to the preview pane and to open messages.

• Pictures become attachments so that they are not lost.

• Because the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.



Top of section
FAQ for URL Decoding Zone Spoofing Vulnerability - CAN-2005-0054:

What is the scope of the vulnerability?
This vulnerability could potentially allow remote code execution. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

Other possible attack scenarios include cross site scripting and partial address bar spoofing.

What causes the vulnerability?
The way that Internet Explorer parses certain types of encoded URLs.

What is URL encoding and what it is used for?
URL encoding is necessary in certain situations where a URL contains characters other than alphanumeric. Characters such as ASCII control characters or other reserved characters are included in a URL without first being encoded might be interpreted in an unintended way by browsers. Some characters, such as “space”, the pound character (“#”), or the percent character (“%”) may be misunderstood if included in URLs and are therefore encoded. For more information about URL encoding, see the Uniform Resource Locators (URL) RFC document: RFC 1738.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.

How could an attacker exploit the vulnerability?
An attacker could use this vulnerability to cause Internet Explorer to interpret an HTML page in the Internet zone as if it were in another Internet Explorer security zone. Internet Explorer would then apply the security settings for that Internet Explorer security zone to the HTML page instead of the Internet Explorer security zone that the HTML page belongs to. A user would have to click a link for any malicious action to occur. This vulnerability could also be used to attempt cross site scripting attacks or partial address bar spoofing. An attacker could create a Web page that would display a URL of the attacker’s choice in the Address bar, while displaying a different Web site in the browser window. An attacker could use this vulnerability to create a malicious page that spoofs a legitimate site. For example, an attacker could create a Web page that looks like a user's online e-mail Web site. However, this Web page would be hosted on a malicious Web site. An attacker could use this vulnerability to display a legitimate-looking URL in the Address bar. A user might see this URL and mistakenly provide sensitive information to the attacker's Web site.

The address bar spoof in this case is not complete and would, in part, display the attacker’s Web site URL as well.

What are Internet Explorer security zones?
Internet Explorer security zones are part of a system that divides online content into categories or zones that are based on the trustworthiness of the content. Specific Web domains can be assigned to a zone, depending on how much you trust the content of each domain. The zone then restricts the capabilities of the Web content, based on the zone's policy. By default, most Internet domains are treated as part of the Internet zone. By default, the policy of the Internet zone prevents scripts and other active code from accessing resources on the local system.

What systems are primarily at risk from the vulnerability?
This vulnerability requires that a user is logged on and reading e-mail or visiting Web sites for any malicious action to occur. Therefore, any systems where e-mail is read or where Internet Explorer is used frequently, such as users’ workstations or terminal servers, are at the most risk from this vulnerability. Systems that are not typically used to read e-mail or to visit Web sites, such as most server systems, are at a reduced risk.

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 this vulnerability. Critical security updates for these platforms are available, are provided as part of this security bulletin, and can be downloaded only 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 validates encoded URLs.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. However, a similar vulnerability has since been publicly disclosed. This update addresses both the privately reported vulnerability, which has been assigned CAN-2005-0054, as well as the independently publicly disclosed variation, which has not been assigned any CAN number.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had seen examples of proof of concept code published publicly but had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.

Top of section
Top of section
DHTML Method Heap Memory Corruption Vulnerability - CAN-2005-0055

A remote code execution vulnerability exists in Internet Explorer because of the way that it handles certain DHTML methods. An attacker could exploit the vulnerability by constructing a malicious Web page. This malicious Web page could potentially allow remote code execution if a user visited a malicious Web site or viewed a malicious e-mail message. An attacker who successfully exploited this vulnerability could take complete control of an affected system. However, user interaction is required to exploit this vulnerability.

Mitigating Factors for DHTML Method Heap Memory Corruption Vulnerability - CAN-2005-0055:

• 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 could also attempt to compromise a Web site to display a Web page with malicious content. An attacker would have no way to force users to visit a 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 or to a site that has been compromised by the attacker.

• An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

• By default, Outlook Express 6, Outlook 2002, and Outlook 2003 open HTML e-mail messages in the Restricted sites zone. Additionally, Outlook 2000 opens HTML e-mail messages in the Restricted sites zone if the Outlook E-mail Security Update has been installed. Outlook Express 5.5 Service Pack 2 opens HTML e-mail messages in the Restricted sites zone if Microsoft Security Bulletin MS04-018 has been installed. The Restricted sites zone helps reduce attacks that could try to exploit this vulnerability.

The risk of attack from the HTML e-mail vector can be significantly reduced if you meet all the following conditions:

• Apply the update that is included with Microsoft Security Bulletin MS03-040 or a later Cumulative Security Update for Internet Explorer.

• Use the Microsoft Outlook E-mail Security Update, use Microsoft Outlook Express 6 or a later version, or use Microsoft Outlook 2000 Service Pack 2 or a later version in its default configuration.


• The vulnerability could not be exploited automatically through e-mail. For an attack to be successful, a user must open an attachment this is sent in an e-mail message.


Top of section
Workarounds for DHTML Method Heap Memory Corruption Vulnerability - CAN-2005-0055:

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.

• Set Internet and Local intranet security zone settings to “High” to prompt before running 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 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 high security setting.

Alternatively, you can change your settings to prompt before running Active Scripting only. 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, 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.

7.
Click OK two times to return to Internet Explorer.


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. Prompting before running Active Scripting controls is a global setting that affects all Internet and intranet sites. You will be 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.

• Restrict Web sites to only your trusted Web sites.

After you set Internet Explorer to require a prompt before it runs 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, and then click Sites.

3.
If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.

4.
In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.

5.
Repeat these steps for each site that you want to add to the zone.

6.
Click OK two times to accept the changes and return to Internet Explorer.


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.

• Install the update that is described in Microsoft Security Bulletin MS04-018 if you are using Outlook Express 5.5 SP2.

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.

Customers who use one or more of these products could be at a reduced risk from an e-mail-borne attack that tries to exploit this vulnerability unless the user clicks a malicious link in the e-mail message.

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

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

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

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

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

• The changes are applied to the preview pane and to open messages.

• Pictures become attachments so that they are not lost.

• Because the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.



Top of section
FAQ for DHTML Method Heap Memory Corruption Vulnerability - CAN-2005-0055:

What is the scope of the vulnerability?
This is a remote code execution vulnerability. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

What causes the vulnerability?
The process used by Internet Explorer to validate the buffer used when processing certain DHTML methods?

What are DHTML methods?
The DHTML object model allows for more dynamic content on Web pages. DHTML methods are the methods that the DHTML object model provides. These methods can be used in script code to add dynamic content to a Web site. For more information about DHTML methods, see the product documentation.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.

How could an attacker exploit the vulnerability?
An attacker could exploit this vulnerability by creating a malicious Web page or an HTML e-mail message and then persuading the user to visit the page or to view the HTML e-mail message. If the user visited the page or viewed the e-mail message, the attacker could access information from other Web sites, could access local files on the system, or could cause malicious code to run in the security context of the locally logged on user.

What systems are primarily at risk from the vulnerability?
This vulnerability requires that a user is logged on and reading e-mail or visiting Web sites for any malicious action to occur. Therefore, any systems where e-mail is read or where Internet Explorer is used frequently, such as users’ workstations or terminal servers, are at the most risk from this vulnerability. Systems that are not typically used to read e-mail or to visit Web sites, such as most server systems, are at a reduced risk.

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 this vulnerability. Critical security updates for these platforms are available, are provided as part of this security bulletin, and can be downloaded only 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 validates the length of a message before it passes the message to the allocated buffer.

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

Top of section
Top of section
Channel Definition Format (CDF) Cross Domain Vulnerability - CAN-2005-0056:

A cross-domain vulnerability exists in Internet Explorer that could allow information disclosure or remote code execution on an affected system. An attacker could exploit the vulnerability by constructing a malicious Web page. The malicious Web page could potentially allow remote code execution if viewed by a user. 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 Channel Definition Format (CDF) Cross Domain Vulnerability - CAN-2005-0056:

• 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 could also attempt to compromise a Web site to have it display a Web page with malicious content. An attacker would have no way to force users to visit a 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 or to a site that has been compromised by the attacker.

• An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

• By default, Microsoft Outlook Express 6, Outlook 2000, Outlook 2002, and Outlook 2003 open HTML e-mail messages in the Restricted sites zone. 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. The Restricted sites zone helps reduce attacks that could try to exploit this vulnerability.

The risk of attack from the HTML e-mail vector can be significantly reduced if you meet all the following conditions:

• Install the update that is included with Microsoft Security Bulletin MS03-040 or a later Cumulative Security Update for Internet Explorer.

• Use Microsoft Outlook Express 6 or a later version in its default configuration, or use Microsoft Outlook 2000 Service Pack 2 or a later version in its default configuration.


• 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 security update for more information about Internet Explorer Enhanced Security Configuration.

• Windows XP Service Pack 2 introduced a security enhancement known as the Local Machine zone lockdown. This security enhancement mitigates this vulnerability. See the FAQ section of this security update for more information about Local Machine zone lockdown.

• Windows XP Service Pack 2 introduced a new security context on all scriptable objects so that access to cached objects (except for ActiveX controls) is blocked. In addition to blocking access when navigating across domains, access is also blocked when navigating within the same domain. In this context, a domain is defined as a fully qualified domain name, or FQDN. A reference to an object is no longer accessible after the context has changed due to navigation. For more information about Internet Explorer Object Caching in Windows XP Service Pack 2, see the product documentation.


Top of section
Workarounds for Channel Definition Format (CDF) Cross Domain Vulnerability - CAN-2005-0056:

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.

• 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 high security setting.

Alternatively, you can change you settings to prompt before running ActiveX controls only. 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.

5.
In the Scripting section, under Active Scripting, click Prompt, and then click OK.

6.
Click Local intranet, and then click Custom Level.

7.
Under Settings, in the ActiveX controls and plug-ins section, under Run ActiveX controls and plug-ins, click Prompt.

8.
In the Scripting section, under Active Scripting, click Prompt.

9.
Click OK two times to return to Internet Explorer.


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

3.
If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.

4.
In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.

5.
Repeat these steps for each site that you want to add to the zone.

6.
Click OK two times to accept the changes and return to Internet Explorer.


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.

• Install the update that is described in Microsoft Security Bulletin MS04-018 if you are using Outlook Express 5.5 SP2.

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.

Customers who use any of these products could be at a reduced risk from an e-mail-borne attack that tries to exploit this vulnerability unless the user clicks a malicious link in the e-mail message.

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

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

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

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

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

• The changes are applied to the preview pane and to open messages.

• Pictures become attachments so that they are not lost.

• Because the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.



Top of section
FAQ for Channel Definition Format (CDF) Cross Domain Vulnerability - CAN-2005-0056:

What is the scope of the vulnerability?
This is a cross-domain vulnerability that could allow information disclosure or remote code execution. If a user is logged on with administrative privileges, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full privileges. Users whose accounts are configured to have fewer privileges on the system could be less impacted than users who operate with administrative privileges.

What causes the vulnerability?
The process by which certain URLs that are found in Channel Definition Format (CDF) files are validated by the Internet Explorer cross-domain security model.

What are Channel Definition Format files?
Channel Definition Format (CDF) files can be used to organize a set of related Web pages into a logical hierarchy. A channel is a Web site described by a Channel Definition Format (CDF) file. The CDF file defines a hierarchy of the pages that are included in the channel. Besides defining the resources in the channel, the CDF file also specifies how each item will be used or displayed, and when the channel should be updated. For more information about CDF files, see the product documentation.

What are Internet Explorer security zones?
Internet Explorer security zones are part of a system that divides online content into categories or zones, based on the trustworthiness of the content. Specific Web domains can be assigned to a zone, depending on how much trust is put in the content of each domain. The zone then restricts the capabilities of the Web content, based on the zone's policy. By default, most Internet domains are treated as part of the Internet zone. By default, the policy of the Internet zone prevents scripts and other active code from accessing resources on the local system.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run malicious script code in the Local Machine security zone in Internet Explorer. This could allow an attacker to take complete control of the affected system.

How could an attacker exploit the vulnerability?
An attacker could exploit this vulnerability by creating a malicious Web page or an HTML e-mail message and then persuading the user to visit this page or to view the HTML e-mail message. When the user visited the page or viewed the e-mail message and interacted with the Web page or HTML email message, the attacker could access information from other Web sites, local files on the system, or cause script to run in the security context of the Local Machine zone.

What systems are primarily at risk from the vulnerability?
This vulnerability requires that a user view a Web site for malicious action to occur and accept a prompt for adding an Internet Explorer favorite to their system. Therefore, any systems where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability. Systems that are not typically used to visit Web sites, such as most server systems, are at a reduced risk.

I am running Internet Explorer on Windows Server 2003. Does this mitigate this vulnerabilitiy?
Yes. 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.

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

• Security level for the Internet zone is set to High. This setting disables scripts, ActiveX controls, Microsoft Java Virtual Machine (MSJVM), HTML content, and file downloads.

• Automatic detection of intranet sites is disabled. This setting assigns all intranet Web sites and all Universal Naming Convention (UNC) paths that are not explicitly listed in the Local intranet zone to the Internet zone.

• Install On Demand and non-Microsoft browser extensions are disabled. This setting prevents Web pages from automatically installing components and prevents non-Microsoft extensions from running.

• Multimedia content is disabled. This setting prevents music, animations, and video clips from running.


I am running Internet Explorer on Windows XP Service Pack 2. Does this mitigate this vulnerability?
Yes. Windows XP Service Pack 2 introduced a security enhancement known as the Local Machine zone lockdown that mitigates this vulnerability.

What is the Local Machine zone lockdown?
In Windows XP Service Pack 2, all local files and content that are processed by Internet Explorer has additional security applied to it in the Local Machine zone. This feature restricts HTML in the Local Machine zone. This feature also restricts HTML that is hosted in Internet Explorer. These restrictions help mitigate attacks where the Local Machine zone is used as an attack vector to load malicious HTML code.

Because of this change, ActiveX script in local HTML pages that are viewed inside Internet Explorer will not run. Also, script in local HTML pages that is viewed inside Internet Explorer prompts the user for permission to run.

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 the Internet Explorer cross-domain security model is enforced when Internet Explorer uses Channel Definition Format (CDF) files.

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

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had seen examples of proof of concept code published publicly but had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.

Top of section
Top of section
Top of section
Security Update Information

Affected Software:

For additional information about how to determine which version of Internet Explorer you are running, see Microsoft Knowledge Base Article 164539. For information about the specific security update for your affected software, click the appropriate link:

Internet Explorer 6 for Windows Server 2003 (all versions) and for Windows XP 64-Bit Edition, Version 2003

Prerequisites
This update requires Internet Explorer 6 (version 6.00.3790.0000) on Windows Server 2003 (all versions) or Internet Explorer 6 (version 6.00.3790.0000) on Windows XP 64-Bit Edition, Version 2003.

Inclusion in Future Service Packs:
The update for this issue will be included in Windows Server 2003 Service Pack 1.

Installation Information

This security update supports the following setup switches:

     /help                 Displays the command-line options

Setup Modes

     /quiet                Quiet mode (no user interaction or display)

     /passive            Unattended mode (progress bar only)

     /uninstall          Uninstalls the package

Restart Options

     /norestart          Do not restart when installation has completed

     /forcerestart      Restart after installation

Special Options

     /l                        Lists installed Windows hotfixes or update packages

     /o                       Overwrite OEM files without prompting

     /n                       Do not backup files needed for uninstall

     /f                        Force other programs to close when the computer shuts down

     /integrate:path  Integrates the update into the Windows source files located at the path specified

     /extract             Extracts files without starting the Setup program

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

Deployment Information

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

Windowsserver2003-kb867282-x86-enu /passive /quiet

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

Windowsserver2003-kb867282-x86-enu /norestart

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

Restart Requirement

You must restart your system after you apply this security update. You do not have to use an administrator logon after the computer restarts for any version of this 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%\$NTUninstallKB867282$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:

     /help                 Displays the command line options

Setup Modes

     /quiet                Quiet mode (no user interaction or display)

     /passive            Unattended mode (progress bar only)

Restart Options

     /norestart          Do not restart when installation is complete

     /forcerestart      Restart after installation

Special Options

     /f                        Force other programs to close when the computer shuts down

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, Enterprise Edition; Windows Server 2003, Datacenter Edition; and Windows Small Business Server 2003:

File Name Version Date Time Size Folder
Browseui.dll
6.0.3790.259
27-Jan-2005
23:14
1,057,792
RTMGDR

Cdfview.dll
6.0.3790.259
27-Jan-2005
23:14
147,968
RTMGDR

Digest.dll
6.0.3790.259
27-Jan-2005
23:14
59,904
RTMGDR

Iepeers.dll
6.0.3790.259
27-Jan-2005
23:14
238,080
RTMGDR

Inseng.dll
6.0.3790.259
27-Jan-2005
23:14
73,216
RTMGDR

Mshtml.dll
6.0.3790.259
27-Jan-2005
23:14
2,926,592
RTMGDR

Shdocvw.dll
6.0.3790.259
27-Jan-2005
23:14
1,395,200
RTMGDR

Shlwapi.dll
6.0.3790.259
27-Jan-2005
23:14
287,232
RTMGDR

Urlmon.dll
6.0.3790.259
27-Jan-2005
23:14
518,656
RTMGDR

Wininet.dll
6.0.3790.259
27-Jan-2005
23:14
624,640
RTMGDR

Browseui.dll
6.0.3790.259
27-Jan-2005
23:24
1,057,792
RTMQFE

Cdfview.dll
6.0.3790.259
27-Jan-2005
23:24
147,456
RTMQFE

Digest.dll
6.0.3790.259
27-Jan-2005
23:24
59,904
RTMQFE

Iepeers.dll
6.0.3790.259
27-Jan-2005
23:24
238,080
RTMQFE

Inseng.dll
6.0.3790.259
27-Jan-2005
23:24
73,216
RTMQFE

Mshtml.dll
6.0.3790.259
27-Jan-2005
23:24
2,927,104
RTMQFE

Shdocvw.dll
6.0.3790.259
27-Jan-2005
23:24
1,398,272
RTMQFE

Shlwapi.dll
6.0.3790.259
27-Jan-2005
23:24
287,232
RTMQFE

Urlmon.dll
6.0.3790.259
27-Jan-2005
23:24
518,656
RTMQFE

Wininet.dll
6.0.3790.259
27-Jan-2005
23:24
626,176
RTMQFE


Windows Server 2003, Enterprise Edition for Itanium-based Systems and Windows Server 2003, Datacenter Edition for Itanium-based Systems:

File Name Version Date Time Size CPU Folder
Browseui.dll
6.0.3790.259
27-Jan-2005
23:10
2,536,960
IA-64
RTMGDR

Cdfview.dll
6.0.3790.259
27-Jan-2005
23:10
303,616
IA-64
RTMGDR

Digest.dll
6.0.3790.259
27-Jan-2005
23:10
141,312
IA-64
RTMGDR

Iepeers.dll
6.0.3790.259
27-Jan-2005
23:10
674,816
IA-64
RTMGDR

Inseng.dll
6.0.3790.259
27-Jan-2005
23:10
217,600
IA-64
RTMGDR

Mshtml.dll
6.0.3790.259
27-Jan-2005
23:10
8,235,008
IA-64
RTMGDR

Shdocvw.dll
6.0.3790.259
27-Jan-2005
23:10
3,362,816
IA-64
RTMGDR

Shlwapi.dll
6.0.3790.259
27-Jan-2005
23:10
738,816
IA-64
RTMGDR

Urlmon.dll
6.0.3790.259
27-Jan-2005
23:10
1,289,216
IA-64
RTMGDR

Wininet.dll
6.0.3790.259
27-Jan-2005
23:10
1,503,232
IA-64
RTMGDR

Wbrowseui.dll
6.0.3790.259
27-Jan-2005
23:14
1,057,792
x86
RTMGDR\WOW

Wcdfview.dll
6.0.3790.259
27-Jan-2005
23:14
147,968
x86
RTMGDR\WOW

Wiepeers.dll
6.0.3790.259
27-Jan-2005
23:14
238,080
x86
RTMGDR\WOW

Winseng.dll
6.0.3790.259
27-Jan-2005
23:14
73,216
x86
RTMGDR\WOW

Wmshtml.dll
6.0.3790.259
27-Jan-2005
23:14
2,926,592
x86
RTMGDR\WOW

Wshdocvw.dll
6.0.3790.259
27-Jan-2005
23:14
1,395,200
x86
RTMGDR\WOW

Wshlwapi.dll
6.0.3790.259
27-Jan-2005
23:14
287,232
x86
RTMGDR\WOW

Wurlmon.dll
6.0.3790.259
27-Jan-2005
23:14
518,656
x86
RTMGDR\WOW

Wwdigest.dll
6.0.3790.259
27-Jan-2005
23:14
59,904
x86
RTMGDR\WOW

Wwininet.dll
6.0.3790.259
27-Jan-2005
23:14
624,640
x86
RTMGDR\WOW

Browseui.dll
6.0.3790.259
27-Jan-2005
23:17
2,538,496
IA-64
RTMQFE

Cdfview.dll
6.0.3790.259
27-Jan-2005
23:17
303,616
IA-64
RTMQFE

Digest.dll
6.0.3790.259
27-Jan-2005
23:17
141,312
IA-64
RTMQFE

Iepeers.dll
6.0.3790.259
27-Jan-2005
23:17
674,816
IA-64
RTMQFE

Inseng.dll
6.0.3790.259
27-Jan-2005
23:17
217,600
IA-64
RTMQFE

Mshtml.dll
6.0.3790.259
27-Jan-2005
23:17
8,236,032
IA-64
RTMQFE

Shdocvw.dll
6.0.3790.259
27-Jan-2005
23:17
3,373,056
IA-64
RTMQFE

Shlwapi.dll
6.0.3790.259
27-Jan-2005
23:17
738,816
IA-64
RTMQFE

Urlmon.dll
6.0.3790.259
27-Jan-2005
23:17
1,289,216
IA-64
RTMQFE

Wininet.dll
6.0.3790.259
27-Jan-2005
23:17
1,505,280
IA-64
RTMQFE

Wbrowseui.dll
6.0.3790.259
27-Jan-2005
23:24
1,057,792
x86
RTMQFE\WOW

Wcdfview.dll
6.0.3790.259
27-Jan-2005
23:24
147,456
x86
RTMQFE\WOW

Wiepeers.dll
6.0.3790.259
27-Jan-2005
23:24
238,080
x86
RTMQFE\WOW

Winseng.dll
6.0.3790.259
27-Jan-2005
23:24
73,216
x86
RTMQFE\WOW

Wmshtml.dll
6.0.3790.259
27-Jan-2005
23:24
2,927,104
x86
RTMQFE\WOW

Wshdocvw.dll
6.0.3790.259
27-Jan-2005
23:24
1,398,272
x86
RTMQFE\WOW

Wshlwapi.dll
6.0.3790.259
27-Jan-2005
23:24
287,232
x86
RTMQFE\WOW

Wurlmon.dll
6.0.3790.259
27-Jan-2005
23:24
518,656
x86
RTMQFE\WOW

Wwdigest.dll
6.0.3790.259
27-Jan-2005
23:24
59,904
x86
RTMQFE\WOW

Wwininet.dll
6.0.3790.259
27-Jan-2005
23:24
626,176
x86
RTMQFE\WOW


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

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

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

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

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 may be able to 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 Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003; Windows Server 2003, Enterprise Edition for Itanium-based Systems; and Windows Server 2003, Datacenter Edition for Itanium-based Systems:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB867282\Filelist


Top of section
Internet Explorer 6 for Windows XP Service Pack 2

Prerequisites
This update requires Internet Explorer 6 (version 6.00.2900.2180) on Windows XP Service Pack 2.

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:

     /help                 Displays the command-line options

Setup Modes

     /quiet                Quiet mode (no user interaction or display)

     /passive            Unattended mode (progress bar only)

     /uninstall          Uninstalls the package

Restart Options

     /norestart          Do not restart when installation has completed

     /forcerestart      Restart after installation

Special Options

     /l                        Lists installed Windows hotfixes or update packages

     /o                       Overwrite OEM files without prompting

     /n                       Do not backup files needed for uninstall

     /f                        Force other programs to close when the computer shuts down

     /integrate:path  Integrates the update into the Windows source files located at the path specified

     /extract             Extracts files without starting the Setup program

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 Service Pack 2:

Windowsxp-kb867282-x86-enu /passive /quiet

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

Windowsxp-kb867282-x86-enu /norestart

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

Restart Requirement

You must restart your system after you install this security update. You do not have to use an administrator logon after the computer restarts for any version of this 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%\$NTUninstallKB867282$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:

     /help                 Displays the command line options

Setup Modes

     /quiet                Quiet mode (no user interaction or display)

     /passive            Unattended mode (progress bar only)

Restart Options

     /norestart          Do not restart when installation is complete

     /forcerestart      Restart after installation

Special Options

     /f                        Force other programs to close when the computer shuts down

File Information

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

Internet Explorer 6 for Windows XP Service Pack 2:

File Name Version Date Time Size Folder
Browseui.dll
6.0.2900.2578
27-Jan-2005
17:13
1,016,832
SP2GDR

Cdfview.dll
6.0.2900.2573
27-Jan-2005
17:13
151,040
SP2GDR

Iepeers.dll
6.0.2900.2604
27-Jan-2005
17:13
249,856
SP2GDR

Inseng.dll
6.0.2900.2573
27-Jan-2005
17:13
96,256
SP2GDR

Mshtml.dll
6.0.2900.2604
27-Jan-2005
17:13
3,006,976
SP2GDR

Shdocvw.dll
6.0.2900.2573
27-Jan-2005
17:13
1,483,264
SP2GDR

Shlwapi.dll
6.0.2900.2573
27-Jan-2005
17:13
473,600
SP2GDR

Urlmon.dll
6.0.2900.2574
27-Jan-2005
17:13
607,744
SP2GDR

Wininet.dll
6.0.2900.2577
27-Jan-2005
17:13
656,896
SP2GDR

Browseui.dll
6.0.2900.2598
27-Jan-2005
17:08
1,016,832
SP2QFE

Cdfview.dll
6.0.2900.2573
27-Jan-2005
17:08
151,040
SP2QFE

Iepeers.dll
6.0.2900.2604
27-Jan-2005
17:08
249,856
SP2QFE

Inseng.dll
6.0.2900.2573
27-Jan-2005
17:08
96,256
SP2QFE

Mshtml.dll
6.0.2900.2604
27-Jan-2005
17:08
3,008,000
SP2QFE

Shdocvw.dll
6.0.2900.2598
27-Jan-2005
17:08
1,484,288
SP2QFE

Shlwapi.dll
6.0.2900.2573
27-Jan-2005
17:08
473,600
SP2QFE

Urlmon.dll
6.0.2900.2598
27-Jan-2005
17:08
607,744
SP2QFE

Wininet.dll
6.0.2900.2598
27-Jan-2005
17:08
657,920
SP2QFE


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

If you have previously installed a hotfix to update an affected file, the installer copies the SP2QFE files to your system.

If you have not previously installed a hotfix to update an affected file, the installer copies the SP2GDR files to your system.

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

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

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

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 may be able to 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.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB867282\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 867282 security update into the Windows installation source files.


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

Note For Windows XP 64-Bit Edition Version 2003, this security update is the same as the Windows Server 2003 64-Bit Edition security update.

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 3, Service Pack 4

• Microsoft Windows XP Service Pack 1

• Microsoft Windows XP 64-Bit Edition, 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 will be included in a future Update Rollup.

Installation Information

This security update supports the following setup switches:

     /help                 Displays the command-line options

Setup Modes

     /quiet                Quiet mode (no user interaction or display)

     /passive            Unattended mode (progress bar only)

     /uninstall          Uninstalls the package

Restart Options

     /norestart          Do not restart when installation has completed

     /forcerestart      Restart after installation

Special Options

     /l                        Lists installed Windows hotfixes or update packages

     /o                       Overwrite OEM files without prompting

     /n                       Do not backup files needed for uninstall

     /f                        Force other programs to close when the computer shuts down

     /integrate:path  Integrates the update into the Windows source files located at the path specified

     /extract             Extracts files without starting the Setup program

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-KB867282-Windows-2000-XP-x86-enu /passive /quiet

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

IE6.0sp1-KB867282-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.

Restart Requirement

You must restart your system after you install this security update. You do not have to use an administrator logon after the computer restarts for any version of this 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%\$NTUninstallKB867282-ie6sp1-20050127.163319$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:

     /help                 Displays the command line options

Setup Modes

     /quiet                Quiet mode (no user interaction or display)

     /passive            Unattended mode (progress bar only)

Restart Options

     /norestart          Do not restart when installation is complete

     /forcerestart      Restart after installation

Special Options

     /f                        Force other programs to close when the computer shuts down

File Information

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

Internet Explorer 6 Service Pack 1 on Windows 2000 Service Pack 3, Windows 2000 Service Pack 4, and Windows XP Service Pack 1:

File Name Version Date Time Size Folder
Browseui.dll
6.0.2800.1612
08-Dec-2004
01:41
1,017,856
RTMGDR

Cdfview.dll
6.0.2800.1612
08-Dec-2004
01:43
143,360
RTMGDR

Iepeers.dll
6.0.2800.1485
07-Dec-2004
19:51
236,032
RTMGDR

Inseng.dll
6.0.2800.1469
26-Aug-2004
17:53
69,632
RTMGDR

Mshtml.dll
6.0.2800.1491
27-Jan-2005
23:35
2,806,272
RTMGDR

Shdocvw.dll
6.0.2800.1612
08-Dec-2004
01:34
1,337,344
RTMGDR

Shlwapi.dll
6.0.2800.1612
08-Dec-2004
02:11
402,432
RTMGDR

Urlmon.dll
6.0.2800.1485
08-Dec-2004
00:37
495,104
RTMGDR

Wininet.dll
6.0.2800.1485
08-Dec-2004
00:37
590,336
RTMGDR

Browseui.dll
6.0.2800.1612
08-Dec-2004
01:41
1,017,856
RTMQFE

Cdfview.dll
6.0.2800.1612
08-Dec-2004
01:43
143,360
RTMQFE

Iepeers.dll
6.0.2800.1486
08-Dec-2004
02:46
236,032
RTMQFE

Inseng.dll
6.0.2800.1475
24-Sep-2004
22:07
69,632
RTMQFE

Mshtml.dll
6.0.2800.1492
27-Jan-2005
22:20
2,699,776
RTMQFE

Shdocvw.dll
6.0.2800.1612
08-Dec-2004
01:34
1,337,344
RTMQFE

Shlwapi.dll
6.0.2800.1612
08-Dec-2004
02:11
402,432
RTMQFE

Urlmon.dll
6.0.2800.1487
13-Dec-2004
17:39
455,168
RTMQFE

Wininet.dll
6.0.2800.1486
08-Dec-2004
01:23
581,120
RTMQFE


Internet Explorer 6 Service Pack 1 on Windows XP 64-Bit Edition, Service Pack 1:

File Name Version Date Time Size CPU Folder
Browseui.dll
6.0.2800.1612
08-Dec-2004
01:42
2,869,760
IA-64
RTMGDR

Cdfview.dll
6.0.2800.1612
08-Dec-2004
01:43
319,488
IA-64
RTMGDR

Iepeers.dll
6.0.2800.1485
07-Dec-2004
20:45
783,872
IA-64
RTMGDR

Inseng.dll
6.0.2800.1469
26-Aug-2004
17:53
230,912
IA-64
RTMGDR

Mshtml.dll
6.0.2800.1491
27-Jan-2005
22:46
9,114,112
IA-64
RTMGDR

Shdocvw.dll
6.0.2800.1612
08-Dec-2004
01:36
3,670,016
IA-64
RTMGDR

Shlwapi.dll
6.0.2800.1612
08-Dec-2004
01:40
1,117,696
IA-64
RTMGDR

Urlmon.dll
6.0.2800.1485
07-Dec-2004
20:46
1,442,816
IA-64
RTMGDR

Wininet.dll
6.0.2800.1485
07-Dec-2004
20:46
1,798,656
IA-64
RTMGDR

Wbrowseui.dll
6.0.2800.1612
08-Dec-2004
01:41
1,017,856
x86
RTMGDR\WOW

Wcdfview.dll
6.0.2800.1612
08-Dec-2004
01:43
143,360
x86
RTMGDR\WOW

Wiepeers.dll
6.0.2800.1485
07-Dec-2004
19:51
236,032
x86
RTMGDR\WOW

Winseng.dll
6.0.2800.1469
26-Aug-2004
17:53
69,632
x86
RTMGDR\WOW

Wmshtml.dll
6.0.2800.1491
27-Jan-2005
23:35
2,806,272
x86
RTMGDR\WOW

Wshdocvw.dll
6.0.2800.1612
08-Dec-2004
01:34
1,337,344
x86
RTMGDR\WOW

Wshlwapi.dll
6.0.2800.1612
08-Dec-2004
02:11
402,432
x86
RTMGDR\WOW

Wurlmon.dll
6.0.2800.1485
08-Dec-2004
00:37
495,104
x86
RTMGDR\WOW

Wwininet.dll
6.0.2800.1485
08-Dec-2004
00:37
590,336
x86
RTMGDR\WOW

Browseui.dll
6.0.2800.1612
08-Dec-2004
01:42
2,869,760
IA-64
RTMQFE

Cdfview.dll
6.0.2800.1612
08-Dec-2004
01:43
319,488
IA-64
RTMQFE

Iepeers.dll
6.0.2800.1486
08-Dec-2004
02:46
783,872
IA-64
RTMQFE

Inseng.dll
6.0.2800.1475
24-Sep-2004
23:03
230,912
IA-64
RTMQFE

Mshtml.dll
6.0.2800.1492
27-Jan-2005
22:43
9,125,888
IA-64
RTMQFE

Shdocvw.dll
6.0.2800.1612
08-Dec-2004
01:36
3,670,016
IA-64
RTMQFE

Shlwapi.dll
6.0.2800.1612
08-Dec-2004
01:40
1,117,696
IA-64
RTMQFE

Urlmon.dll
6.0.2800.1487
13-Dec-2004
17:40
1,435,648
IA-64
RTMQFE

Wininet.dll
6.0.2800.1486
08-Dec-2004
01:24
1,827,840
IA-64
RTMQFE

Wbrowseui.dll
6.0.2800.1612
08-Dec-2004
01:41
1,017,856
x86
RTMQFE\WOW

Wcdfview.dll
6.0.2800.1612
08-Dec-2004
01:43
143,360
x86
RTMQFE\WOW

Wiepeers.dll
6.0.2800.1486
08-Dec-2004
02:46
236,032
x86
RTMQFE\WOW

Winseng.dll
6.0.2800.1475
24-Sep-2004
22:07
69,632
x86
RTMQFE\WOW

Wmshtml.dll
6.0.2800.1492
27-Jan-2005
22:20
2,699,776
x86
RTMQFE\WOW

Wshdocvw.dll
6.0.2800.1612
08-Dec-2004
01:34
1,337,344
x86
RTMQFE\WOW

Wshlwapi.dll
6.0.2800.1612
08-Dec-2004
02:11
402,432
x86
RTMQFE\WOW

Wurlmon.dll
6.0.2800.1487
13-Dec-2004
17:39
455,168
x86
RTMQFE\WOW

Wwininet.dll
6.0.2800.1486
08-Dec-2004
01:23
581,120
x86
RTMQFE\WOW


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 may be able to 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 confirming that an Installed DWORD value with a data value of 1 exists in the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB867282-ie6sp1-20050127.163319

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 867282 security update into the Windows installation source files.


Top of section
Internet Explorer 5.01 for Windows 2000 (all versions)

Prerequisites
To install the Internet Explorer 5.01 version of this update, you must be running one of the following combinations of Internet Explorer and Windows 2000:

• Internet Explorer 5.01 Service Pack 3 (version 5.00.3502.1000) on Windows 2000 SP3

• Internet Explorer 5.01 Service Pack 4 (version 5.00.3700.1000) on Windows 2000 SP4


Note: Versions of Windows and versions of Internet Explorer that are not listed in this article are no longer supported. Although you can install some of the update packages that are described in this article on these unlisted versions of Windows and of Internet Explorer, Microsoft has not tested them to assess whether they are affected by these vulnerabilities. Microsoft has also not tested these versions to confirm that the update that this bulletin describes addresses these vulnerabilities. We recommend that you upgrade to a supported version of Windows and of Internet Explorer, and then install the appropriate update.

For more information about support lifecycles for Windows components, see the following Microsoft Support Lifecycle Web site.

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

Installation Information

This security update supports the following setup switches:

     /help                 Displays the command-line options

Setup Modes

     /quiet                Quiet mode (no user interaction or display)

     /passive            Unattended mode (progress bar only)

     /uninstall          Uninstalls the package

Restart Options

     /norestart          Do not restart when installation has completed

     /forcerestart      Restart after installation

Special Options

     /l                        Lists installed Windows hotfixes or update packages

     /o                       Overwrite OEM files without prompting

     /n                       Do not backup files needed for uninstall

     /f                        Force other programs to close when the computer shuts down

     /integrate:path  Integrates the update into the Windows source files located at the path specified

     /extract             Extracts files without starting the Setup program

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 3:

IE5.01sp3-KB867282-Windows2000sp3-x86-enu /passive /quiet

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.01sp3-KB867282-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.

Restart Requirement

You must restart your system after you install this security update. You do not have to use an administrator logon after the computer restarts for any version of this 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%\$NTUninstallKB867282-ie501sp4- 20050107.164742$\Spuninst folder for Windows 2000 SP4 and %Windir%\$NTUninstallKB867282-ie501sp3-20050107.164329$\Spuninst for Windows 2000 SP3. The Spuninst.exe utility supports the following setup switches:

     /help                 Displays the command line options

Setup Modes

     /quiet                Quiet mode (no user interaction or display)

     /passive            Unattended mode (progress bar only)

Restart Options

     /norestart          Do not restart when installation is complete

     /forcerestart      Restart after installation

Special Options

     /f                        Force other programs to close when the computer shuts down

File Information

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

Internet Explorer 5.01 Service Pack 3 on Windows 2000 Service Pack 3:

File Name Version Date Time Size
Browseui.dll
5.0.3537.700
08-Dec-2004
06:28
792,336

Inseng.dll
5.0.3533.2600
26-Aug-2004
18:33
74,000

Mshtml.dll
5.0.3538.700
07-Jan-2005
23:45
2,293,008

Pngfilt.dll
5.0.3534.2300
24-Sep-2004
02:08
48,912

Shdocvw.dll
5.0.3537.700
08-Dec-2004
06:27
1,100,048

Shlwapi.dll
5.0.3900.7007
08-Dec-2004
06:49
282,384

Url.dll
5.50.4915.500
05-Mar-2002
04:53
84,240

Urlmon.dll
5.0.3537.700
08-Dec-2004
06:33
420,624

Wininet.dll
5.0.3537.700
08-Dec-2004
06:33
450,832


Internet Explorer 5.01 Service Pack 4 on Windows 2000 Service Pack 4

File Name Version Date Time Size
Browseui.dll
5.0.3824.700
08-Dec-2004
17:48
792,336

Inseng.dll
5.0.3820.2600
26-Aug-2004
19:03
74,000

Mshtml.dll
5.0.3825.700
07-Jan-2005
23:55
2,293,008

Pngfilt.dll
5.0.3821.2300
24-Sep-2004
02:08
48,912

Shdocvw.dll
5.0.3824.700
08-Dec-2004
17:48
1,100,048

Shlwapi.dll
5.0.3900.7007
08-Dec-2004
06:49
282,384

Url.dll
5.50.4915.500
05-Mar-2002
04:53
84,240

Urlmon.dll
5.0.3824.700
08-Dec-2004
17:54
420,624

Wininet.dll
5.0.3824.700
08-Dec-2004
17:54
450,832


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 may be able to 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 confirming that Installed DWORD value with a data value of 1 exists in the following registry keys.

Windows 2000 SP3: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB867282-ie501sp3-20050107.164329

Windows 2000 SP4: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB867282-ie501sp4-20050107.164742

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 867282 security update into the Windows installation source files.


Top of section
Top of section
Acknowledgments

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

• Michael Krax for working with us responsibly on the “Drag-and-Drop Vulnerability” (CAN-2005-0053).

• Andreas Sandblad of Secunia for working with us responsibly on the “Drag-and-Drop Vulnerability” (CAN-2005-0053).

• Jouko Pynnönen for reporting the URL Decoding Zone Spoofing Vulnerability (CAN-2005-0054).

• Andreas Sandblad of Secunia for reporting the DHTML Method Heap Memory Corruption Vulnerability (CAN-2005-0055).


Obtaining Other Security Updates:

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

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

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


Support:

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

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


Security Resources:

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

• Microsoft Software Update Services

• Microsoft Baseline Security Analyzer (MBSA)

• Windows Update

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

• Office Update


Software Update Services:

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

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

Disclaimer:

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

Revisions:

• V1.0 (February 8, 2005): Bulletin published

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