SecurityvulnsSECURITYVULNS:DOC:9918Microsoft Security Bulletin MS05-049 Vulnerabilities in Windows Shell Could Allow Remote Code Execution (900725)
Microsoft Security Bulletin MS05-049
Vulnerabilities in Windows Shell Could Allow Remote Code Execution (900725)
Published: October 11, 2005
Version: 1.0
Summary
Who should read this document: Customers who use Microsoft Windows
Impact of Vulnerability: Remote Code Execution
Maximum Severity Rating: Important
Recommendation: Customers should apply the update at the earliest opportunity.
Security Update Replacement: This bulletin replaces several prior security updates. 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
Non-Affected Software:
•
Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME)
The software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.
Top of sectionTop of section
General Information
Executive Summary
Executive Summary:
This update resolves several newly-discovered, privately reported vulnerabilities. Each vulnerability is documented in this bulletin in its own "Vulnerability Details" section.
If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. However, user interaction is required to exploit this vulnerability.
We recommend that customers apply the update at the earliest opportunity.
Severity Ratings and Vulnerability Identifiers:
Vulnerability Identifiers Impact of Vulnerability Windows 2000 Windows XP Service Pack 1 Windows XP Service Pack 2 Windows Server 2003 Windows Server 2003 Service Pack 1
Shell Vulnerability - CAN-2005-2122
Remote Code Execution
Important
Important
Important
Important
Important
Shell Vulnerability - CAN-2005-2118
Remote Code Execution
Important
Important
None
None
None
Web View Script Injection Vulnerability - CAN-2005-2117
Remote Code Execution
Moderate
None
None
None
None
Aggregate Severity of All Vulnerabilities
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 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.
Top of sectionTop of section
Frequently asked questions (FAQ) related to this security update
Why does this update address several reported security vulnerabilities?
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers can install only this update.
What updates does this release replace?
This security update replaces several prior security bulletins. The security bulletin IDs and operating systems that are affected are listed in the following table.
Bulletin ID Windows 2000 Windows XP (All versions) Windows Server 2003 Windows Server 2003 Service Pack 1
MS05-016
Replaced
Replaced
Replaced
Not Applicable
MS05-024
Replaced
Not Applicable
Not Applicable
Not Applicable
Extended security update support for Microsoft Windows NT Workstation 4.0 Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. Extended security update support for Microsoft Windows NT Server 4.0 Service Pack 6a ended on December 31, 2004. Extended security update support for Microsoft Windows 2000 Service Pack 3 ended on June 30, 2005. I am still using one of these operating systems, what should I do?
Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, Windows 2000 Service Pack 2, and Windows 2000 Service Pack 3 have reached the end of their life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.
Customers who require additional custom support for these products must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager.
For more information, see the Windows Operating System Product Support Lifecycle FAQ.
Security update support for Microsoft Windows XP 64-Bit Edition Service Pack 1 (Itanium) and Microsoft Windows XP 64-Bit Edition Version 2003 (Itanium) ended on June 30, 2005. I’m still using one of these operating systems, what should I do?
With the release of Windows XP Professional x64 Edition, Microsoft Windows XP 64-Bit Edition Service Pack 1 (Itanium) and Microsoft Windows XP 64-Bit Edition Version 2003 (Itanium) will no longer receive security update support. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. Microsoft will continue to fully support Windows Server 2003 for Itanium-based systems, Windows XP Professional x64 Edition, and Windows Server 2003 x64 Editions for 64-bit computing requirements. Microsoft continues to license and support Windows Server 2003 Enterprise and Datacenter editions for Itanium-based systems, and the 64-bit version of SQL Server 2000 Enterprise Edition. In the future, we will expand Itanium support to Visual Studio 2005, .NET Framework 2005, and SQL Server 2005.
Customers who require additional assistance about this issue must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for information about the available migration options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager.
Can I use the Microsoft Baseline Security Analyzer (MBSA) 1.2.1 to determine whether this update is required?
Yes. MBSA 1.2.1 will determine whether this update is required. For more information about MBSA, visit the MBSA Web site.
Can I use the Microsoft Baseline Security Analyzer (MBSA) 2.0 to determine whether this update is required?
Yes. MBSA 2.0 will determine whether this update is required. MBSA 2.0 can detect security updates for products that Microsoft Update supports. For more information about MBSA, visit the MBSA Web site.
Can I use Systems Management Server (SMS) to determine whether this update is required?
Yes. SMS can help detect and deploy this security update. For information about SMS, visit the SMS Web site. The Security Update Inventory Tool can be used by SMS for detecting security updates that are offered by Windows Update, that are supported by Software Update Services, and other security updates that are supported by MBSA 1.2.1. For more information about the Security Update Inventory Tool, visit the following Microsoft Web site. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460. The SMS 2003 Inventory Tool for Microsoft Updates can be used by SMS for detecting security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 Inventory Tool for Microsoft Updates, visit the following Microsoft Web site.
Top of sectionTop of section
Vulnerability Details
Shell Vulnerability- CAN-2005-2122:
A remote code execution vulnerability exists in Windows because of the way that it handles the .lnk file name extension. By persuading a user to open an .lnk file that has specially-crafted properties an attacker could execute code on an affected system.
Mitigating Factors for Shell Vulnerability- CAN-2005-2122:
•
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 an action. An attack could only occur after they performed this actions.
•
The vulnerability could not be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message.
•
To exploit this vulnerability locally the attacker must have valid logon credentials and be able to log on. The vulnerability could not be exploited remotely or by anonymous users.
Top of sectionTop of section
Workarounds for Shell Vulnerability- CAN-2005-2122:
Do not open files that have .lnk extensions and that come from unknown or untrusted sources.
Top of sectionTop of section
FAQ for Shell Vulnerability- CAN-2005-2122:
What is the scope of the vulnerability?
A remote code execution vulnerability exists in Windows because of the way that it handles files with the .lnk file name extension. An attacker could exploit the vulnerability by persuading a user to open an .lnk file that has specially-crafted properties. An attacker who successfully exploited this vulnerability could execute code on the affected system. However, user interaction is required to exploit this vulnerability.
What causes the vulnerability?
The way that Windows handles certain properties that are associated with .lnk files.
What are .lnk files?
An .lnk file is a file that is used to point to another file, such as a program. These files are often known as shortcut files and can contain properties that are passed to the target program.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.
Who could exploit the vulnerability?
Any anonymous user who could deliver a specially-crafted .lnk file to a user, and then persuade that user to open the .lnk file, could try to exploit this vulnerability.
How could an attacker exploit the vulnerability?
To exploit this vulnerability locally, an attacker must be able to log on to the specific system that is targeted for attack or persuade a user to open a specially-crafted .lnk file.
What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who have administrative permissions log on to servers and open specially-crafted .lnk files.
Could the vulnerability be exploited over the Internet?
No. An attacker must be able to log on to the specific system that is targeted for attack or persuade a user to open a specially-crafted .lnk file.
What does the update do?
The update removes the vulnerability by modifying the way that Windows processes files that use the .lnk file name extension.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
Top of sectionTop of section
Top of sectionTop of section
Shell Vulnerability - CAN-2005-2118:
A remote code execution vulnerability exists in Windows because of the way that it handles files with the .lnk file name extension. By persuading a user to view the properties of a specially-crafted .lnk file, an attacker could execute code on the affected system.
Mitigating Factors for Shell Vulnerability - CAN-2005-2118:
•
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 an action. An attack could only occur after they performed this action.
•
The vulnerability could not be exploited automatically through e-mail. For an attack to be successful, a user must open an attachment that is sent in an e-mail message.
•
To exploit this vulnerability locally, the attacker must have valid logon credentials and be able to log on. The vulnerability could not be exploited remotely or by anonymous users.
Top of sectionTop of section
Workarounds for Shell Vulnerability - CAN-2005-2118:
Do not view the properties of files that have .lnk file name extensions and that come from unknown or untrusted sources.
Top of sectionTop of section
FAQ for Shell Vulnerability - CAN-2005-2118:
What is the scope of the vulnerability?
A remote code execution vulnerability exists in Windows because of the way that it handles files with the .lnk file name extension. An attacker could exploit the vulnerability by persuading a user to view the properties of an .lnk file that contains specially-crafted properties. An attacker who successfully exploited this vulnerability could execute code on the affected system. However, user interaction is required to exploit this vulnerability.
What causes the vulnerability?
This vulnerability is attributed to the way Windows handles certain properties that are associated with .lnk files.
What are .lnk files?
An .lnk file is a file that is used to point to another file, such as a program. These files are often known as shortcut files and can contain properties that are passed to the target program.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.
Who could exploit the vulnerability?
Any anonymous user who could deliver a specially-crafted .lnk file to a user, and then persuade that user to open the .lnk file, could try to exploit this vulnerability.
How could an attacker exploit the vulnerability?
To locally this vulnerability locally, an attacker must be able to log on to the specific system that is targeted for attack or persuade a user to right click and view the properties of a specially-crafted .lnk file.
What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who do not have sufficient administrative permissions are given the ability to log on to servers and open specially-crafted .lnk files. However, best practices strongly discourage allowing this.
Could the vulnerability be exploited over the Internet?
No. An attacker must be able to log on to the specific system that is targeted for attack or persuade a user to open on a specially-crafted .lnk file.
What does the update do?
The update removes the vulnerability by modifying the way that Windows handles malformed .lnk file properties before passing them to allocated buffers.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
Top of sectionTop of section
Top of sectionTop of section
Web View Script Injection Vulnerability - CAN-2005-2117:
A remote code execution vulnerability exists in the way that Web View in Windows Explorer handles certain HTML characters in preview fields. By persuading a user to preview a malicious file, an attacker could execute code. However, user interaction is required to exploit this vulnerability.
Mitigating Factors for Web View Script Injection Vulnerability - CAN-2005-2117:
•
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 an action. 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 vulnerability could not be exploited automatically through e-mail. For an attack to be successful through e-mail a user must save an attachment locally and then preview it in Windows Explorer.
Top of sectionTop of section
Workarounds for Web View Script Injection Vulnerability - CAN-2005-2117:
Microsoft has tested the following workarounds. While these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section.
•
Disable Web View:
Disabling Web View will reduce the ability to maliciously use this feature to perform an attack. To disable Web View, follow these steps:
Click Start, and then click My Computer.
Click Tools menu, and then click Folder Options.
On the General tab, under Tasks, click Use Windows classic folders, and then click OK.
These settings take affect only after you log off the system and then log back on again.
Impact of Workaround: This change will reduce the functionality of Windows Explorer by removing the left hand task pane which contains links to common folders and tasks.
•
Use the Group Policy settings to disable Web View on all affected systems that do not require this feature:
Disabling Web View will reduce the ability to maliciously use this feature to perform an attack.
For more information about Group Policy, visit the following Web sites:
•
Step-by-Step Guide to Understanding the Group Policy Feature Set
•
Windows 2000 Group Policy
Impact of Workaround: This change will reduce the functionality of Windows Explorer by removing the task pane, which contains links to common folders and tasks.
•
Block TCP ports 139 and 445 at the perimeter firewall:
These ports are used to initiate a connection by using the Server Message Block (SMB) protocol. Blocking outbound SMB traffic at the perimeter firewall will help prevent systems from trying to connect to a malicious file server outside the firewall. For more information about the ports, visit the following Web site.
Impact of Workaround: Computers that are behind the firewall will be unable to access trusted file servers by using the Server Message Block (SMB) protocol outside the network.
Top of sectionTop of section
FAQ for Web View Script Injection Vulnerability - CAN-2005-2117:
What is the scope of the vulnerability?
This is a remote code execution vulnerability. By persuading a user to preview a malicious file, an attacker could execute code. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. However, user interaction is required to exploit this vulnerability.
What causes the vulnerability?
The process that Windows Explorer uses to validate HTML characters in certain document fields when in Web View.
What is Web View?
Web View is one of two formats that Windows Explorer provides to view file and folder information. This feature allows a user to preview a file or folder in a thumbnail view before they open it. Web View also displays information about that file or folder, such as the title and the author.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.
How could an attacker exploit the vulnerability?
An attacker could try to exploit the vulnerability by creating a malicious file and placing it in a local or remote location. The attacker would then have to persuade a user to connect to the folder in Windows Explorer and preview the document. The document could then cause the affected system to execute code.
What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who do not have sufficient administrative permissions are given the ability to log on to servers and to run programs.
What does the update do?
The update addresses the vulnerability by modifying the way that Windows Explorer validates HTML characters in certain file fields.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
Top of sectionTop of section
Top of sectionTop of section
Top of sectionTop of section
Security Update Information
Affected Software:
For information about the specific security update for your affected software, click the appropriate link:
Windows Server 2003 (all versions)
Prerequisites
This security update requires Windows Server 2003 or Windows Server 2003 Service Pack 1.
Inclusion in Future Service Packs:
The update for this issue will be included in a future Service Pack or Update Rollup.
Installation Information
This security update supports the following setup switches.
Supported Security Update Installation Switches
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-kb900725-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 KB900725.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-kb900725-x86-enu /norestart
For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.
Restart Requirement
You must restart your system after you apply this security update.
Removal Information
To remove this update, use the Add or Remove Programs tool in Control Panel.
System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB900725$\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; and Windows Server 2003, Datacenter Edition with SP1:
File Name Version Date Time Size Folder
Linkinfo.dll
5.2.3790.401
01-Sep-2005
02:10
17,408
RTMGDR
Shell32.dll
6.0.3790.413
23-Sep-2005
16:58
8,171,520
RTMGDR
Shlwapi.dll
6.0.3790.403
03-Sep-2005
01:36
287,744
RTMGDR
Winsrv.dll
5.2.3790.401
01-Sep-2005
02:10
292,352
RTMGDR
Linkinfo.dll
5.2.3790.401
01-Sep-2005
02:13
17,408
RTMQFE
Shell32.dll
6.0.3790.413
23-Sep-2005
16:39
8,172,544
RTMQFE
Shlwapi.dll
6.0.3790.403
03-Sep-2005
01:40
287,744
RTMQFE
Winsrv.dll
5.2.3790.401
01-Sep-2005
02:13
292,864
RTMQFE
Linkinfo.dll
5.2.3790.2521
01-Sep-2005
02:18
20,480
SP1GDR
Shell32.dll
6.0.3790.2534
23-Sep-2005
16:50
8,379,392
SP1GDR
Shlwapi.dll
6.0.3790.2523
03-Sep-2005
01:44
321,536
SP1GDR
Winsrv.dll
5.2.3790.2521
01-Sep-2005
02:18
296,960
SP1GDR
Linkinfo.dll
5.2.3790.2521
01-Sep-2005
02:15
20,480
SP1QFE
Shell32.dll
6.0.3790.2534
23-Sep-2005
16:54
8,379,904
SP1QFE
Shlwapi.dll
6.0.3790.2523
03-Sep-2005
01:46
321,536
SP1QFE
Winsrv.dll
5.2.3790.2521
01-Sep-2005
02:15
297,472
SP1QFE
Arpidfix.exe
5.2.3790.2535
27-Sep-2005
02:22
32,256
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
Linkinfo.dll
5.2.3790.401
28-Sep-2005
00:30
45,568
IA-64
RTMGDR
Shell32.dll
6.0.3790.413
28-Sep-2005
00:30
12,961,792
IA-64
RTMGDR
Shlwapi.dll
6.0.3790.403
28-Sep-2005
00:30
740,352
IA-64
RTMGDR
Winsrv.dll
5.2.3790.401
28-Sep-2005
00:30
765,952
IA-64
RTMGDR
Wlinkinfo.dll
5.2.3790.401
28-Sep-2005
00:30
17,408
x86
RTMGDR\WOW
Wshell32.dll
6.0.3790.413
28-Sep-2005
00:30
8,171,520
x86
RTMGDR\WOW
Wshlwapi.dll
6.0.3790.403
28-Sep-2005
00:30
287,744
x86
RTMGDR\WOW
Linkinfo.dll
5.2.3790.401
28-Sep-2005
00:32
45,568
IA-64
RTMQFE
Shell32.dll
6.0.3790.413
28-Sep-2005
00:32
12,964,864
IA-64
RTMQFE
Shlwapi.dll
6.0.3790.403
28-Sep-2005
00:32
740,352
IA-64
RTMQFE
Winsrv.dll
5.2.3790.401
28-Sep-2005
00:32
766,976
IA-64
RTMQFE
Wlinkinfo.dll
5.2.3790.401
28-Sep-2005
00:32
17,408
x86
RTMQFE\WOW
Wshell32.dll
6.0.3790.413
28-Sep-2005
00:32
8,172,544
x86
RTMQFE\WOW
Wshlwapi.dll
6.0.3790.403
28-Sep-2005
00:32
287,744
x86
RTMQFE\WOW
Linkinfo.dll
5.2.3790.2521
28-Sep-2005
00:28
49,664
IA-64
SP1GDR
Shell32.dll
6.0.3790.2534
28-Sep-2005
00:28
13,244,928
IA-64
SP1GDR
Shlwapi.dll
6.0.3790.2523
28-Sep-2005
00:28
824,320
IA-64
SP1GDR
Winsrv.dll
5.2.3790.2521
28-Sep-2005
00:28
815,104
IA-64
SP1GDR
Wlinkinfo.dll
5.2.3790.2521
28-Sep-2005
00:28
20,480
x86
SP1GDR\WOW
Wshell32.dll
6.0.3790.2534
28-Sep-2005
00:28
8,379,392
x86
SP1GDR\WOW
Wshlwapi.dll
6.0.3790.2523
28-Sep-2005
00:28
321,536
x86
SP1GDR\WOW
Linkinfo.dll
5.2.3790.2521
28-Sep-2005
00:33
49,664
IA-64
SP1QFE
Shell32.dll
6.0.3790.2534
28-Sep-2005
00:33
13,245,440
IA-64
SP1QFE
Shlwapi.dll
6.0.3790.2523
28-Sep-2005
00:33
824,320
IA-64
SP1QFE
Winsrv.dll
5.2.3790.2521
28-Sep-2005
00:33
814,592
IA-64
SP1QFE
Wlinkinfo.dll
5.2.3790.2521
28-Sep-2005
00:33
20,480
x86
SP1QFE\WOW
Wshell32.dll
6.0.3790.2534
28-Sep-2005
00:33
8,379,904
x86
SP1QFE\WOW
Wshlwapi.dll
6.0.3790.2523
28-Sep-2005
00:33
321,536
x86
SP1QFE\WOW
Arpidfix.exe
5.2.3790.2535
28-Sep-2005
00:34
74,752
IA-64
Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition:
File Name Version Date Time Size CPU Folder
Linkinfo.dll
5.2.3790.2521
28-Sep-2005
00:28
31,744
x64
SP1GDR
Shell32.dll
6.0.3790.2534
28-Sep-2005
00:28
10,491,392
x64
SP1GDR
Shlwapi.dll
6.0.3790.2523
28-Sep-2005
00:28
621,568
x64
SP1GDR
Winsrv.dll
5.2.3790.2521
28-Sep-2005
00:28
509,952
x64
SP1GDR
Wlinkinfo.dll
5.2.3790.2521
28-Sep-2005
00:28
20,480
x86
SP1GDR\WOW
Wshell32.dll
6.0.3790.2534
28-Sep-2005
00:28
8,379,392
x86
SP1GDR\WOW
Wshlwapi.dll
6.0.3790.2523
28-Sep-2005
00:28
321,536
x86
SP1GDR\WOW
Linkinfo.dll
5.2.3790.2521
28-Sep-2005
00:30
31,744
x64
SP1QFE
Shell32.dll
6.0.3790.2534
28-Sep-2005
00:30
10,491,904
x64
SP1QFE
Shlwapi.dll
6.0.3790.2523
28-Sep-2005
00:30
621,568
x64
SP1QFE
Winsrv.dll
5.2.3790.2521
28-Sep-2005
00:30
509,440
x64
SP1QFE
Wlinkinfo.dll
5.2.3790.2521
28-Sep-2005
00:30
20,480
x86
SP1QFE\WOW
Wshell32.dll
6.0.3790.2534
28-Sep-2005
00:30
8,379,904
x86
SP1QFE\WOW
Wshlwapi.dll
6.0.3790.2523
28-Sep-2005
00:30
321,536
x86
SP1QFE\WOW
Arpidfix.exe
5.2.3790.2535
28-Sep-2005
00:32
43,008
x64
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.
Arpidfix.exe is used by the security update installer to address an issue documented in Microsoft Knowledge Base Article 904630. This file is not installed onto the affected system.
Verifying that the Update Has Been Applied
•
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
•
File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
Click Start, and then click Search.
In the Search Results pane, click All files and folders under Search Companion.
In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
•
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the following registry key.
Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003; Windows Server 2003, 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, 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:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP2\KB900725\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 900725 security update into the Windows installation source files.
Top of sectionTop of section
Windows XP (all versions)
Prerequisites
This security update requires Microsoft Windows XP Service Pack 1 or a later version. For more information, see Microsoft Knowledge Base Article 322389.
Inclusion in Future Service Packs:
The update for this issue will be included in a future Service Pack or Update Rollup.
Installation Information
This security update supports the following setup switches.
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-kb900725-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 KB900725.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-kb900725-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%\$NTUninstallKB900725$\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 Folder
Fldrclnr.dll
6.0.2800.1579
20-Aug-2004
22:01
82,432
SP1QFE
Linkinfo.dll
5.1.2600.1740
01-Sep-2005
01:49
16,384
SP1QFE
Shell32.dll
6.0.2800.1751
23-Sep-2005
03:27
8,348,672
SP1QFE
Shlwapi.dll
6.0.2800.1740
01-Sep-2005
01:49
409,088
SP1QFE
Sxs.dll
5.1.2600.1579
20-Aug-2004
22:01
700,928
SP1QFE
Winsrv.dll
5.1.2600.1740
01-Sep-2005
01:49
278,016
SP1QFE
Comctl32.dll
6.0.2800.1740
01-Sep-2005
01:49
925,184
SP1QFE\ASMS\60\MSFT\WINDOWS\COMMON\CONTROLS
Controls.man
01-Sep-2005
01:52
1,812
SP1QFE\ASMS\60\MSFT\WINDOWS\COMMON\CONTROLS
Comctl.man
01-Sep-2005
01:52
621
SP1QFE\ASMS\60\POLICY\60\COMCTL
Linkinfo.dll
5.1.2600.2751
01-Sep-2005
01:41
19,968
SP2GDR
Shell32.dll
6.0.2900.2763
23-Sep-2005
03:05
8,450,560
SP2GDR
Shlwapi.dll
6.0.2900.2753
02-Sep-2005
23:52
473,600
SP2GDR
Winsrv.dll
5.1.2600.2751
01-Sep-2005
01:41
291,840
SP2GDR
Linkinfo.dll
5.1.2600.2751
01-Sep-2005
01:44
19,968
SP2QFE
Shell32.dll
6.0.2900.2763
23-Sep-2005
03:18
8,452,608
SP2QFE
Shlwapi.dll
6.0.2900.2753
02-Sep-2005
23:53
474,112
SP2QFE
Winsrv.dll
5.1.2600.2751
01-Sep-2005
01:44
291,840
SP2QFE
Xpsp3res.dll
5.1.2600.2764
27-Sep-2005
00:29
21,504
SP2QFE
Arpidfix.exe
5.1.2600.2764
27-Sep-2005
00:36
30,720
Windows XP Professional x64:
File Name Version Date Time Size CPU Folder
Linkinfo.dll
5.2.3790.2521
09-Sep-2005
19:06
31,744
x64
SP1GDR
Shell32.dll
6.0.3790.2521
09-Sep-2005
19:06
10,491,392
x64
SP1GDR
Shlwapi.dll
6.0.3790.2523
09-Sep-2005
19:06
621,568
x64
SP1GDR
Winsrv.dll
5.2.3790.2521
09-Sep-2005
19:06
509,952
x64
SP1GDR
Wlinkinfo.dll
5.2.3790.2521
09-Sep-2005
19:06
20,480
x86
SP1GDR\WOW
Wshell32.dll
6.0.3790.2521
09-Sep-2005
19:06
8,379,392
x86
SP1GDR\WOW
Wshlwapi.dll
6.0.3790.2523
09-Sep-2005
19:06
321,536
x86
SP1GDR\WOW
Linkinfo.dll
5.2.3790.2521
09-Sep-2005
19:08
31,744
x64
SP1QFE
Shell32.dll
6.0.3790.2521
09-Sep-2005
19:08
10,491,904
x64
SP1QFE
Shlwapi.dll
6.0.3790.2523
09-Sep-2005
19:08
621,568
x64
SP1QFE
Winsrv.dll
5.2.3790.2521
09-Sep-2005
19:08
509,440
x64
SP1QFE
Wlinkinfo.dll
5.2.3790.2521
09-Sep-2005
19:08
20,480
x86
SP1QFE\WOW
Wshell32.dll
6.0.3790.2521
09-Sep-2005
19:08
8,379,904
x86
SP1QFE\WOW
Wshlwapi.dll
6.0.3790.2523
09-Sep-2005
19:08
321,536
x86
SP1QFE\WOW
Arpidfix.exe
5.2.3790.2526
09-Sep-2005
19:10
43,008
x64
Notes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the Update.exe installer, visit the Microsoft TechNet Web site.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
Arpidfix.exe is used by the security update installer to address an issue documented in Microsoft Knowledge Base Article 904630. This file is not installed onto the affected system.
Verifying that the Update Has Been Applied
•
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
•
File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
Click Start, and then click Search.
In the Search Results pane, click All files and folders under Search Companion.
In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
•
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the following registry keys.
For Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB900725\Filelist
For Windows XP Professional x64 Edition:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP2\KB900725\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 900725 security update into the Windows installation source files.
Top of sectionTop of section
Windows 2000 (all versions)
Prerequisites
For Windows 2000, this security update requires Service Pack 4 (SP4). For Small Business Server 2000, this security update requires Small Business Server 2000 Service Pack 1a (SP1a) or Small Business Server 2000 running with Windows 2000 Server Service Pack 4 (SP4).
The software that is listed has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.
For more information about how to obtain the latest service pack, see Microsoft Knowledge Base Article 260910.
Inclusion in Future Service Packs:
The update for this issue may be included in a future Update Rollup.
Installation Information
This security update supports the following setup switches.
Supported Security Update Installation Switches
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. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
Deployment Information
To install the security update without any user intervention, use the following command at a command prompt for Windows 2000 Service Pack 4:
Windows2000-kb900725-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 KB900725.log file for any failure messages when they use this switch.
To install the security update without forcing the system to restart, use the following command at a command prompt for Windows 2000 Service Pack 4:
Windows2000-kb900725-x86-enu /norestart
For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.
Restart Requirement
You must restart your system after you apply this security update.
Removal Information
To remove this security update, use the Add or Remove Programs tool in Control Panel.
System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB900725$\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 2000 Service Pack 4 and Small Business Server 2000:
File Name Version Date Time Size Folder
Linkinfo.dll
5.0.2195.7069
23-Sep-2005
11:03
17,680
Shell32.dll
5.0.3900.7071
23-Sep-2005
11:03
2,360,592
Shlwapi.dll
5.0.3900.7068
25-Aug-2005
07:13
284,432
Webvw.dll
5.0.3900.7069
23-Sep-2005
11:03
1,120,016
Winsrv.dll
5.0.2195.7061
23-Sep-2005
11:03
245,008
Winsrv.dll
5.0.2195.7061
23-Sep-2005
11:03
245,008
UNIPROC
Shlwapi.dll
6.0.2800.1740
12-Sep-2005
04:00
409,088
XPSP2_BINARYDROP
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.
Click Start, and then click Search.
In the Search Results pane, click All files and folders under Search Companion.
In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
•
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB900725\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 900725 security update into the Windows installation source files.
Top of sectionTop of section
Top of sectionTop of section
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
•
Cesar Cerrudo of Argeniss for reporting the Shell Vulnerability (CAN-2005-2122) and the Shell Vulnerability (CAN-2005-2118).
•
Brett Moore of security-assessment.com for reporting the Web View Script Injection Vulnerability (CAN-2005-2117).
Obtaining Other Security Updates:
Updates for other security issues are available at the following locations:
•
Security updates are available in the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch."
•
Updates for consumer platforms are available at the Microsoft Update Web site.
Support:
•
Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
•
International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.
Security Resources:
•
The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
•
Microsoft Software Update Services
•
Microsoft Windows Server Update Services
•
Microsoft Baseline Security Analyzer (MBSA)
•
Windows Update
•
Microsoft Update
•
Windows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.
•
Office Update
Software Update Services:
By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.
For more information about how to deploy 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 (October 11, 2005): Bulletin published.
Related
