Microsoft Security Bulletin MS05-003
Vulnerability in the Indexing Service Could Allow Remote Code Execution (871250)
Issued: January 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 consider applying the security update.
Security Update Replacement: None
Caveats: None
Tested Software and Security Update Download Locations:
Affected Software:
- Microsoft Windows 2000 Service Pack 3 and Microsoft Windows 2000 Service Pack 4 – Download the update
- Microsoft Windows XP Service Pack 1 – Download the update
- Microsoft Windows XP 64-Bit Edition Service Pack 1 – Download the update
- Microsoft Windows XP 64-Bit Edition Version 2003 – Download the update
- Microsoft Windows Server 2003 – Download the update
- Microsoft Windows Server 2003 64-Bit Edition – Download the update
Non-Affected Software:
- Microsoft Windows NT Server 4.0 Service Pack 6a
- Microsoft Windows NT Server 4.0 Terminal Server Edition Service Pack 6
- Microsoft Windows XP Service Pack 2
- Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME)
Tested Microsoft Windows Components:
Affected Components:
- Indexing Service
The software in this list has been tested to determine if the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support lifecycle for your product and version, visit the following Microsoft Support Lifecycle Web site.
General Information
Executive Summary
Executive Summary:
This update resolves a newly-discovered, privately 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 privileges. While remote code execution is possible, an attack would most likely result in a denial of service condition.
We recommend that customers consider applying the security update.
Severity Ratings and Vulnerability Identifiers:
| Vulnerability Identifiers | Impact of Vulnerability | Windows 2000 | Windows XP Service Pack 1 | Windows Server 2003 |
|---|---|---|---|---|
| Indexing Service Vulnerability - CAN-2004-0897 | Remote Code Execution | None | 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.
Frequently asked questions (FAQ) related to this security update
Does this update contain any other security-related changes to functionality?
Yes. In addition to the changes that are listed in the Vulnerability Details section of this bulletin, this update includes the following change in functionality: The Microsoft.ISAdm.1 ActiveX control has been updated with enhanced security.
Why is Windows 2000 listed as affected software when the Indexing Service Vulnerability (CAN-2004-0897) is rated “None”?
Windows 2000 is not affected by this vulnerability. However the additional security-related change does affect Windows 2000 and we recommend customers install this update.
I am still using Windows XP, but extended security update support ended on September 30th, 2004. What should I do?
The original version of Windows XP, commonly known as Windows XP Gold or Windows XP Release to Manufacturing (RTM) version, reached the end of its extended security update support life cycle on September 30, 2004.
It should be a priority for customers who have this operating system version to migrate to supported operating system versions to prevent potential exposure to vulnerabilities. For more information about the Windows Service Pack Product Life Cycle, visit the Microsoft Support Lifecycle Web site. For more information about the Windows Product Life Cycle, visit the Microsoft Support Lifecycle Web site.
For more information, visit the Windows Operating System FAQ.
I am still using Windows 2000 Service Pack 2, but extended security update support ended on June 30, 2004. What should I do?
Windows 2000 Service Pack 2 reached the end of its extended support life cycle as previously documented. It should be a priority for customers who have this operating system version to migrate to supported operating system versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Life Cycle, visit the Microsoft Support Lifecycle Web site. For more information about the extended security update support period for this operating system version, visit the Microsoft Product Support Services Web site.
For more information, visit the Windows Operating System FAQ.
Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine if this update is required?
Yes. MBSA will determine if this update is required. For more information about MBSA, visit the MBSA Web site.
Note After April 20, 2004, the Mssecure.xml file that is used by MBSA 1.1.1 and earlier versions is no longer being updated with new security bulletin data. Therefore, scans that are performed after that date with MBSA 1.1.1 or earlier will be incomplete. All users should upgrade to MBSA 1.2 because it provides more accurate security update detection and supports additional products. Users can download MBSA 1.2.1 from the MBSA Web site. For more information about MBSA support, visit the following Microsoft Baseline Security Analyzer 1.2 Q&A Web site.
Can I use Systems Management Server (SMS) to determine if this update is required?
Yes. SMS can help detect and deploy this security update. For information about SMS, visit the SMS Web site. The Security Update Inventory Tool is required for detecting Microsoft Windows and other affected Microsoft products. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460
Vulnerability Details
Indexing Service Vulnerability - CAN-2004-0897:
A remote code execution vulnerability exists in the Indexing Service because of the way that it handles query validation. An attacker could exploit the vulnerability by constructing a malicious query that could potentially allow remote code execution on an affected system. An attacker who successfully exploited this vulnerability could take complete control of an affected system. While remote code execution is possible, an attack would most likely result in a denial of service condition.
Mitigating Factors for Indexing Service Vulnerability - CAN-2004-0897:
- The Indexing Service is not enabled by default on the affected systems.
- Even when the Indexing Service is installed, by default it is not accessible from Internet Information Services (IIS). Manual steps are required to enable (IIS) to become a Web-based interface for the Indexing Service. By default the Indexing Service is used only to perform local and remote file system queries. Web-based query pages must be created or installed manually that will allow IIS to receive queries from anonymous users and pass those queries to the Indexing Service.
- Only users with permissions to access the manually created or installed queries pages would be able to attempt to exploit this vulnerability through IIS. If these Web-based query pages require authenticated access, anonymous users would not be able to exploit this vulnerable through IIS.
- If none of the Web-based query methods have been manually enabled, only authenticated users would be able to attempt to exploit this vulnerability through remote file system queries.
- Windows 2000 is not affected by this vulnerability. However the additional security-related change does affect Windows 2000 and we recommend customers install this update.
- 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.
Workarounds for Indexing Service Vulnerability - CAN-2004-0897:
Microsoft has tested the following workarounds. While these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified below.
- Block the following at the firewall:
- UDP ports 137 and 138 and TCP ports 139 and 445
These ports could be used to initiate a connection with the Indexing Service to perform file system based queries. Blocking them at the firewall will help prevent systems that are behind that firewall from attempts to exploit this vulnerability through these ports. We recommend that you block all unsolicited inbound communication from the Internet to help prevent attacks that may use other ports.
- Use a personal firewall such as the Internet Connection Firewall, which is included with Windows XP and Windows Server 2003.
If you use the Internet Connection Firewall feature in Windows XP or in Windows Server 2003 to help protect your Internet connection, it blocks unsolicited inbound traffic by default. We recommend that you block all unsolicited inbound communication from the Internet.
To enable the Internet Connection Firewall feature by using the Network Setup Wizard, follow these steps:
- Click Start, and then click Control Panel.
- In the default Category View, click Network and Internet Connections, and then click Setup or change your home or small office network. The Internet Connection Firewall feature is enabled when you select a configuration in the Network Setup Wizard that indicates that your system is connected directly to the Internet.
To configure Internet Connection Firewall manually for a connection, follow these steps:
- Click Start, and then click Control Panel.
- In the default Category View, click Networking and Internet Connections, and then click Network Connections.
- Right-click the connection on which you want to enable Internet Connection Firewall, and then click Properties.
- Click the Advanced tab.
- Click to select the Protect my computer or network by limiting or preventing access to this computer from the Internet check box, and then click OK.
Note If you want to enable the use of some programs and services through the firewall, click Settings on the Advanced tab, and then select the programs, protocols, and services that are required.
- Enable advanced TCP/IP filtering on systems that support this feature.
You can enable advanced TCP/IP filtering to block all unsolicited inbound traffic. For more information about how to configure TCP/IP filtering, see Microsoft Knowledge Base Article 309798.
- Block the affected ports by using IPSec on the affected systems.
Use Internet Protocol security (IPSec) to help protect network communications. Detailed information about IPSec and how to apply filters is available in Microsoft Knowledge Base Article 313190 and Microsoft Knowledge Base Article 813878.
- Remove the Indexing Service if you do not need it:
If the Indexing Service is no longer needed, you could remove it by following this procedure.
To configure components and services:
- In Control Panel, open Add or Remove Programs.
- Click Add/Remove Windows Components.
- Click to clear the Indexing Service check box to remove the Indexing Service.
- Complete the Windows Components Wizard by following the instructions on the screen.
- You could modify any web pages that use the Index Service to block queries longer than 60 characters. Microsoft Knowledge Base Article 890621 provides more information on how to perform these steps.
FAQ for Indexing Service Vulnerability - CAN-2004-0897:
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full privileges. While remote code execution is possible, an attack would most likely result in a denial of service condition. There are also significant mitigating factors that exist that helps reduce the severity of this vulnerability. For more information see the Mitigating Factors section of the security bulletin.
What causes the vulnerability?
An unchecked buffer in the Indexing Service.
What is Indexing Service?
The Indexing Service is a base service for the affected operating systems. Formerly known as Index Server, its original function was to index the content of Internet Information Services (IIS) Web servers. Indexing Service now creates indexed catalogs for the contents and properties of both file systems and virtual Webs.
The Indexing Service is available to applications and scripts for providing an efficient means of managing, querying, and indexing information in file systems or Web servers. Indexing Service also provides query mechanisms for efficiently accessing the information in the catalogs. The indexed information results from filtering the file systems and the Web servers using Microsoft-supplied filters and, optionally, custom-supplied filters.
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?
On systems where administrators have manually performed multiple steps and have enabled an anonymous Web-based query interface through Internet Information Services (IIS) to the Indexing Service, any anonymous user who could deliver a specially crafted message to the affected system could attempt to exploit this vulnerability. By default, the Indexing Service does not enable the Web-based query interface. However, the Indexing Service does listen on the local network interface for communication requests by default. Any authenticated user could attempt to exploit this vulnerable by sending a specially-crafted network packet to the Indexing Service. This vulnerability could also be used locally by an authenticated user to attempt a local elevation of privilege attack.
What systems are primarily at risk from the vulnerability?
Systems that have the Indexing Service enabled are primarily at risk from this vulnerability from local or network based attacks. Systems that have the Indexing Service accessible through IIS are at risk from this vulnerability from Internet based attacks. If the Indexing Service is not enabled the system would not be vulnerable to this issue. None of the affected systems enable the Indexing Service by default.
Could the vulnerability be exploited over the Internet?
Yes. An attacker could attempt to exploit this vulnerability over the Internet. Firewall best practices and standard default firewall configurations can help protect against attacks that originate from the Internet. Microsoft has provided information on how you can help protect your PC. End users can visit the Protect Your PC Web site. IT Professionals can visit the Security Center Web site.
What does the update do?
The update removes the vulnerability by modifying the way that Indexing Service validates the length of a message before it passes the message to the allocated buffer.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft had not received any information indicating 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 indicating 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.
Security Update Information
Installation Platforms and Prerequisites:
For information about the specific security update for your platform, click the appropriate link:
Windows Server 2003 (all versions)
Prerequisites
This security update requires a release version of Windows Server 2003.
Inclusion in Future Service Packs:
The update for this issue will be included in Windows Server 2003 Service Pack 1.
Installation Information
This security update supports the following setup switches:
/help Displays the command line options
Setup Modes
/quiet Quiet mode (no user interaction or display)
/passive Unattended mode (progress bar only)
/uninstall Uninstalls the package
Restart Options
/norestart Do not restart when installation is complete
/forcerestart Restart after installation
Special Options
/l Lists installed Windows hotfixes or update packages
/o Overwrite OEM files without prompting
/n Do not backup files needed for uninstall
/f Force other programs to close when the computer shuts down
/integrate:path Integrates the update into the Windows source files located at the path specified.
/extract Extracts files without starting setup
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the previous version of the setup utility uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. 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-kb871250-x86-enu /passive /quiet
To install the security update without forcing the system to restart, use the following command at a command prompt for Windows Server 2003:
Windowsserver2003-kb871250-x86-enu /norestart
For information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.
Restart Requirement
This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are in use, this update will require a restart. If this occurs, a message appears that advises you to restart. To help reduce the chance that a reboot will not be required, stop all affected services and close all applications that may use the affected files prior to installing the 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%\$NTUninstallKB871250$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:
/help Displays the command line options
Setup Modes
/quiet Quiet mode (no user interaction or display)
/passive Unattended mode (progress bar only)
Restart Options
/norestart Do not restart when installation is complete
/forcerestart Restart after installation
Special Options
/f Force other programs to close when the computer shuts down
File Information
The English version of this update has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows Server 2003 Enterprise Edition, Windows Server 2003 Standard Edition, Windows Server 2003 Web Edition, and Windows Server 2003 Datacenter Edition:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| Ciodm.dll | 5.2.3790.220 | 18-Oct-2004 | 08:19 | 66,048 | RTMGDR |
| Query.dll | 5.2.3790.220 | 18-Oct-2004 | 08:19 | 1,359,872 | RTMGDR |
| Ciodm.dll | 5.2.3790.220 | 18-Oct-2004 | 08:39 | 66,048 | RTMQFE |
| Query.dll | 5.2.3790.220 | 18-Oct-2004 | 08:39 | 1,359,872 | RTMQFE |
Windows Server 2003 64-Bit Enterprise Edition and Windows Server 2003 64-Bit Datacenter Edition:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| Ciodm.dll | 5.2.3790.220 | 18-Oct-2004 | 08:19 | 202,240 | IA-64 | RTMGDR |
| Query.dll | 5.2.3790.220 | 18-Oct-2004 | 08:19 | 4,809,728 | IA-64 | RTMGDR |
| Wciodm.dll | 5.2.3790.220 | 18-Oct-2004 | 08:19 | 66,048 | x86 | RTMGDR\WOW |
| Wquery.dll | 5.2.3790.220 | 18-Oct-2004 | 08:19 | 1,359,872 | x86 | RTMGDR\WOW |
| Ciodm.dll | 5.2.3790.220 | 18-Oct-2004 | 08:39 | 202,240 | IA-64 | RTMQFE |
| Query.dll | 5.2.3790.220 | 18-Oct-2004 | 08:39 | 4,809,728 | IA-64 | RTMQFE |
| Wciodm.dll | 5.2.3790.220 | 18-Oct-2004 | 08:39 | 66,048 | x86 | RTMQFE\WOW |
| Wquery.dll | 5.2.3790.220 | 18-Oct-2004 | 08:39 | 1,359,872 | x86 | RTMQFE\WOW |
Note When you install this security update on Windows Server 2003, the installer checks to see if any of the files that are being updated on your system have previously been updated by a Microsoft hotfix. If you have previously installed a hotfix to update an affected file, the installer copies the RTMQFE files to your system. Otherwise, the installer copies the RTMGDR files to your system.
For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the Update.exe installer, visit the Microsoft TechNet Web site.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
Verifying Update Installation
- Microsoft Baseline Security Analyzer
To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. This tool allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
- File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
- On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying the update installation. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
- Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the following registry keys.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB871250\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 871250 security update into the Windows installation source files.
Windows XP (all versions)
Note For Windows XP 64-Bit Edition Version 2003, this security update is the same as the Windows Server 2003 64-Bit Edition security update.
Prerequisites
This security update requires the release version Windows XP Service Pack 1 (SP1). For more information, see Microsoft Knowledge Base Article 322389.
Inclusion in Future Service Packs:
The update for this issue is included in Windows XP Service Pack 2.
Installation Information
This security update supports the following setup switches:
/help Displays the command line options
Setup Modes
/quiet Quiet mode (no user interaction or display)
/passive Unattended mode (progress bar only)
/uninstall Uninstalls the package
Restart Options
/norestart Do not restart when installation is complete
/forcerestart Restart after installation
Special Options
/l Lists installed Windows hotfixes or update packages
/o Overwrite OEM files without prompting
/n Do not backup files needed for uninstall
/f Force other programs to close when the computer shuts down
/integrate:path Integrates the update into the Windows source files located at the path specified.
/extract Extracts files without starting setup
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the previous version of the setup utility uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. 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 XP:
Windowsxp-kb871250-x86-enu /passive /quiet
To install the security update without forcing the system to restart, use the following command at a command prompt for Windows XP:
Windowsxp-kb871250-x86-enu /norestart
For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.
Restart Requirement
This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are in use, this update will require a restart. If this occurs, a message appears that advises you to restart. To help reduce the chance that a reboot will not be required, stop all affected services and close all applications that may use the affected files prior to installing the security update.
Removal Information
To remove this security update, use the Add or Remove Programs tool in Control Panel.
System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe is located in the %Windir%\$NTUninstallKB871250$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:
/help Displays the command line options
Setup Modes
/quiet Quiet mode (no user interaction or display)
/passive Unattended mode (progress bar only)
Restart Options
/norestart Do not restart when installation is complete
/forcerestart Restart after installation
Special Options
/f Force other programs to close when the computer shuts down
File Information
The English version of this update has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Ciodm.dll | 5.1.2600.1596 | 28-Oct-2004 | 15:45 | 64,512 |
| Query.dll | 5.1.2600.1596 | 28-Oct-2004 | 15:45 | 1,350,144 |
Windows XP 64-Bit Edition Service Pack 1:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| Ciodm.dll | 5.1.2600.1596 | 28-Oct-2004 | 15:43 | 203,776 | IA-64 | SP1QFE |
| Query.dll | 5.1.2600.1596 | 28-Oct-2004 | 15:43 | 4,942,336 | IA-64 | SP1QFE |
| Wciodm.dll | 5.1.2600.1596 | 28-Oct-2004 | 15:46 | 64,512 | x86 | SP1QFE\WOW |
| Wquery.dll | 5.1.2600.1596 | 28-Oct-2004 | 15:46 | 1,350,144 | x86 | SP1QFE\WOW |
Windows XP 64-Bit Edition Version 2003:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| Ciodm.dll | 5.2.3790.220 | 18-Oct-2004 | 08:19 | 202,240 | IA-64 | RTMGDR |
| Query.dll | 5.2.3790.220 | 18-Oct-2004 | 08:19 | 4,809,728 | IA-64 | RTMGDR |
| Wciodm.dll | 5.2.3790.220 | 18-Oct-2004 | 08:19 | 66,048 | x86 | RTMGDR\WOW |
| Wquery.dll | 5.2.3790.220 | 18-Oct-2004 | 08:19 | 1,359,872 | x86 | RTMGDR\WOW |
| Ciodm.dll | 5.2.3790.220 | 18-Oct-2004 | 08:39 | 202,240 | IA-64 | RTMQFE |
| Query.dll | 5.2.3790.220 | 18-Oct-2004 | 08:39 | 4,809,728 | IA-64 | RTMQFE |
| Wciodm.dll | 5.2.3790.220 | 18-Oct-2004 | 08:39 | 66,048 | x86 | RTMQFE\WOW |
| Wquery.dll | 5.2.3790.220 | 18-Oct-2004 | 08:39 | 1,359,872 | x86 | RTMQFE\WOW |
Notes The Windows XP 64-Bit Edition Version 2003 version of this security update is packaged as a dual-mode package. Dual-mode packages contain files for the multiple versions of the affected operating system. For more information about dual-mode packages, see Microsoft Knowledge Base Article 328848.
When you install this security update on Windows XP 64-Bit Edition Version 2003 the installer checks to see if any of the files that are being updated on your system have previously been updated by a Microsoft hotfix. If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE files to your system. Otherwise, the installer copies the RTMGDR files to your system.
For more information 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 Update Installation
- Microsoft Baseline Security Analyzer
To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. This tool allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
- File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
- On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying the update installation. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
- Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the following registry keys.
For Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP2\KB871250\Filelist
For Windows XP 64-Bit Edition Version 2003:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB871250\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 871250 security update into the Windows installation source files.
Windows 2000 (all versions)
Prerequisites
For Windows 2000, this security update requires Service Pack 3 (SP3) or Service Pack 4 (SP4).
The software that is listed has been tested to determine if the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support lifecycle for your product and version, visit the Microsoft Support Lifecycle Web site.
For more information about how to obtain the latest service pack, see Microsoft Knowledge Base Article 260910.
Inclusion in Future Service Packs:
The update for this issue will be included in a future Update Rollup.
Installation Information
This security update supports the following setup switches:
/help Displays the command line options
Setup Modes
/quiet Quiet mode (no user interaction or display)
/passive Unattended mode (progress bar only)
/uninstall Uninstalls the package
Restart Options
/norestart Do not restart when installation is complete
/forcerestart Restart after installation
Special Options
/l Lists installed Windows hotfixes or update packages
/o Overwrite OEM files without prompting
/n Do not backup files needed for uninstall
/f Force other programs to close when the computer shuts down
/integrate:path Integrates the update into the Windows source files located at the path specified.
/extract Extracts files without starting setup
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the previous version of the setup utility uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
Deployment Information
To install the security update without any user intervention, use the following command at a command prompt for Windows 2000 Service Pack 3 and Windows 2000 Service Pack 4:
Windows2000-kb871250-x86-enu /passive /quiet
To install the security update without forcing the system to restart, use the following command at a command prompt for Windows 2000 Service Pack 3 and Windows 2000 Service Pack 4:
Windows2000-kb871250-x86-enu /norestart
For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.
Restart Requirement
This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are in use, this update will require a restart. If this occurs, a message appears that advises you to restart. To help reduce the chance that a reboot will not be required, stop all affected services and close all applications that may use the affected files prior to installing the 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%\$NTUninstallKB871250$\Spuninst folder. The Spuninst.exe utility supports the following setup switches:
/help Displays the command line options
Setup Modes
/quiet Quiet mode (no user interaction or display)
/passive Unattended mode (progress bar only)
Restart Options
/norestart Do not restart when installation is complete
/forcerestart Restart after installation
Special Options
/f Force other programs to close when the computer shuts down
File Information
The English version of this update has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Note Date, time, file name, or size information could change during installation. See the Verifying Update Installation section for details about how to verify an installation.
Windows 2000 Service Pack 3 and Windows 2000 Service Pack 4:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| Ciodm.dll | 5.0.2195.6981 | 05-Nov-2004 | 04:41 | 68,880 |
Verifying Update Installation
- Microsoft Baseline Security Analyzer
To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. This tool allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
- File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
- On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying the update installation. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
- Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB871250\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 871250 security update into the Windows installation source files.
Other Information
Obtaining Other Security Updates:
Updates for other security issues are available from the following locations:
- Security updates are available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch."
- Updates for consumer platforms are available from the Windows Update Web site.
Support:
- Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
- International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.
Security Resources:
- The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
- Microsoft Software Update Services
- Microsoft Baseline Security Analyzer (MBSA)
- Windows Update
- Windows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.
- Office Update
Software Update Services:
By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.
For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.
Systems Management Server:
Microsoft Systems Management Server (SMS) delivers a highly-configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and to perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, visit the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site.
Note SMS uses the Microsoft Baseline Security Analyzer and the Microsoft Office Detection Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, see the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.
Disclaimer:
The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Revisions:
- V1.0 (January 11, 2005): Bulletin published