Security Bulletin
Microsoft Security Bulletin MS06-075 - Important
Vulnerability in Windows Could Allow Elevation of Privilege (926255)
Published: December 12, 2006
Version: 1.0
Summary
Who Should Read this Document: Customers who use Microsoft Windows
Impact of Vulnerability: Elevation of Privilege
Maximum Severity Rating: Important
Recommendation: Customers should apply the update at the earliest opportunity
Security Update Replacement: None.
Caveats: None.
Tested Software and Security Update Download Locations:
Affected Software:
- Microsoft Windows XP Service Pack 2 — Download the update
- Microsoft Windows Server 2003— Download the update
- Microsoft Windows Server 2003 for Itanium-based Systems— Download the update
Non-Affected Software:
- Microsoft Windows 2000 Service Pack 4
- Microsoft Windows XP Professional x64 Edition
- Microsoft Windows Server 2003 Service Pack 1
- Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based Systems
- Microsoft Windows Server 2003 x64 Edition
- Windows Vista
The software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.
General Information
Executive Summary
Executive Summary:
This update resolves a privately identified vulnerability. The vulnerability is documented in the "Vulnerability Details" section of this bulletin.
We recommend that customers apply the update at the earliest opportunity.
Severity Ratings and Vulnerability Identifiers:
| Vulnerability Identifiers | Impact of Vulnerability | Windows XP Service Pack 2 | Windows Server 2003 |
|---|---|---|---|
| File Manifest Corruption Vulnerability - CVE-2006-5585 | Elevation of Privilege\ | 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 Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.
Frequently Asked Questions (FAQ) Related to This Security Update
Extended security update support for Microsoft Windows 98, Windows 98 Second Edition, or Windows Millennium Edition ended on July 11, 2006. I am still using one of these operating systems; what should I do?
Windows 98, Windows 98 Second Edition, and Windows Millennium Edition have reached the end of their support 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.
Extended security update support for Microsoft Windows XP Home Edition Service Pack 1 or Service Pack 1a, Windows XP Media Center Edition 2002 Service Pack 1, Windows XP Media Center Edition 2004 Service Pack 1, Windows XP Professional Service Pack 1 or Service Pack 1a, and Windows XP Tablet PC Edition Service Pack 1 ended on October 10, 2006. I am still using one of these operating systems; what should I do?
Windows XP (all versions) Service Pack 1 has reached the end of its support life cycle. 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.
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 support 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 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.
Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?
The following table provides the MBSA detection summary for this security update.
| Product | MBSA 1.2.1 | MBSA 2.0 |
|---|---|---|
| Microsoft Windows XP Service Pack 2 | Yes | Yes |
| Microsoft Windows Server 20003 | Yes | Yes |
| Microsoft Windows Server 2003 for Itanium-based Systems | No | Yes |
For more information about MBSA, visit the MBSA Web site. For more information about the programs that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.
For more detailed information, see Microsoft Knowledge Base Article 910723.
Can I use Systems Management Server (SMS) to determine whether this update is required?
The following table provides the SMS detection summary for this security update.
| Product | SMS 2.0 | SMS 2003 |
|---|---|---|
| Microsoft Windows XP Service Pack 2 | Yes | Yes |
| Microsoft Windows Server 2003 | Yes | Yes |
| Microsoft Windows Server 2003 for Itanium-based Systems | No | Yes |
SMS 2.0 and SMS 2003 Software Update Services (SUS) Feature Pack can use MBSA 1.2.1 for detection and therefore have the same limitation that is listed earlier in this bulletin related to programs that MBSA 1.2.1 does not detect.
For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about SUIT, visit the following Microsoft Web site. For more information about the limitations of SUIT, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.
For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.
For more information about SMS, visit the SMS Web site.
For more detailed information, see Microsoft Knowledge Base Article 910723.
Vulnerability Details
File Manifest Corruption Vulnerability - CVE-2006-5585:
A privilege elevation vulnerability exists in the way that Microsoft Windows starts applications with specially crafted file manifests. This vulnerability could allow a logged on user to take complete control of the system.
Mitigating Factors for File Manifest Corruption Vulnerability - CVE-2006-5585:
- An attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability. The vulnerability could not be exploited remotely or by anonymous users.
Workarounds for File Manifest Corruption Vulnerability - CVE-2006-5585:
No workarounds have been identified for this vulnerability.
FAQ for File Manifest Corruption Vulnerability - CVE-2006-5585:
What is the scope of the vulnerability?
This is a privilege elevation 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 user rights. To attempt to exploit the vulnerability, an attacker must be able to log on locally to the system and run a program.
What causes the vulnerability?
Improper processing and management of file manifests by the Client-Server Run-time Subsystem.
What is the Client Server Run-Time Subsystem?
Csrss is the user-mode portion of the Win32 subsystem (with Win32.sys being the kernel-mode portion). Csrss stands for client/server run-time subsystem and is an essential subsystem that must be running at all times. Csrss is responsible for console windows, creating and/or deleting threads.
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?
To try to exploit the vulnerability, an attacker must be able to log on locally to a system and run a program
How could an attacker exploit the vulnerability?
To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and gain complete control over the affected system.
What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. 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. An attacker cannot load and run a program remotely by using this vulnerability.
What does the update do?
The update removes the vulnerability by modifying the way that Client Server Run-time Subsystem validates embedded file manifests before it passes data to the allocated buffer.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No this issue has not been previously publicly disclosed as a vulnerability.
How does this vulnerability relate to Microsoft Knowledge Base Article 921337
Microsoft Knowledge Base Article 921337 discusses a related issue with file manifest that could potentially cause a system to reboot. In reviewing this issue Microsoft identified a potential security vulnerability that is addressed by the release of this security update.
Security Update Information
Affected Software:
For information about the specific security update for your affected software, click the appropriate link:
Windows XP
Prerequisites
This security update requires Microsoft Windows XP Service Pack 2. 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.
| 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 forces other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Displays 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 uninstallation. |
| /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-kb926255-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 KB926255.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-kb926255-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
This update requires a restart.
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%\$NTUninstallKB926255$\Spuninst folder.
| 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 forces other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Displays 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 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 |
|---|---|---|---|---|---|
| Sxs.dll | 5.1.2600.3019 | 19-Oct-2006 | 13:56 | 713,216 | SP2GDR |
| Sxs.dll | 5.1.2600.3019 | 19-Oct-2006 | 13:59 | 713,216 | SP2QFE |
Notes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the Update.exe installer, visit the Microsoft TechNet Web site.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
Verifying that the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the frequently asked question, “Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?” in the section, Frequently Asked Questions (FAQ) Related to This Security Update, earlier in this bulletin.File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
- On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table. Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the following registry keys.Windows 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\KB926255\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 security update into the Windows installation source files.
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 future Service Pack or Update Rollup.
Installation Information
This security update supports the following setup 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 forces other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Displays 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 uninstallation. |
| /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-kb926255-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 KB926255.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-kb926255-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
This update requires a restart.
This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.
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%\$NTUninstallKB926255$\Spuninst folder.
| 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 forces other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Displays 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, Enterprise Edition; Windows Server 2003, Datacenter Edition; and Windows Small Business Server 2003:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| Sxs.dll | 5.2.3790.599 | 12-Oct-2006 | 14:44 | 749,568 | x86 | RTMGDR |
| Sxs.dll | 5.2.3790.599 | 12-Oct-2006 | 14:49 | 749,568 | x86 | RTMQFE |
Windows Server, 2003 Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003 for Itanium-based Systems.
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| Sxs.dll | 5.2.3790.599 | 12-Oct-2006 | 14:49 | 1,860,096 | IA-64 | RTMGDR |
| Wsxs.dll | 5.2.3790.599 | 12-Oct-2006 | 14:44 | 749,568 | x86 | RTMGDR\WOW |
| Sxs.dll | 5.2.3790.599 | 12-Oct-2006 | 14:48 | 1,860,096 | IA-64 | RTMQFE |
| Wsxs.dll | 5.2.3790.599 | 12-Oct-2006 | 14:49 | 749,568 | x86 | RTMQFE\WOW |
Notes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the Update.exe installer, visit the Microsoft TechNet Web site.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
Verifying that the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the frequently asked question, “Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?” in the section, Frequently Asked Questions (FAQ) Related to This Security Update, earlier in this bulletin.File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
- On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table. Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the following registry keys.Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003; Windows Server 2003, Enterprise Edition for Itanium-based Systems; and Windows Server 2003, Datacenter Edition for Itanium-based Systems:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB926255\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 926255 security update into the Windows installation source files.
Obtaining Other Security Updates:
Updates for other security issues are available at the following locations:
- Security updates are available at 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.
- TechNet Update Management Center
- 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 Scan 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.
Other Information
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 (December 12, 2006): Bulletin published.
Built at 2014-04-18T13:49:36Z-07:00