Microsoft Security Bulletin MS05-008
Vulnerability in Windows Shell Could Allow Remote Code Execution (890047)
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: Important
Recommendation: Customers should apply the update at the earliest opportunity.
Security Update Replacement: None
Caveats: None
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-014, 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 – Download the update
- Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 – Download the update
- Microsoft Windows XP 64-Bit Edition Service Pack 1 (Itanium) – Download the update
- Microsoft Windows XP 64-Bit Edition Version 2003 (Itanium) – Download the update
- Microsoft Windows Server 2003 – Download the update
- Microsoft Windows Server 2003 for Itanium-based Systems – Download the update
- 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.
The software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.
General Information
Executive Summary
Executive Summary:
This update resolves a newly-discovered vulnerability. The vulnerability is documented in the “Vulnerability Details” section of this bulletin. A privilege elevation vulnerability exists in Windows because of the way that Windows 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.
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. However, user interaction is required to exploit this vulnerability.
We recommend that customers apply the update at the earliest opportunity.
Severity Ratings and Vulnerability Identifiers:
| Vulnerability Identifiers | Impact of Vulnerability | Windows 98, 98 SE, ME | Windows 2000 | Windows XP | Windows Server 2003 |
|---|---|---|---|---|---|
| Drag-and-Drop Vulnerability - CAN-2005-0053 | Remote Code Execution | Not Critical | Important | Important | Moderate |
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.
Frequently asked questions (FAQ) related to this security update
How does this update relate to the Drag and Drop update for Internet Explorer?
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-014, 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.
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.
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.
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?
No. None of these vulnerabilities are critical in severity on Windows 98, on Windows 98 Second Edition, or on Windows Millennium Edition. For more information about severity ratings, visit the following 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 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 1.2 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. The Security Update Inventory Tool is required for detecting Microsoft Windows and other affected Microsoft products. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460.
Vulnerability Details
Drag-and-Drop Vulnerability - CAN-2005-0053
A privilege elevation vulnerability exists in Windows because of the way that Windows 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.
- This vulnerability allows an attacker to put malicious code on the user’s system in specified locations. An attack could only occur after the user ran this code by restarting the system, by logging off and then logging back on to the system, or by unintentionally running the code that the attacker saved locally on the system.
- 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 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.
- 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.
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:
- 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.
- 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:
- In Internet Explorer, click Internet Options on the Tools menu, and then click the Security tab.
- In the Select a Web content zone to specify its security settings box, click Internet, and then click Custom Level.
- In the Settings box, locate the Drag and drop or copy and paste files option under Miscellaneous. Make a note of your current setting.
- Under Drag and drop or copy and paste files, click Disable, and then click OK.
- 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:
- On the Internet Explorer Tools menu, click Internet Options.
- In the Internet Options dialog box, click the Security tab, and then click the Internet icon.
- 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:
- In Internet Explorer, click Internet Options on the Tools menu.
- Click the Security tab.
- Click Internet, and then click Custom Level.
- Under Settings, in the ActiveX controls and plug-ins section, under Run ActiveX controls and plug-ins, click Prompt.
- In the Scripting section, under Active Scripting, click Prompt, and then click OK.
- Click Local intranet, and then click Custom Level.
- Under Settings, in the ActiveX controls and plug-ins section, under Run ActiveX controls and plug-ins, click Prompt.
- In the Scripting section, under Active Scripting, click Prompt.
- 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:
- In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
- In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
- 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.
- In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
- Repeat these steps for each site that you want to add to the zone.
- 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.
FAQ for Drag-and-Drop Vulnerability - CAN-2005-0053:
What is the scope of the vulnerability?
This vulnerability involves drag and drop events in Windows. 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 DHTML 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 vulnerability?
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 Windows validates some drag and drop events.
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 issues: 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 that is currently being exploited. The vulnerability that has been addressed has been assigned the Common Vulnerability and Exposure number CAN-2005-0053.
Security Update Information
Affected Software:
For information about the specific security update for your affected software, click the appropriate link:
Windows Server 2003 (all versions)
Prerequisites
This security update requires a release version of Windows Server 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-kb890047-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-kb890047-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.
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%\$NTUninstallKB890047$\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 |
|---|---|---|---|---|---|
| Shell32.dll | 6.0.3790.241 | 13-Dec-2004 | 20:44 | 8,171,008 | RTMGDR |
| Shell32.dll | 6.0.3790.241 | 13-Dec-2004 | 20:33 | 8,171,520 | 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 |
|---|---|---|---|---|---|---|
| Shell32.dll | 6.0.3790.241 | 13-Dec-2004 | 20:37 | 12,960,768 | IA-64 | RTMGDR |
| Wshell32.dll | 6.0.3790.241 | 13-Dec-2004 | 20:44 | 8,171,008 | x86 | RTMGDR\WOW |
| Shell32.dll | 6.0.3790.241 | 13-Dec-2004 | 20:33 | 12,962,304 | IA-64 | RTMQFE |
| Wshell32.dll | 6.0.3790.241 | 13-Dec-2004 | 20:33 | 8,171,520 | 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.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed. - On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
- Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the following registry keys.
Windows Server 2003, Web Edition; 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\KB890047\Filelist
Note This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly if an administrator or an OEM integrates or slipstreams the 890047 security update into the Windows installation source files.
Windows XP (all versions)
Prerequisites
This security update requires Microsoft Windows XP Service Pack 1 or a later version. For more information, see Microsoft Knowledge Base Article 322389.
Inclusion in Future Service Packs:
The update for this issue will be included in a future Service Pack or Update Rollup.
Installation Information
This security update supports the following setup switches:
/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:
Windowsxp-kb890047-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:
Windowsxp-kb890047-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.
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%\$NTUninstallKB890047$\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 XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| Fldrclnr.dll | 6.0.2800.1579 | 20-Aug-2004 | 22:01 | 82,432 | SP1QFE |
| Shell32.dll | 6.0.2800.1613 | 21-Dec-2004 | 20:55 | 8,443,904 | SP1QFE |
| Sxs.dll | 5.1.2600.1579 | 20-Aug-2004 | 22:01 | 700,928 | SP1QFE |
| Comctl32.dll | 6.0.2800.1612 | 21-Dec-2004 | 20:55 | 921,600 | SP1QFE\ASMS\60\MSFT\WINDOWS\COMMON\CONTROLS |
| Controls.man | 21-Dec-2004 | 21:01 | 1,812 | SP1QFE\ASMS\60\MSFT\WINDOWS\COMMON\CONTROLS | |
| Comctl.man | 21-Dec-2004 | 21:01 | 621 | SP1QFE\ASMS\60\POLICY\60\COMCTL | |
| Shell32.dll | 6.0.2900.2578 | 21-Dec-2004 | 20:49 | 8,450,048 | SP2GDR |
| Shell32.dll | 6.0.2900.2578 | 21-Dec-2004 | 20:50 | 8,451,072 | SP2QFE |
Windows XP 64-Bit Edition Service Pack 1 (Itanium):
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| Fldrclnr.dll | 6.0.2800.1579 | 20-Aug-2004 | 21:52 | 130,560 | IA-64 | SP1QFE |
| Shell32.dll | 6.0.2800.1613 | 21-Dec-2004 | 20:55 | 14,395,904 | IA-64 | SP1QFE |
| Sxs.dll | 5.1.2600.1579 | 20-Aug-2004 | 21:52 | 2,034,176 | IA-64 | SP1QFE |
| Comctl32.dll | 6.0.2800.1612 | 21-Dec-2004 | 20:55 | 2,639,360 | IA-64 | SP1QFE\ASMS\60\MSFT\WINDOWS\COMMON\CONTROLS |
| Controls.man | 21-Dec-2004 | 21:03 | 1,813 | SP1QFE\ASMS\60\MSFT\WINDOWS\COMMON\CONTROLS | ||
| Comctl.man | 21-Dec-2004 | 21:03 | 623 | SP1QFE\ASMS\60\POLICY\60\COMCTL | ||
| Comctl32.dll | 6.0.2800.1612 | 12-Jan-2005 | 19:05 | 922,112 | x86 | SP1QFE\ASMS\X86\60\MSFT\WINDOWS\COMMON\CONTROLS |
| Controls.man | 12-Jan-2005 | 19:06 | 1,814 | SP1QFE\ASMS\X86\60\MSFT\WINDOWS\COMMON\CONTROLS | ||
| Comctl.man | 12-Jan-2005 | 19:06 | 625 | SP1QFE\ASMS\X86\60\POLICY\60\COMCTL | ||
| Wfldrclnr.dll | 6.0.2800.1579 | 20-Aug-2004 | 22:01 | 82,432 | x86 | SP1QFE\WOW |
| Wshell32.dll | 6.0.2800.1613 | 12-Jan-2005 | 19:05 | 8,443,904 | x86 | SP1QFE\WOW |
| Wsxs.dll | 5.1.2600.1579 | 20-Aug-2004 | 22:01 | 700,928 | x86 | SP1QFE\WOW |
Windows XP 64-Bit Edition Version 2003 (Itanium):
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| Shell32.dll | 6.0.3790.241 | 13-Dec-2004 | 20:37 | 12,960,768 | IA-64 | RTMGDR |
| Wshell32.dll | 6.0.3790.241 | 13-Dec-2004 | 20:44 | 8,171,008 | x86 | RTMGDR\WOW |
| Shell32.dll | 6.0.3790.241 | 13-Dec-2004 | 20:33 | 12,962,304 | IA-64 | RTMQFE |
| Wshell32.dll | 6.0.3790.241 | 13-Dec-2004 | 20:33 | 8,171,520 | x86 | RTMQFE\WOW |
Notes The Windows XP and Windows XP 64-Bit Edition Version 2003 (Itanium) versions of this security update are packaged as dual-mode packages. These dual-mode packages contain files for the original version of Windows XP Service Pack 1 (SP1) and files for Windows XP Service Pack 2 (SP2).
For more information about dual-mode packages, see Microsoft Knowledge Base Article 328848.
When you install this security update on Windows XP SP2 or on Windows XP 64-Bit Edition Version 2003 (Itanium), 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, one of the following conditions occurs, depending on your operating system:
- Windows XP SP2
The installer copies the SP2QFE files to your system. - Windows XP 64-Bit Edition Version 2003 (Itanium)
The installer copies the RTMQFE files to your system.
If you have not previously installed a hotfix to update an affected file, one of the following conditions occurs, depending on your operating system:
- Windows XP SP2
The installer copies the SP2GDR files to your system. - Windows XP 64-Bit Edition Version 2003 (Itanium)
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.
Note For Windows XP 64-Bit Edition Version 2003 (Itanium), this security update is the same as the Windows Server 2003 for Itanium-based Systems security update.
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.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed. - On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
- Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the following registry keys.
For Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB890047\Filelist
For Windows XP 64-Bit Edition Version 2003 (Itanium):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB890047\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 890047 security update into the Windows installation source files.
Windows 2000 (all versions)
Prerequisites
For Windows 2000, this security update requires Service Pack 3 (SP3) or Service Pack 4 (SP4). For Small Business Server 2000, this security update requires Small Business Server 2000 Service Pack 1a or Small Business Server 2000 running with Windows 2000 Server Service Pack 4.
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 2000 Service Pack 3 and Windows 2000 Service Pack 4:
Windows2000-kb890047-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:
Windows2000-kb890047-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 apply this security update.
Removal Information
To remove this security update, use the Add or Remove Programs tool in Control Panel.
System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB890047$\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 2000 Service Pack 3, Windows 2000 Service Pack 4, and Small Business Server 2000:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Shell32.dll | 5.0.3900.7009 | 10-Dec-2004 | 09:27 | 2,359,056 |
| Sp3res.dll | 5.0.2195.7004 | 02-Dec-2004 | 14:27 | 6,272,512 |
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.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed. - On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
- Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB890047\Filelist
Note This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly when an administrator or an OEM integrates or slipstreams the 890047 security update into the Windows installation source files.
Other Information
Obtaining Other Security Updates:
Updates for other security issues are available at the following locations:
- Security updates are available 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 Microsoft Update Web site.
Support:
- Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
- International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.
Security Resources:
- The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
- Microsoft Software Update Services
- Microsoft Baseline Security Analyzer (MBSA)
- Microsoft Update
- Windows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.
- Office Update
Software Update Services:
By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.
For more information about how to deploy 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