INFORMATION BULLETIN
INFORMATION BULLETIN
| PROBLEM: | A remote code execution vulnerability exists in Windows Explorer because of the way that Windows Explorer handles Drag and Drop events. An attacker could exploit the vulnerability by constructing a malicious Web page that 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. |
| PLATFORM: | Microsoft Windows 2000 Service Pack 4
Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 Microsoft Windows XP Professional x64 Edition Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems Microsoft Windows Server 2003 x64 Edition |
| DAMAGE: | An attacker who successfully exploited this vulnerability could take complete control of an affected system. |
| SOLUTION: | Apply current patches. |
| VULNERABILITY ASSESSMENT: |
The risk is HIGH. An attacker who successfully exploited this vulnerability could take complete control of an affected system. |
| LINKS: | |
| CIAC BULLETIN: | http://www.ciac.org/ciac/bulletins/q-276.shtml |
| ORIGINAL BULLETIN: | http://www.microsoft.com/technet/security/Bulletin/MS06-045.mspx |
| CVE: | CVE-2006-3281 |
[***** Start Microsoft Security Bulletin MS06-045 (921398) *****]
Version: 1.0
sID='l1-EQC'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: This bulletin replaces a prior security update. See the frequently asked questions (FAQ) section of this bulletin for the complete list.
Caveats: None
Tested Software and Security Update Download Locations:
Affected Software:
| • | 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 Professional x64 Edition – Download the update |
| • | Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 - Download the update |
| • | Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems - Download the update |
| • | Microsoft Windows Server 2003 x64 Edition – Download the update |
The software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.
Note The security updates for Microsoft Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 x64 Edition also apply to Windows Server 2003 R2.
sID='3l1-ECF';writePM(sID) |
startA('s'+sID)
Executive SummaryendA() |
Executive Summary:
This update resolves a newly-discovered, publicly-reported vulnerability. The vulnerability is documented in the "Vulnerability Details" section of this bulletin.
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.
If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
We recommend that customers apply the update immediately.
Severity Ratings and Vulnerability Identifiers:
| Vulnerability Identifiers | Impact of Vulnerability | Windows 2000 | Windows XP Service Pack 1 | Windows XP Service Pack 2 | Windows Server 2003 | Windows Server 2003 Service Pack 1 |
Folder GUID Code Execution Vulnerability - CVE-2006-3281 |
Remote code execution |
Important |
Important |
Important |
Important |
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.
Note The security updates for Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 x64 Edition also apply to Windows Server 2003 R2.
Note The severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows:
| • | The Microsoft Windows XP Professional x64 Edition severity rating is the same as the Windows XP Service Pack 2 severity rating. |
| • | The Microsoft Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating. |
| • | The Microsoft Windows Server 2003 with SP1 for Itanium-based Systems severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating. |
| • | The Microsoft Windows Server 2003 x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating. |
|
startA('s'+sID)
Vulnerability DetailsendA() |
| sID='3l2-E3HAC';writePM(sID) |
startA('s'+sID)
Folder GUID Code Execution Vulnerability - CVE-2006-3281:endA() |
A remote code execution vulnerability exists in Windows Explorer because of the way that Windows Explorer handles Drag and Drop events. An attacker could exploit the vulnerability by constructing a malicious Web page that 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. User interaction is required to exploit this vulnerability
| sID='3l3-EAIAC';writePM(sID) |
startA('s'+sID)
Mitigating Factors for Folder GUID Code Execution Vulnerability - CVE-2006-3281:endA() |
| • | Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems that are connected to the Internet have a minimal number of ports exposed. |
| • | 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. After they click the link, they would be prompted to perform several actions. An attack could only occur after they performed these actions. |
| • | An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. |
| • | The Restricted sites zone helps reduce attacks that could try to exploit this vulnerability by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail. However, if a user clicks on a link within an e-mail they could still be vulnerable to this issue through the Web-based attack scenario described previously. |
| • | The vulnerability could not be exploited automatically through e-mail. For an attack to be successful a user must open an attachment or click on a link that is sent in an e-mail message. |
|
startA('s'+sID)
Security Update InformationendA() |
Affected Software:
For information about the specific security update for your affected software, click the appropriate link:
sID='3l2-EVPAC';writePM(sID) |
startA('s'+sID)
Windows Server 2003 (all versions)endA() |
Prerequisites
This security update requires Windows Server 2003 or Windows Server 2003 Service Pack 1.
Inclusion in Future Service Packs:
The update for this issue will be included in future Service Pack or Update Rollup.
Installation Information
This security update supports the following setup switches.
Note The security updates for Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 also apply to Microsoft Windows Server 2003 R2.
Inclusion in Future Service Packs:
The update for this issue will be included in future Service Pack or Update Rollup.
Installation Information
This security update supports the following setup switches
| Supported Security Update Installation Switches | |
| Switch | Description |
/help |
Displays the command-line options |
| Setup Modes | |
/passive |
Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
/quiet |
Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
/norestart |
Does not restart when installation has completed |
/forcerestart |
Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
/warnrestart[:x] |
Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
/promptrestart |
Display a dialog box prompting the local user to allow a restart |
| Special Options | |
/overwriteoem |
Overwrites OEM files without prompting |
/nobackup |
Does not back up files needed for uninstall |
/forceappsclose |
Forces other programs to close when the computer shuts down |
/log: path |
Allows the redirection of installation log files |
/integrate:path |
Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. |
/extract[:path] |
Extracts files without starting the Setup program |
/ER |
Enables extended error reporting |
/verbose |
Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.
Deployment Information
To install the security update without any user intervention, use the following command at a command prompt for Windows Server 2003:
Windowsserver2003-kb921398-x86-enu /quiet
Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB921398.log file for any failure messages when they use this switch.
To install the security update without forcing the system to restart, use the following command at a command prompt for Windows Server 2003:
Windowsserver2003-kb921398-x86-enu /norestart
For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.
Restart Requirement
You must restart your system after you apply this security update.
This security update does not support HotPatching. For more information about HotPatching and how to deploy this security update as a HotPatch see Microsoft Knowledge Base Article 897341.
Note Not all security updates support HotPatching, and some security updates that support HotPatching might require that you restart the server after you install the security update. HotPatching is only supported if the files being replaced by the security update are General Distribution Release (GDR) files. HotPatching is not supported if you have previously installed a hotfix to update one of the files included in the security update. For more information about this behavior, see Microsoft Knowledge Base Article 897341 and Microsoft Knowledge Base Article 824994.
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%\$NTUninstallKB921398$\Spuninst folder.
| Supported Spuninst.exe Switches | |
| Switch | Description |
/help |
Displays the command-line options |
| Setup Modes | |
/passive |
Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
/quiet |
Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
/norestart |
Does not restart when installation has completed |
/forcerestart |
Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
/warnrestart[:x] |
Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
/promptrestart |
Display a dialog box prompting the local user to allow a restart |
| Special Options | |
/forceappsclose |
Forces other programs to close when the computer shuts down |
/log:path |
Allows the redirection of installation log files |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Datacenter Edition; Windows Server 2003, Enterprise Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; Windows Server 2003, Datacenter Edition with SP1; Windows Server 2003 R2, Web Edition; Windows Server 2003 R2, Standard Edition; Windows Server 2003 R2, Datacenter Edition; Windows Server 2003 R2, Enterprise Edition; Windows Small Business Server 2003 R2:
| File Name | Version | Date | Time | Size | CPU | Folder |
Shell32.dll |
6.0.3790.559 |
13-Jul-2006 |
12:42 |
8,173,056 |
|
RTMGDR |
Shell32.dll |
6.0.3790.559 |
13-Jul-2006 |
12:59 |
8,174,080 |
x86 |
RTMQFE |
Shell32.dll |
6.0.3790.2746 |
13-Jul-2006 |
12:55 |
8,382,976 |
x86 |
SP1GDR |
Shell32.dll |
6.0.3790.2746 |
13-Jul-2006 |
13:06 |
8,384,512 |
x86 |
SP1QFE |
W03a2409.dll |
5.2.3790.2746 |
13-Jul-2006 |
09:48 |
26,624 |
x86 |
SP1QFE |
Windows Server, 2003 Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; and Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems:
| File Name | Version | Date | Time | Size | CPU | Folder |
Shell32.dll |
6.0.3790.559 |
13-Jul-2006 |
13:54 |
12,969,984 |
IA-64 |
RTMGDR |
Wshell32.dll |
6.0.3790.559 |
13-Jul-2006 |
13:54 |
8,173,056 |
|
RTMGDR\WOW |
Shell32.dll |
6.0.3790.559 |
13-Jul-2006 |
13:55 |
12,973,056 |
IA-64 |
RTMQFE |
Wshell32.dll |
6.0.3790.559 |
13-Jul-2006 |
13:55 |
8,174,080 |
x86 |
RTMQFE\WOW |
Shell32.dll |
6.0.3790.2746 |
13-Jul-2006 |
14:08 |
13,254,656 |
IA-64 |
SP1GDR |
Wshell32.dll |
6.0.3790.2746 |
13-Jul-2006 |
14:08 |
8,382,976 |
x86 |
SP1GDR\WOW |
Shell32.dll |
6.0.3790.2746 |
13-Jul-2006 |
13:55 |
13,258,240 |
IA-64 |
SP1QFE |
W03a2409.dll |
5.2.3790.2746 |
13-Jul-2006 |
13:55 |
25,600 |
IA-64 |
SP1QFE |
Wshell32.dll |
6.0.3790.2746 |
13-Jul-2006 |
13:55 |
8,384,512 |
x86 |
SP1QFE\WOW |
Ww03a2409.dll |
5.2.3790.2746 |
13-Jul-2006 |
13:55 |
26,624 |
x86 |
SP1QFE\WOW |
Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition; Windows Server 2003 R2, Standard x64 Edition; Windows Server 2003 R2, Enterprise x64 Edition; and Windows Server 2003 R2, Datacenter x64 Edition:
| File Name | Version | Date | Time | Size | CPU | Folder |
Shell32.dll |
6.0.3790.2746 |
13-Jul-2006 |
14:07 |
10,499,584 |
x64 |
SP1GDR |
Wshell32.dll |
6.0.3790.2746 |
13-Jul-2006 |
14:07 |
8,382,976 |
x86 |
SP1GDR\WOW |
Shell32.dll |
6.0.3790.2746 |
13-Jul-2006 |
13:55 |
10,502,144 |
x64 |
SP1QFE |
W03a2409.dll |
5.2.3790.2746 |
13-Jul-2006 |
13:55 |
27,136 |
x64 |
SP1QFE |
Wshell32.dll |
6.0.3790.2746 |
13-Jul-2006 |
13:55 |
8,384,512 |
x86 |
SP1QFE\WOW |
Ww03a2409.dll |
5.2.3790.2746 |
13-Jul-2006 |
13:55 |
26,624 |
x86 |
SP1QFE\WOW |
Notes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the Update.exe installer, visit the Microsoft TechNet Web site.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
Verifying that the Update Has Been Applied
| • | Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site. |
||||||||||
| • | File Version Verification Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
|
| • | Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the following registry key. Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Datacenter Edition; Windows Server 2003, Enterprise Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; Windows Server 2003, Datacenter Edition with SP1; Windows Server 2003 R2, Web Edition; Windows Server 2003 R2, Standard Edition; Windows Server 2003 R2, Datacenter Edition; Windows Server 2003 R2, Enterprise Edition; Windows Small Business Server 2003 R2; Windows Server 2003, Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems; Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition; Windows Server 2003 R2, Standard x64 Edition; Windows Server 2003 R2, Enterprise x64 Edition; and Windows Server 2003 R2, Datacenter x64 Edition: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP2\KB921398\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 921398 security update into the Windows installation source files. |
| sID='3l2-EXZAE';writePM(sID) |
startA('s'+sID)
Windows XP (all versions)endA() |
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.
| Supported Security Update Installation Switches | |
| Switch | Description |
/help |
Displays the command-line options |
| Setup Modes | |
/passive |
Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
/quiet |
Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
/norestart |
Does not restart when installation has completed |
/forcerestart |
Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
/warnrestart[:x] |
Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
/promptrestart |
Display a dialog box prompting the local user to allow a restart |
| Special Options | |
/overwriteoem |
Overwrites OEM files without prompting |
/nobackup |
Does not back up files needed for uninstall |
/forceappsclose |
Forces other programs to close when the computer shuts down |
/log:path |
Allows the redirection of installation log files |
/integrate:path |
Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. |
/extract[:path] |
Extracts files without starting the Setup program |
/ER |
Enables extended error reporting |
/verbose |
Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.
Deployment Information
To install the security update without any user intervention, use the following command at a command prompt for Microsoft Windows XP:
Windowsxp-kb921398-x86-enu /quiet
Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB921398.log file for any failure messages when they use this switch.
To install the security update without forcing the system to restart, use the following command at a command prompt for Windows XP:
Windowsxp-kb921398-x86-enu /norestart
For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.
Restart Requirement
You must restart your system after you apply this security update.
Removal Information
To remove this security update, use the Add or Remove Programs tool in Control Panel.
System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB921398$\Spuninst folder.
| Supported Spuninst.exe Switches | |
| Switch | Description |
/help |
Displays the command-line options |
| Setup Modes | |
/passive |
Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
/quiet |
Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
/norestart |
Does not restart when installation has completed |
/forcerestart |
Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
/warnrestart[:x] |
Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
/promptrestart |
Display a dialog box prompting the local user to allow a restart |
| Special Options | |
/forceappsclose |
Forces other programs to close when the computer shuts down |
/log:path |
Allows the redirection of installation log files |
File Information
The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows 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 | CPU | Folder |
Fldrclnr.dll |
6.0.2800.1579 |
20-Aug-2004 |
22:01 |
82,432 |
x86 |
SP1QFE |
Shell32.dll |
6.0.2800.1873 |
13-Jul-2006 |
13:46 |
8,353,280 |
x86 |
SP1QFE |
Sxs.dll |
5.1.2600.1579 |
20-Aug-2004 |
22:01 |
700,928 |
x86 |
SP1QFE |
Comctl32.dll |
6.0.2800.1873 |
13-Jul-2006 |
13:46 |
925,184 |
x86 |
SP1QFE\ASMS\60\MSFT\WINDOWS\COMMON\CONTROLS |
Controls.man |
|
13-Jul-2006 |
14:02 |
1,812 |
|
SP1QFE\ASMS\60\MSFT\WINDOWS\COMMON\CONTROLS |
Comctl.man |
|
13-Jul-2006 |
14:02 |
621 |
|
SP1QFE\ASMS\60\POLICY\60\COMCTL |
Shell32.dll |
6.0.2900.2951 |
13-Jul-2006 |
13:33 |
8,453,632 |
x86 |
SP2GDR |
Shell32.dll |
6.0.2900.2951 |
13-Jul-2006 |
14:03 |
8,457,728 |
x86 |
SP2QFE |
Xpsp3res.dll |
5.1.2600.2951 |
13-Jul-2006 |
11:22 |
150,016 |
x86 |
SP2QFE |
Windows XP Professional x64:
| File Name | Version | Date | Time | Size | CPU | Folder |
Shell32.dll |
6.0.3790.2746 |
13-Jul-2006 |
14:07 |
10,499,584 |
x64 |
SP1GDR |
Wshell32.dll |
6.0.3790.2746 |
13-Jul-2006 |
14:07 |
8,382,976 |
x86 |
SP1GDR\WOW |
Shell32.dll |
6.0.3790.2746 |
13-Jul-2006 |
13:55 |
10,502,144 |
x64 |
SP1QFE |
W03a2409.dll |
5.2.3790.2746 |
13-Jul-2006 |
13:55 |
27,136 |
x64 |
SP1QFE |
Wshell32.dll |
6.0.3790.2746 |
13-Jul-2006 |
13:55 |
8,384,512 |
x86 |
SP1QFE\WOW |
Ww03a2409.dll |
5.2.3790.2746 |
13-Jul-2006 |
13:55 |
26,624 |
x86 |
SP1QFE\WOW |
Notes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the Update.exe installer, visit the Microsoft TechNet Web site.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
Verifying that the Update Has Been Applied
| • | Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site. |
||||||||||
| • | File Version Verification Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
|
| • | 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\KB921398\Filelist For Windows XP Professional x64 Edition: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP2\KB921398\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 921398 security update into the Windows installation source files. |
| sID='3l2-EUPAG';writePM(sID) |
startA('s'+sID)
Windows 2000 (all versions) |
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. |
| • | |
| • | |
| • | |
| • | |
| • | |
| • | Windows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166. |
| • |
Software Update Services:
By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.
For more information about how to deploy security updates by using Software Update Services, visit the Software Update Services Web site.
Windows Server Update Services:
By using Windows Server Update Services (WSUS), administrators can quickly and reliably deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 onto Windows 2000 and later operating systems.
For more information about how to deploy security updates using Windows Server Update Services, visit the Windows Server Update Services Web site.
Systems Management Server:
Microsoft Systems Management Server (SMS) delivers a highly-configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and can perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, visit the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site.
Note SMS uses the Microsoft Baseline Security Analyzer, the Microsoft Office Detection Tool, and the Enterprise Update Scanning Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.
Disclaimer:
The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Revisions:
| • | V1.0 (August 8, 2006): Bulletin published |
[***** End Microsoft Security Bulletin MS06-045 (921398) *****]
Voice: +1 925-422-8193 (7 x 24)
FAX: +1 925-423-8002
STU-III: +1 925-423-2604
E-mail: ciac@ciac.org
World Wide Web: http://www.ciac.org/
Anonymous FTP: ftp.ciac.org