Microsoft Security Bulletin MS04-037
Vulnerability in Windows Shell Could Allow Remote Code Execution (841356)
Issued: October 12, 2004
Updated: February 15, 2005
Version: 1.2
Summary
Who should read this document: Customers who use Microsoft Windows
Impact of Vulnerability: Remote Code Execution
Maximum Severity Rating: Critical
Recommendation: Customers should apply the update immediately.
Security Update Replacement: This bulletin replaces several prior security updates. See the frequently asked questions (FAQ) section of this bulletin for the complete list.
Caveats: Microsoft Knowledge Base Article 841356 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 841356.
Tested Software and Security Update Download Locations:
Affected Software:
- Microsoft Windows NT Server 4.0 Service Pack 6a – Download the update
- Microsoft Windows NT Server 4.0 Terminal Server Edition Service Pack 6 – Download the update
- Microsoft Windows 2000 Service Pack 3 and Microsoft Windows 2000 Service Pack 4 – Download the update
- Microsoft Windows XP and Microsoft Windows XP Service Pack 1 – Download the update
- Microsoft Windows XP 64-Bit Edition Service Pack 1 – Download the update
- Microsoft Windows XP 64-Bit Edition Version 2003 – Download the update
- Microsoft Windows Server 2003 – Download the update
- Microsoft Windows Server 2003 64-Bit Edition – 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.
Non-Affected Software:
- Microsoft Windows XP Service Pack 2
The software in this list has been tested to determine if the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support lifecycle for your product and version, visit the following Microsoft Support Lifecycle Web site.
General Information
Executive Summary
Executive Summary:
This update resolves several newly-discovered, public vulnerabilities. Each vulnerability is documented in this bulletin in its own Vulnerability Details section.
If a user is logged on with administrative privileges, an attacker who successfully exploited the most severe of these vulnerabilities could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts with full privileges. Users whose accounts are configured to have fewer privileges on the system would be at less risk than users who operate with administrative privileges. However, user interaction is required to exploit these vulnerabilities.
We recommend that customers apply the update immediately.
Severity Ratings and Vulnerability Identifiers:
| Vulnerability Identifiers | Impact of Vulnerability | Windows 98, 98 SE, ME | Windows NT 4.0 | Windows 2000 | Windows XP and Windows XP Service Pack 1 | Windows Server 2003 |
|---|---|---|---|---|---|---|
| Shell Vulnerability - CAN-2004-0214 | Remote Code Execution | Not Critical | Critical | Critical | Critical | None |
| Program Group Converter Vulnerability - CAN-2004-0572 | Remote Code Execution | Not Critical | Important | Important | Important | Important |
| Aggregate Severity of All Vulnerabilities | Not Critical | Critical | Critical | Critical | Important |
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
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 bulletins. The security bulletin IDs and operating systems that are affected are listed in the following table.
| Bulletin ID | Windows NT 4.0 | Windows 2000 | Windows XP | Windows Server 2003 |
|---|---|---|---|---|
| MS02-014 | Replaced | Replaced | Not Applicable | Not Applicable |
| MS03-027 | Not Applicable | Not Applicable | Replaced | Not Applicable |
Does this update contain any other security-related changes?
Yes. In addition to the changes that are listed in the Vulnerability Details section of this bulletin, this update includes the following changes:
- On Windows XP and Windows Server 2003, we have made a defense in depth change that limits the functionality of the Shell. This change in functionality prevents the use of the “shell:” protocol so that it does not automatically start applications that have known filename extension mappings when it processes certain types of malformed requests. This change is consistent with the default settings in Windows XP Service Pack 2.
- On Windows XP and Windows Server 2003 we have made another defense in depth change that prevents the Shell from using the “shell:” protocol to reference files. This protocol was designed to reference system objects and folders, not to reference files. This change is consistent with the default settings in Windows XP Service Pack 2.
I am still using Windows XP, but extended security update support ended on September 30th, 2004. However, this bulletin has a security update for this operating system version. Why is that?
The original version of Windows XP, commonly 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. However, the end-of-life occurred very recently. In this case, the majority of the steps that are required to address this vulnerability were completed before this date. Therefore, we have decided to release a security update for this operating system version as part of this security bulletin.
We do not anticipate doing this for future vulnerabilities that may affect this operating system version, but we reserve the right to produce updates and to make these updates available when necessary. 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 Life Cycle, visit the Microsoft Support Lifecycle Web site. For more information about the Windows Product Life Cycle, visit the Microsoft Support Lifecycle Web site.
For more information, visit the Windows Operating System FAQ.
I am still using Microsoft Windows NT 4.0 Workstation Service Pack 6a or Windows 2000 Service Pack 2, but extended security update support ended on June 30, 2004. What should I do?
Windows NT 4.0 Workstation Service Pack 6a and Windows 2000 Service Pack 2 have reached the end of their life cycles as previously documented, and Microsoft extended this support to June 30, 2004.
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 Life Cycle, 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 Workstation 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 phone numbers. When you call, ask to speak with the local Premier Support sales manager.
For more information, visit the Windows Operating System 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 any 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 if this update is required?
Yes. MBSA will determine if 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 with 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 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 if this update is required?
Yes. SMS can help detect and deploy this security update. SMS can search for the existence of the affected files that are documented in the Security Update Information section of this bulletin. Update all versions of affected files that are earlier than versions that are documented in this security bulletin. For information about SMS, visit the SMS Web site.
Vulnerability Details
Shell Vulnerability - CAN-2004-0214:
A remote code execution vulnerability exists in the way that the Windows Shell starts applications. An attacker could exploit the vulnerability if a user visited a malicious Web site. If a user is logged on with administrative privileges, 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 Shell Vulnerability - CAN-2004-0214:
- In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's Web site. An attack could only occur after they performed this action.
- An attacker who successfully exploited this vulnerability could gain the same privileges as the user. Users whose accounts are configured to have fewer privileges on the system would be at less risk than users who operate with administrative privileges.
- By default, Outlook Express 6, Outlook 2002, and Outlook 2003 open HTML e-mail messages in the Restricted sites zone. Additionally, Outlook 98 and Outlook 2000 open HTML e-mail messages in the Restricted sites zone if the Outlook E-mail Security Update has been installed. Outlook Express 5.5 Service Pack 2 opens HTML e-mail messages in the Restricted sites zone if Microsoft Security Bulletin MS04-018 has been installed. The Restricted sites zone helps reduce attacks that could attempt 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 Internet Explorer 6 or later.
- Use the Microsoft Outlook E-mail Security Update, use Microsoft Outlook Express 6 or later, or use Microsoft Outlook 2000 Service Pack 2 or later in its default configuration.
Workarounds for Shell Vulnerability - CAN-2004-0214:
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 below.
- Install the Outlook E-mail Security Update if you are using Outlook 2000 SP1 or earlier to help protect yourself from the HTML e-mail attack vector.
By default, Outlook Express 6, Outlook 2002 and Outlook 2003 open HTML e-mail messages in the Restricted sites zone. Additionally, Outlook 98 and Outlook 2000 open HTML e-mail messages in the Restricted sites zone if the Outlook E-mail Security Update has been installed. Outlook Express 5.5 Service Pack 2 opens HTML e-mail in the Restricted sites zone if Microsoft Security Bulletin MS04-018 has been installed. The Restricted sites zone helps reduce attacks that could attempt to exploit this vulnerability.
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 later, or Outlook Express 6 SP1 or later, to help protect yourself from the HTML e-mail attack vector.
Microsoft Outlook 2002 users who have applied Office XP Service Pack 1 or later and Microsoft 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. In addition:
- 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 Shell Vulnerability - CAN-2004-0214:
What is the scope of the vulnerability?
This is remote code execution vulnerability. If a user is logged on with administrative privileges, an attacker who successfully exploited this vulnerability could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts with full privileges. However, user interaction is required to exploit this vulnerability. Users whose accounts are configured to have fewer privileges on the system would be at less risk than users who operate with administrative privileges.
What causes the vulnerability?
Unchecked buffers in Windows Shell functions.
What is the Windows Shell?
The Microsoft Windows user interface (UI) provides users with access to a wide variety of objects that are necessary for running applications and managing the operating system. The most numerous and familiar of these objects are the folders and files that reside on computer disk drives. There are also a number of virtual objects that allow the user to do tasks such as sending files to remote printers or accessing the Recycle Bin. The Shell organizes these objects into a hierarchical namespace and provides users and applications with a consistent and efficient way to access and manage objects. For more information, visit the following Web site.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could gain the same privileges as the user. Users whose accounts are configured to have fewer privileges on the system would be at less risk than users who operate with administrative privileges.
How could an attacker exploit the vulnerability?
To exploit this vulnerability, an attacker would have to host a malicious Web site and then persuade a user to view that Web site. An attacker could also create an e-mail message that has a specially crafted link, and then persuade a user to view the e-mail message and then click the malicious link.
What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers are only at risk if users are given the ability to log on and to run programs. However, best practices strongly discourage allowing this.
Are Windows 98, Windows 98 Second Edition or Windows Millennium Edition critically affected by this vulnerability?
No. Although Windows Millennium Edition does contain the affected component, the vulnerability is not critical. For more information about severity ratings, visit the following Web site.
Could the vulnerability be exploited over the Internet?
Yes. An attacker could attempt to exploit this vulnerability over the Internet.
What does the update do?
The update removes the vulnerability by modifying the way that the Windows Shell 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?
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CAN-2004-0214.
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 indicating that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.
Program Group Converter Vulnerability- CAN-2004-0572:
A remote code execution vulnerability exists in Program Group Converter because of the way that it handles specially crafted requests. An attacker could exploit the vulnerability by constructing a malicious request that could potentially allow remote code execution if a user performed an action such as opening a file attachment or clicking a HTML link. If a user is logged on with administrative privileges, 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 Program Group Converter Vulnerability - CAN-2004-0572:
- In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. An attack could only occur after they performed this action.
- An attacker who successfully exploited this vulnerability could gain the same privileges as the user. Users whose accounts are configured to have fewer privileges on the system would be at less risk than users who operate with administrative privileges.
- By default, Outlook Express 6, Outlook 2002, and Outlook 2003 open HTML e-mail messages in the Restricted sites zone. Additionally, Outlook 98 and Outlook 2000 open HTML e-mail messages in the Restricted sites zone if the Outlook E-mail Security Update has been installed. Outlook Express 5.5 Service Pack 2 opens HTML e-mail in the Restricted sites zone if Microsoft Security Bulletin MS04-018 has been installed. The Restricted sites zone helps reduce attacks that could attempt 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 Internet Explorer 6 or later.
- Use the Microsoft Outlook E-mail Security Update, use Microsoft Outlook Express 6 or later, or use Microsoft Outlook 2000 Service Pack 2 or later in its default configuration.
Workarounds for Program Group Converter - CAN-2004-0572:
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 below.
- Install the Outlook E-mail Security Update if you are using Outlook 2000 SP1 or earlier to help protect yourself from the HTML e-mail attack vector.
By default, Outlook Express 6, Outlook 2002 and Outlook 2003 open HTML e-mail messages in the Restricted sites zone. Additionally, Outlook 98 and Outlook 2000 open HTML e-mail messages in the Restricted sites zone if the Outlook E-mail Security Update has been installed. Outlook Express 5.5 Service Pack 2 opens HTML e-mail messages in the Restricted sites zone if Microsoft Security Bulletin MS04-018 has been installed. The Restricted sites zone helps reduce attacks that could attempt to exploit this vulnerability.
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 later, or Outlook Express 6 SP1 or later, to help protect yourself from the HTML e-mail attack vector.
Microsoft Outlook 2002 users who have applied Office XP Service Pack 1 or later and Microsoft 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. In addition:
- 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.
- Do not open or save .grp files that you receive from untrusted sources.
This vulnerability could be exploited when a user views a .grp file. Do not open files that use this file name extension. - Remove the association between .grp files and the grpconv.exe application on Windows XP, Windows XP Service Pack 1, and Windows Server 2003.
To enable the workaround, follow these steps the following steps as a local administrator:
- Put the following code in a file named Un-grpconv.inf:
[Version]
Signature="$CHICAGO$"
[DefaultInstall]
DelReg=DisableGrpAssociation.DelReg
AddReg=DisableGrpAssociation.AddReg
[DisableGrpAssociation.DelReg]
HKCR,"MSProgramGroup"
[DisableGrpAssociation.AddReg]
HKCR,".grp",,,""
HKCR,"MSProgramGroup",,,""
[DisableGrpAssociation.AddReg.Security]
"D:(D;CI;6;;;WD)(A;ID;KR;;;BU)(A;CIIOID;GR;;;BU)(A;ID;0x3001F;;;PU)(A;CIIOID;SDGWGR;;;PU)(A;ID;KA;;;BA)(A;CIIOID;GA;;;BA)(A;ID;KA;;;SY)(A;CIIOID;GA;;;SY)(A;CIIOID;GA;;;CO)" - Right-click on Un-grpconv.inf and then click Install.
To disable the workaround and revert to default behavior, follow these steps as a local administrator:
- Put the following code in a file named Grpconv.inf.
[Version]
Signature="$CHICAGO$"
[DefaultInstall]
DelReg=EnableGrpAssociation.DelReg
[EnableGrpAssociation.DelReg]
HKCR,"MSProgramGroup"
HKCR,".grp" - Right-click on Grpconv.inf and then click Install.
Note: This workaround is only designed for Windows XP, Windows XP Service Pack 1, and Windows Server 2003. This workaround does function correctly on other affected operating systems
- Put the following code in a file named Un-grpconv.inf:
FAQ for Program Group Converter - CAN-2004-0572:
What is the scope of the vulnerability?
This is remote code execution vulnerability. If a user is logged on with administrative privileges, an attacker who successfully exploited this vulnerability could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts with full privileges. Users whose accounts are configured to have fewer privileges on the system would be at less risk than users who operate with administrative privileges. However, user interaction is required to exploit this vulnerability.
What causes the vulnerability?
An unchecked buffer in the Program Group Converter application.
What is Program Group Converter?
The Program Group Converter was used to convert Program Manager Group files that were created in Windows 3.1, Windows 3.11, Windows for Workgroups 3.1, and Windows for Workgroups 3.11 so that they could be used by later operating systems. This application is also used during Windows Setup and by third-party applications during the installation of applications or devices. For more information about Program Group Converter, visit the following Web site.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could gain the same privileges as the user. Users whose accounts are configured to have fewer privileges on the system would be at less risk than users who operate with administrative privileges.
How could an attacker exploit the vulnerability?
To exploit this vulnerability, an attacker could host a malicious Web site and then persuade a user to visit that Web site. An attacker could also create an HTML e-mail message that contains a specially crafted link, and then persuade a user to view the HTML e-mail message and click the link. An attacker could also send a specially crafted .grp file to a user, and then persuade the user to open the file.
An attacker could also access the affected component through another vector. For example, an attacker could use another program that passes parameters to the vulnerable component (locally or remotely).
What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers are only at risk if users are given the ability to log on and to run programs. However, best practices strongly discourage allowing this.
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.
Could the vulnerability be exploited over the Internet?
Yes. An attacker could attempt to exploit this vulnerability over the Internet.
What does the update do?
The update removes the vulnerability by modifying the way that the Program Group Converter application 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?
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CAN-2004-0572.
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 indicating that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.
Security Update Information
Installation Platforms and Prerequisites:
For information about the specific security update for your platform, 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 is complete
/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
/extract Extracts files without starting setup
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the previous version of the setup utility uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Deployment Information
To install the security update without any user intervention, use the following command at a command prompt for Windows Server 2003:
Windowsserver2003-kb841356-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-kb841356-x86-enu /norestart
For 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 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%\$NTUninstallKB841356$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:
/?: Show the list of installation switches.
/u: Use unattended mode.
/f: Force other programs to quit when the computer shuts down.
/z: Do not restart when the installation is complete.
/q: Use Quiet mode (no user interaction).
File Information
The English version of this update has the file attributes (or later) 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 Enterprise Edition, Windows Server 2003 Standard Edition, Windows Server 2003 Web Edition, and Windows Server 2003 Datacenter Edition:
Date Time Version Size File name Folder
-------------------------------------------------------------------------
20-Aug-2004 17:39 5.2.3790.205 40,960 Grpconv.exe RTMGDR
23-Aug-2004 17:16 6.0.3790.205 8,170,496 Shell32.dll RTMGDR
23-Aug-2004 17:16 6.0.3790.205 287,232 Shlwapi.dll RTMGDR
20-Aug-2004 17:42 5.2.3790.205 37,376 Grpconv.exe RTMQFE
23-Aug-2004 17:10 6.0.3790.205 8,171,008 Shell32.dll RTMQFE
23-Aug-2004 17:10 6.0.3790.205 287,232 Shlwapi.dll RTMQFE
Windows Server 2003 64-Bit Enterprise Edition and Windows Server 2003 64-Bit Datacenter Edition:
Date Time Version Size File name Platform Folder
------------------------------------------------------------------------------------
20-Aug-2004 17:45 5.2.3790.205 120,832 Grpconv.exe IA-64 RTMGDR
23-Aug-2004 17:10 6.0.3790.205 12,959,232 Shell32.dll IA-64 RTMGDR
23-Aug-2004 17:10 6.0.3790.205 738,816 Shlwapi.dll IA-64 RTMGDR
20-Aug-2004 17:39 5.2.3790.205 40,960 Wgrpconv.exe x86 RTMGDR\WOW
23-Aug-2004 17:16 6.0.3790.205 8,170,496 Wshell32.dll x86 RTMGDR\WOW
23-Aug-2004 17:16 6.0.3790.205 287,232 Wshlwapi.dll x86 RTMGDR\WOW
20-Aug-2004 17:49 5.2.3790.205 110,592 Grpconv.exe IA-64 RTMQFE
23-Aug-2004 17:10 6.0.3790.205 12,960,768 Shell32.dll IA-64 RTMQFE
23-Aug-2004 17:10 6.0.3790.205 738,816 Shlwapi.dll IA-64 RTMQFE
20-Aug-2004 17:42 5.2.3790.205 37,376 Wgrpconv.exe x86 RTMQFE\WOW
23-Aug-2004 17:10 6.0.3790.205 8,171,008 Wshell32.dll x86 RTMQFE\WOW
23-Aug-2004 17:10 6.0.3790.205 287,232 Wshlwapi.dll x86 RTMQFE\WOW
Note When you install this security update on Windows Server 2003 or on Windows XP 64-Bit Edition Version 2003, the installer checks to see if any of the files that are being updated on your system have previously been updated by a Microsoft hotfix. If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE files to your system. Otherwise, the installer copies the RTMGDR files to your system. For more information, see Microsoft Knowledge Base Article 824994.
Verifying Update Installation
- Microsoft Baseline Security Analyzer
To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. This tool 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 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 the update installation. 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 Server 2003\SP1\KB841356\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 841356 security update into the Windows installation source files.
Windows XP (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
This security update requires the release version of Windows XP or Windows XP Service Pack 1 (SP1). For more information, see Microsoft Knowledge Base Article 322389.
Inclusion in Future Service Packs:
The update for this issue is included in Windows XP Service Pack 2.
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 is complete
/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
/extract Extracts files without starting setup
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the previous version of the setup utility uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Deployment Information
To install the security update without any user intervention, use the following command at a command prompt for Windows XP:
Windowsxp-kb841356-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-kb841356-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 is located in the %Windir%\$NTUninstallKB841356$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:
/?: Show the list of installation switches.
/u: Use unattended mode.
/f: Force other programs to quit when the computer shuts down.
/z: Do not restart when the installation is complete.
/q: Use Quiet mode (no user interaction).
File Information
The English version of this update has the file attributes (or later) 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, Windows XP Professional, Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, and Windows XP Media Center Edition:
Date Time Version Size File name Folder
---------------------------------------------------------------------------
20-Aug-2004 21:41 6.0.2750.165 84,992 Fldrclnr.dll RTMQFE
30-Jul-2004 02:12 5.1.2600.166 38,400 Grpconv.exe RTMQFE
20-Aug-2004 21:41 5.1.2600.165 15,872 Linkinfo.dll RTMQFE
20-Aug-2004 21:41 5.1.2600.165 37,376 Ntlanman.dll RTMQFE
20-Aug-2004 21:41 6.0.2750.166 8,227,840 Shell32.dll RTMQFE
20-Aug-2004 21:41 6.0.2750.167 393,728 Shlwapi.dll RTMQFE
29-Jul-2004 06:19 5.5.31.0 30,720 Xpsp1hfm.exe RTMQFE
20-Aug-2004 22:01 6.0.2800.1579 82,432 Fldrclnr.dll SP1QFE
29-Jul-2004 22:50 5.1.2600.1580 38,400 Grpconv.exe SP1QFE
20-Aug-2004 22:01 5.1.2600.1579 15,872 Linkinfo.dll SP1QFE
20-Aug-2004 22:01 6.0.2800.1580 8,442,368 Shell32.dll SP1QFE
20-Aug-2004 22:01 6.0.2800.1584 422,912 Shlwapi.dll SP1QFE
20-Aug-2004 22:01 5.1.2600.1579 700,928 Sxs.dll SP1QFE
30-Jul-2004 21:29 5.1.2600.1580 594,432 Xpsp2res.dll SP1QFE
20-Aug-2004 22:01 6.0.2800.1579 921,600 Comctl32.dll SP1QFE\Asms\60\Msft\Windows\Common\Controls
20-Aug-2004 22:03 1,812 Controls.man SP1QFE\Asms\60\Msft\Windows\Common\Controls
Windows XP 64-Bit Edition Service Pack 1:
Date Time Version Size File name Platform Folder
------------------------------------------------------------------------------
20-Aug-2004 21:52 6.0.2800.1579 130,560 Fldrclnr.dll IA-64 SP1QFE
29-Jul-2004 23:20 5.1.2600.1580 130,048 Grpconv.exe IA-64 SP1QFE
20-Aug-2004 21:52 5.1.2600.1579 50,176 Linkinfo.dll IA-64 SP1QFE
20-Aug-2004 21:52 6.0.2800.1580 14,392,320 Shell32.dll IA-64 SP1QFE
20-Aug-2004 21:52 6.0.2800.1584 1,117,184 Shlwapi.dll IA-64 SP1QFE
20-Aug-2004 21:52 5.1.2600.1579 2,034,176 Sxs.dll IA-64 SP1QFE
30-Jul-2004 19:20 5.1.2600.1580 593,920 Xpsp2res.dll IA-64 SP1QFE
20-Aug-2004 21:52 6.0.2800.1579 2,639,360 Comctl32.dll IA-64 SP1QFE\Asms\60\Msft\Windows\Common\Controls
20-Aug-2004 22:06 1,813 Controls.man SP1QFE\Asms\60\Msft\Windows\Common\Controls
20-Aug-2004 22:06 623 Comctl.man SP1QFE\Asms\60\Policy\60\Comctl
20-Aug-2004 22:01 6.0.2800.1579 82,432 Wfldrclnr.dll x86 SP1QFE\WOW
29-Jul-2004 22:50 5.1.2600.1580 38,400 Wgrpconv.exe x86 SP1QFE\WOW
20-Aug-2004 22:01 5.1.2600.1579 15,872 Wlinkinfo.dll x86 SP1QFE\WOW
20-Aug-2004 22:01 6.0.2800.1580 8,442,368 Wshell32.dll x86 SP1QFE\WOW
20-Aug-2004 22:01 6.0.2800.1584 422,912 Wshlwapi.dll x86 SP1QFE\WOW
20-Aug-2004 22:01 5.1.2600.1579 700,928 Wsxs.dll x86 SP1QFE\WOW
30-Jul-2004 21:30 5.1.2600.1580 594,432 Wxpsp2res.dll x86 SP1QFE\WOW
Windows XP 64-Bit Edition Version 2003:
Date Time Version Size File name Platform Folder
-------------------------------------------------------------------------
20-Aug-2004 17:45 5.2.3790.205 120,832 Grpconv.exe IA-64 RTMGDR
23-Aug-2004 17:10 6.0.3790.205 12,959,232 Shell32.dll IA-64 RTMGDR
23-Aug-2004 17:10 6.0.3790.205 738,816 Shlwapi.dll IA-64 RTMGDR
20-Aug-2004 17:39 5.2.3790.205 40,960 Wgrpconv.exe x86 RTMGDR\WOW
23-Aug-2004 17:16 6.0.3790.205 8,170,496 Wshell32.dll x86 RTMGDR\WOW
23-Aug-2004 17:16 6.0.3790.205 287,232 Wshlwapi.dll x86 RTMGDR\WOW
20-Aug-2004 17:49 5.2.3790.205 110,592 Grpconv.exe IA-64 RTMQFE
23-Aug-2004 17:10 6.0.3790.205 12,960,768 Shell32.dll IA-64 RTMQFE
23-Aug-2004 17:10 6.0.3790.205 738,816 Shlwapi.dll IA-64 RTMQFE
20-Aug-2004 17:42 5.2.3790.205 37,376 Wgrpconv.exe x86 RTMQFE\WOW
23-Aug-2004 17:10 6.0.3790.205 8,171,008 Wshell32.dll x86 RTMQFE\WOW
23-Aug-2004 17:10 6.0.3790.205 287,232 Wshlwapi.dll x86 RTMQFE\WOW
Notes The Windows XP and Windows XP 64-Bit Edition Version 2003 versions of this security update are packaged as dual-mode packages, which contain files for both the original version of Windows XP and Windows XP Service Pack 1 (SP1). For more information about dual-mode packages, see Microsoft Knowledge Base Article 328848.
When you install the Windows XP 64-Bit Edition Version 2003 security update, the installer checks to see if any of the files that are being updated on your system have previously been updated by a Microsoft hotfix. If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE files to your system. Otherwise, the installer copies the RTMGDR files to your system. For more information, see Microsoft Knowledge Base Article 824994.
Verifying Update Installation
- Microsoft Baseline Security Analyzer
To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. This tool 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 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 the update installation. 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, Windows XP Professional, Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP 64-Bit Edition Service Pack 1, Windows XP Tablet PC Edition, and Windows XP Media Center Edition:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP2\KB841356\Filelist
For Windows XP 64-Bit Edition Version 2003:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB841356\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 841356 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).
The software that is listed has been tested to determine if the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support lifecycle 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 Windows 2000 Service Pack 5.
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 is complete
/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
/extract Extracts files without starting setup
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the previous version of the setup utility uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
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-kb841356-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-kb841356-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%\$NTUninstallKB841356$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:
/?: Show the list of installation switches.
/u: Use unattended mode.
/f: Force other programs to quit when the computer shuts down.
/z: Do not restart when the installation is complete.
/q: Use Quiet mode (no user interaction).
File Information
The English version of this update has the file attributes (or later) 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.
Note Date, time, file name, or size information could change during installation. See the Verifying Update Installation section for details about how to verify an installation.
Windows 2000 Service Pack 3 and Windows 2000 Service Pack 4:
Date Time Version Size File name Folder
-----------------------------------------------------------------------------------------------
10-Aug-2004 05:21 5.0.2195.6966 41,744 Grpconv.exe
02-Sep-2004 20:03 5.0.2195.6958 17,168 Linkinfo.dll
02-Sep-2004 20:03 5.0.2195.6824 35,088 Ntlanman.dll
18-Sep-2004 08:24 5.0.3900.6975 2,358,544 Shell32.dll
20-Aug-2004 22:49 5.0.3900.6969 282,384 Shlwapi.dll
26-Aug-2004 15:28 5.0.2195.6970 5,893,632 Sp3res.dll
18-Sep-2004 08:24 5.0.3900.6975 1,118,992 Webvw.dll
20-Aug-2004 22:39 6.0.2750.167 393,728 Shlwapi.dll Xpclnt_qfe_binarydrop
20-Aug-2004 22:39 6.0.2800.1584 422,912 Shlwapi.dll Xpsp2_binarydrop
Verifying Update Installation
- Microsoft Baseline Security Analyzer
To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. This tool 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 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 the update installation. 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\KB841356\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 841356 security update into the Windows installation source files.
Windows NT 4.0 (all versions)
Prerequisites
This security update requires Windows NT Windows NT Server 4.0 Service Pack 6a (SP6a), or Windows NT Server 4.0 Terminal Server Edition Service Pack 6 (SP6).
The software that is listed has been tested to determine if the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support lifecycle for your product and version, visit the following Microsoft Support Lifecycle Web site.
For more information about obtaining the latest service pack, see Microsoft Knowledge Base Article 152734.
Installation Information
The security update supports the following setup switches:
/Q Specifies quiet mode, or suppresses prompts, when files are being extracted.
/Q:U Specifies user-quiet mode, which presents some dialog boxes to the user.
/Q:A Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
/T: <full path> Specifies the target folder for extracting files.
/C Extracts the files without installing them. If /T: path is not specified, you are prompted for a target folder.
/C: <Cmd> Override Install Command defined by author. Specifies the path and name of the setup .inf or .exe file.
/R:N Never restarts the computer after installation.
/R:I Prompts the user to restart the computer if a restart is required, except when used with /Q:A.
/R:A Always restarts the computer after installation.
/R:S Restarts the computer after installation without prompting the user.
/N:V No version checking - Install the program over any previous version.
Note These switches do not necessarily work with all updates. If a switch is not available that functionality is necessary for the correct installation of the update. Also, using the /N:V switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should consult your support professional to understand why it failed to install.
For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147.
Deployment Information
To install the update without any user intervention and not force the system to restart, use the following command at a command prompt:
Windowsnt4server-kb841356-x86-enu /q:a /r:n
For Windows NT Server 4.0 Terminal Server Edition:
Windowsnt4terminalserver-kb841356-x86-enu /q:a /r:n
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 update, use the Add or Remove Programs tool (or the Add/Remove Programs tool) in Control Panel. Click Windows NT 4.0 Server Hotfix-KB841356, and then click Change/Remove (or click Add/Remove).
System administrators can use the Ieuninst.exe utility to remove this update. This security update installs the Ieuninst.exe utility in the %Windir% folder. This utility supports the following setup switches:
/?: Show the list of supported switches
/z: Do not restart when the installation is complete
/q: Use Quiet mode (no user interaction)
To remove this update quietly, use the following command:
c:\windows\ieuninst /q c:\windows\inf\KB841356.inf
Note This command assumes that Windows is installed in the C:\Windows folder.
File Information
The English version of this update has the file attributes (or later) 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.
Note Date, time, file name, or size information could change during installation. See the Verifying Update Installation section for details about how to verify an installation.
Windows NT Server 4.0:
Date Time Version Size File name Folder
---------------------------------------------------------------------------
31-Jul-2004 19:41 4.72.3843.3100 1,770,720 Adshell32.dll
08-Jun-2004 14:19 4.0.1381.7157 39,696 Ntlanman.dll
17-Jul-2004 00:55 5.0.2195.6960 41,744 Nwgrpconv.exe
16-Jul-2004 16:25 4.0.1381.7286 47,376 Osgrpconv.exe
17-May-2004 15:36 4.0.1381.7267 1,281,808 Osshell32.dll
20-Aug-2004 22:01 6.0.2800.1584 422,912 Shlwapi.dll
31-Jul-2004 19:41 4.72.3843.3100 1,770,720 Shell32.dll Adshell32
17-Jul-2004 00:55 5.0.2195.6960 41,744 Grpconv.exe Nwgrpcnv
16-Jul-2004 16:25 4.0.1381.7286 47,376 Grpconv.exe Osgrpcnv
17-May-2004 15:36 4.0.1381.7267 1,281,808 Shell32.dll Osshell32
Windows NT Server 4.0 Terminal Server Edition:
Date Time Version Size File name Folder
-------------------------------------------------------------------------
10-May-2004 17:48 4.0.1381.33537 39,696 Ntlanman.dll
17-Jul-2004 00:55 5.0.2195.6960 41,744 Nwgrpconv.exe
16-Jul-2004 16:53 4.0.1381.33577 47,376 Osgrpconv.exe
04-May-2004 15:22 4.0.1381.33564 1,301,264 Osshell32.dll
20-Aug-2004 22:01 6.0.2800.1584 422,912 Shlwapi.dll
17-Jul-2004 00:55 5.0.2195.6960 41,744 Grpconv.exe Nwgrpcnv
16-Jul-2004 16:53 4.0.1381.33577 47,376 Grpconv.exe Osgrpcnv
04-May-2004 15:22 4.0.1381.33564 1,301,264 Shell32.dll Osshell32
Verifying Update Installation
- 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 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 the update installation. 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\Active Setup\Installed Components\{dccb3000-9408-4772-b113-b600e1311cef}
Note Confirm that the IsInstalled DWORD value with a data value of 1 appears in the registry key.
- Program Version Verification
Confirm that KB841356 is listed in the Update Versions field in the About Internet Explorer dialog box.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Yorick Koster of ITsec Security Services for working with us responsibly on the Shell Vulnerability (CAN-2004-0214).
- Roozbeh Afrasiabi for working with us responsibly on the Shell Vulnerability (CAN-2004-0214).
Obtaining Other Security Updates:
Updates for other security issues are available from the following locations:
- Security updates are available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch."
- Updates for consumer platforms are available from 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 with 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 to 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, see 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 (October 12, 2004): Bulletin published
- V1.1 (October 25, 2004): Bulletin updated to reduce the scope of a documented workaround to only support Windows XP, Windows XP Service Pack 1, and Windows Server 2003.
- V1.2 (February 15, 2005): Bulletin “Caveats” section updated to reflect the availability of Microsoft Knowledge Base Article 891534 as a known issue with this security update on Windows NT Server 4.0 Terminal Server Edition Service Pack 6. This bulletin has also been updated to document that this security update does not replace MS04-024 as was originally described in the bulletin.