Microsoft Security Bulletin MS04-044 Vulnerabilities in Windows Kernel and LSASS Could Allow Elevation of Privilege (885835)

2004-12-15T00:00:00
ID SECURITYVULNS:DOC:7341
Type securityvulns
Reporter Securityvulns
Modified 2004-12-15T00:00:00

Description

Microsoft Security Bulletin MS04-044 Vulnerabilities in Windows Kernel and LSASS Could Allow Elevation of Privilege (885835)

Issued: December 14, 2004 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 install 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: Microsoft Knowledge Base Article 885835 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues. For more information, see Microsoft Knowledge Base Article 885835.

Tested Software and Security Update Download Locations:

Affected Software:

• Microsoft Windows NT Server 4.0 Service Pack 6a – Download the update

• Microsoft Windows NT Server 4.0 Terminal Server Edition Service Pack 6 – Download the update

• Microsoft Windows 2000 Service Pack 3 and Microsoft Windows 2000 Service Pack 4 – Download the update

• Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 – 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 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME)

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.

Top 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.

An attacker who successfully exploited the most severe of these vulnerabilities could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts that have full privileges.

We recommend that customers install the update at the earliest opportunity.

Severity Ratings and Vulnerability Identifiers:

Vulnerability Identifiers Impact of Vulnerability Windows NT 4.0 Windows 2000 Windows XP Service Pack 1 Windows XP Service Pack 2 and Windows Server 2003 Windows Kernel Vulnerability - CAN-2004-0893 Elevation of Privilege Important Important Important Moderate

LSASS Vulnerability - CAN-2004-0894 Elevation of Privilege None Important Important Important

Aggregate Severity of All Vulnerabilities

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.

Top 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 NT 4.0 Windows 2000 Windows XP Windows Server 2003 MS03-005 Not Applicable Not Applicable Replaced Not Applicable

MS03-013 Replaced Replaced Replaced Not Applicable

I am still using Microsoft Windows NT 4.0 Workstation Service Pack 6a or Windows 2000 Service Pack 2, but extended security update support ended on June 30, 2004. What should I do? Windows NT 4.0 Workstation Service Pack 6a and Windows 2000 Service Pack 2 have reached the end of their life cycles as previously documented. Microsoft extended this support to June 30, 2004.

It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Life Cycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the following Microsoft Product Support Services Web site.

Customers who require additional support for Windows NT Workstation 4.0 SP6a must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers who do not have an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of phone numbers. When you call, ask to speak with the local Premier Support sales manager.

For more information, see the Windows Operating System FAQ.

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.

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

Top of section Vulnerability Details

Windows Kernel Vulnerability - CAN-2004-0893:

A privilege elevation vulnerability exists in the way that the Windows Kernel launches applications. This vulnerability could allow a logged on user to take complete control of the system.

Mitigating Factors for Windows Kernel Vulnerability - CAN-2004-0893:

• 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.

• Attempts to exploit this vulnerability on systems that are running Windows XP Service Pack 2 or Windows Server 2003 would most likely result in a denial of service condition.

Top of section Workarounds for Windows Kernel Vulnerability - CAN-2004-0893:

We have not identified any workarounds for this vulnerability.

Top of section FAQ for Windows Kernel Vulnerability - CAN-2004-0893:

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, including installing programs; viewing, changing, or deleting data; or creating new accounts that have full privileges. 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? An unchecked buffer in a Local Procedure Call (LPC) interface does not validate the restriction that is put on the size of data that is sent through an LPC Port.

What is LPC? LPC is a message-passing service that is provided by Windows. This service allows threads and processes to communicate with each other. When a client process must request a service from a server process, there must be a way for the two processes to communicate with each other. There must be a way for the client process to make requests of the server, for the server to send responses to the client, and for each to determine their status. When the client process and the server process are located on different systems, Remote Procedure Call (RPC) is used. When they are located on the same system, LPC can be used.

What are LPC Ports? Every LPC has a collection of communications channels that are known as LPC ports. Each port carries one type of communication. For example, an LPC will always have a port that is used to allow one client to send messages to the server and a port that allows the server to send messages to each client. The LPC will also have other ports for other purposes, such as ports that allow threads within a process to coordinate their requests.

What might an attacker use the vulnerability to do? An attacker who successfully exploited this vulnerability could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts that have full privileges.

Who could exploit the vulnerability? 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 this vulnerability? To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially-designed application that could exploit the vulnerability, and thereby 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 are only at risk if users who do not have sufficient administrative credentials are given the ability 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 the Windows Kernel 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 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 section Top of section

LSASS Vulnerability - CAN-2004-0894:

A privilege elevation vulnerability exists in the way that the LSASS validates identity tokens. This vulnerability could allow a logged on user to take complete control of the system.

Mitigating Factors for LSASS Vulnerability - CAN-2004-0894:

• 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. However, as soon as an attacker had complete control of an affected system an attacker may be able to use that system to attack other network resources.

• Windows NT 4.0 Server is not affected by this vulnerability.

Top of section Workarounds for LSASS Vulnerability - CAN-2004-0894:

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.

We have not identified any workarounds for this vulnerability.

Top of section FAQ for LSASS Vulnerability - CAN-2004-0894:

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, including installing programs; viewing, changing, or deleting data; or creating new accounts that have full privileges. 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? Incomplete validation of connection information by the Local Security Authority Subsystem Service.

What is LSASS? The Local Security Authority Subsystem Service (LSASS) provides an interface for managing local security, domain authentication, and Active Directory service processes. It handles authentication for the client and for the server. The LSASS also contains features that are used to support Active Directory utilities.

What might an attacker use the vulnerability to do? An attacker who successfully exploited this vulnerability could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts that have full privileges.

Who could exploit the vulnerability? 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 this vulnerability? To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially-designed application that could exploit the vulnerability, and thereby gain complete control over the affected system. As soon as an attacker had complete control of an affected system, an attacker may be able to use that system to attack other network resources.

What systems are primarily at risk from the vulnerability? Workstations and terminal servers are primarily at risk. Servers are only at risk if users who do not have sufficient administrative credentials are given the ability 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 LSASS validates connection information.

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 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.

Top of section Top of section Top of section 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-kb885835-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-kb885835-x86-enu /norestart

For information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.

Restart Requirement

You must restart your system after you apply this security update.

Removal Information

To remove this update, use the Add or Remove Programs tool in Control Panel.

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB885835$\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 Lsasrv.dll 5.2.3790.220 18-Oct-2004 08:58 799,232 RTMGDR

Mrxsmb.sys 5.2.3790.221 12-Oct-2004 00:38 394,240 RTMGDR

Rdbss.sys 5.2.3790.221 12-Oct-2004 00:38 157,184 RTMGDR

Eventlog.dll 5.2.3790.212 18-Oct-2004 14:12 64,000 RTMQFE

Lsasrv.dll 5.2.3790.220 18-Oct-2004 14:12 801,792 RTMQFE

Mrxsmb.sys 5.2.3790.221 12-Oct-2004 00:29 395,264 RTMQFE

Rdbss.sys 5.2.3790.221 12-Oct-2004 00:29 158,208 RTMQFE

Windows Server 2003 64-Bit Enterprise Edition and Windows Server 2003 64-Bit Datacenter Edition:

File Name Version Date Time Size CPU Folder Lsasrv.dll 5.2.3790.220 18-Oct-2004 08:58 2,034,176 IA-64 RTMGDR

Mrxsmb.sys 5.2.3790.221 12-Oct-2004 00:40 1,121,280 IA-64 RTMGDR

Rdbss.sys 5.2.3790.221 12-Oct-2004 00:39 462,336 IA-64 RTMGDR

Eventlog.dll 5.2.3790.212 18-Oct-2004 09:00 167,936 IA-64 RTMQFE

Lsasrv.dll 5.2.3790.220 18-Oct-2004 09:00 2,038,784 IA-64 RTMQFE

Mrxsmb.sys 5.2.3790.221 12-Oct-2004 00:30 1,123,328 IA-64 RTMQFE

Rdbss.sys 5.2.3790.221 12-Oct-2004 00:30 464,896 IA-64 RTMQFE

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.

1. Click Start, and then click Search.

2. In the Search Results pane, click All files and folders under Search Companion.

3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.

4. 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.

5. 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\KB885835\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 885835 security update into the Windows installation source files.

Top of section

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) or 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 Windows XP Service Pack 3.

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-kb885835-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-kb885835-x86-enu /norestart

For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.

Restart Requirement

You must restart your system after you apply this security update.

Removal Information

To remove this security update, use the Add or Remove Programs tool in Control Panel.

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe is located in the %Windir%\$NTUninstallKB885835$\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, 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 Cscdll.dll 5.1.2600.1599 28-Oct-2004 01:29 92,160 SP1QFE

Lsasrv.dll 5.1.2600.1597 28-Oct-2004 01:29 681,984 SP1QFE

Mrxsmb.sys 5.1.2600.1599 12-Oct-2004 16:22 436,608 SP1QFE

Ntkrnlmp.exe 5.1.2600.1605 22-Oct-2004 07:29 1,900,032 SP1QFE

Ntkrnlpa.exe 5.1.2600.1605 22-Oct-2004 07:29 1,955,840 SP1QFE

Ntkrpamp.exe 5.1.2600.1605 22-Oct-2004 07:29 1,928,704 SP1QFE

Ntoskrnl.exe 5.1.2600.1605 22-Oct-2004 08:33 2,088,448 SP1QFE

Rdbss.sys 5.1.2600.1599 12-Oct-2004 16:22 170,112 SP1QFE

Shsvcs.dll 6.0.2800.1605 28-Oct-2004 01:29 116,736 SP1QFE

Lsasrv.dll 5.1.2600.2525 28-Oct-2004 01:21 721,920 SP2GDR

Mrxsmb.sys 5.1.2600.2541 28-Oct-2004 01:14 448,128 SP2GDR

Rdbss.sys 5.1.2600.2541 28-Oct-2004 01:13 174,592 SP2GDR

Lsasrv.dll 5.1.2600.2525 28-Oct-2004 01:28 721,920 SP2QFE

Mrxsmb.sys 5.1.2600.2541 28-Oct-2004 01:15 448,128 SP2QFE

Rdbss.sys 5.1.2600.2541 28-Oct-2004 01:14 174,592 SP2QFE

Windows XP 64-Bit Edition Service Pack 1:

File Name Version Date Time Size CPU Folder Cscdll.dll 5.1.2600.1599 28-Oct-2004 01:29 237,056 IA-64 SP1QFE

Lsasrv.dll 5.1.2600.1597 28-Oct-2004 01:29 2,072,064 IA-64 SP1QFE

Mrxsmb.sys 5.1.2600.1599 12-Oct-2004 05:07 1,287,552 IA-64 SP1QFE

Ntkrnlmp.exe 5.1.2600.1605 22-Oct-2004 07:30 5,833,344 IA-64 SP1QFE

Ntoskrnl.exe 5.1.2600.1605 22-Oct-2004 07:30 5,776,256 IA-64 SP1QFE

Rdbss.sys 5.1.2600.1599 12-Oct-2004 05:07 496,000 IA-64 SP1QFE

Shsvcs.dll 6.0.2800.1605 28-Oct-2004 01:29 326,144 IA-64 SP1QFE

Wcscdll.dll 5.1.2600.1599 28-Oct-2004 01:29 92,160 x86 SP1QFE\WOW

Wshsvcs.dll 6.0.2800.1605 28-Oct-2004 01:29 116,736 x86 SP1QFE\WOW

Windows XP 64-Bit Edition Version 2003:

File Name Version Date Time Size CPU Folder Lsasrv.dll 5.2.3790.220 18-Oct-2004 08:58 2,034,176 IA-64 RTMGDR

Mrxsmb.sys 5.2.3790.221 12-Oct-2004 00:40 1,121,280 IA-64 RTMGDR

Rdbss.sys 5.2.3790.221 12-Oct-2004 00:39 462,336 IA-64 RTMGDR

Eventlog.dll 5.2.3790.212 18-Oct-2004 09:00 167,936 IA-64 RTMQFE

Lsasrv.dll 5.2.3790.220 18-Oct-2004 09:00 2,038,784 IA-64 RTMQFE

Mrxsmb.sys 5.2.3790.221 12-Oct-2004 00:30 1,123,328 IA-64 RTMQFE

Rdbss.sys 5.2.3790.221 12-Oct-2004 00:30 464,896 IA-64 RTMQFE

Notes The Windows XP and Windows XP 64-Bit Edition Version 2003 versions of this security update are packaged as dual-mode packages. These dual-mode packages contain files for the original version of Windows XP Service Pack 1 (SP1) and files for Windows XP Service Pack 2 (SP2).

For more information about dual-mode packages, see Microsoft Knowledge Base Article 328848.

When you install this security update on Windows XP SP2 or on Windows XP 64-Bit Edition Version 2003, 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 an affected file, one of the following conditions occurs, depending on your operating system:

• Windows XP SP2

The installer copies the SP2QFE files to your system.

• Windows XP 64-Bit Edition Version 2003

The installer copies the RTMQFE files to your system.

If you have not previously installed a hotfix to update an affected file, one of the following conditions occurs, depending on your operating system:

• Windows XP SP2

The installer copies the SP2GDR files to your system.

• Windows XP 64-Bit Edition Version 2003

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.

1. Click Start, and then click Search.

2. In the Search Results pane, click All files and folders under Search Companion.

3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.

4. 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.

5. 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, 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\KB885835\Filelist

For Windows XP 64-Bit Edition Version 2003:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB885835\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 885835 security update into the Windows installation source files.

Top of section

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-kb885835-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-kb885835-x86-enu /norestart

For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.

Restart Requirement

You must restart your system after you apply this security update.

Removal Information

To remove this security update, use the Add or Remove Programs tool in Control Panel.

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB885835$\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 Advapi32.dll 5.0.2195.6876 24-Mar-2004 02:17 388,368

Browser.dll 5.0.2195.6866 24-Mar-2004 02:17 69,904

Dnsapi.dll 5.0.2195.6824 24-Mar-2004 02:17 134,928

Dnsrslvr.dll 5.0.2195.6876 24-Mar-2004 02:17 92,432

Eventlog.dll 5.0.2195.6883 24-Mar-2004 02:17 47,888

Kdcsvc.dll 5.0.2195.6890 24-Mar-2004 02:17 143,632

Kerberos.dll 5.0.2195.6903 11-Mar-2004 02:37 210,192

Ksecdd.sys 5.0.2195.6824 21-Sep-2003 00:32 71,888

Lsasrv.dll 5.0.2195.6987 15-Oct-2004 18:16 513,296

Lsass.exe 5.0.2195.6902 25-Feb-2004 23:59 33,552

Mountmgr.sys 5.0.2195.6897 10-Feb-2004 19:47 30,160

Mrxsmb.sys 5.0.2195.6994 01-Nov-2004 05:24 409,424

Msv1_0.dll 5.0.2195.6897 11-Mar-2004 02:37 123,152

Netapi32.dll 5.0.2195.6949 10-Jun-2004 16:58 309,008

Netlogon.dll 5.0.2195.6891 24-Mar-2004 02:17 371,472

Ntdsa.dll 5.0.2195.6896 24-Mar-2004 02:17 1,028,880

Ntkrnlmp.exe 5.0.2195.6992 21-Oct-2004 03:55 1,704,768

Ntkrnlpa.exe 5.0.2195.6992 21-Oct-2004 03:56 1,704,320

Ntkrpamp.exe 5.0.2195.6992 21-Oct-2004 03:56 1,726,080

Ntoskrnl.exe 5.0.2195.6992 21-Oct-2004 03:55 1,681,408

Rdbss.sys 5.0.2195.6988 15-Oct-2004 21:03 170,096

Samsrv.dll 5.0.2195.6897 24-Mar-2004 02:17 388,368

Scecli.dll 5.0.2195.6893 24-Mar-2004 02:17 111,376

Scesrv.dll 5.0.2195.6903 24-Mar-2004 02:17 253,200

Sp3res.dll 5.0.2195.6994 30-Oct-2004 07:07 6,140,416

W32time.dll 5.0.2195.6824 24-Mar-2004 02:17 50,960

W32tm.exe 5.0.2195.6824 21-Sep-2003 00:32 57,104

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.

1. Click Start, and then click Search.

2. In the Search Results pane, click All files and folders under Search Companion.

3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.

4. 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.

5. 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\KB885835\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 885835 security update into the Windows installation source files.

Top of section

Windows NT 4.0 (all versions)

Prerequisites This security update requires Windows NT Server 4.0 Service Pack 6a (SP6a) or Windows NT Server 4.0 Terminal Server Edition Service Pack 6 (SP6).

The software that is listed has been tested to determine if the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support lifecycle for your product and version, visit the following Microsoft Support Lifecycle Web site.

For more information about obtaining the latest service pack, see Microsoft Knowledge Base Article 152734.

Installation Information

This security update supports the following setup switches:

/y: Perform removal (only with /m or /q )

/f: Force programs to quit during the shutdown process

/n: Do not create an Uninstall folder

/z: Do not restart when the update completes

/q: Use Quiet or Unattended mode with no user interface (this switch is a superset of /m )

/m: Use Unattended mode with a user interface

/l: List the installed hotfixes

/x: Extract the files without running Setup

Note You can combine these switches into one command. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. 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 NT Server 4.0:

Windowsnt4server-kb885835-x86-enu /q

For Windows NT Server 4.0 Terminal Server Edition:

Windowsnt4terminalserver-kb885835-x86-enu /q

To install the security update without forcing the system to restart, use the following command at a command prompt for Windows NT Server 4.0:

Windowsnt4server-kb885835-x86-enu /z

For Windows NT Server 4.0 Terminal Server Edition:

Windowsnt4terminalserver-kb885835-x86-enu /z

Restart Requirement

You must restart your system after you apply this security update.

Removal Information

To remove this security update, use the Add/Remove Programs tool in Control Panel.

System administrators can also use the Hotfix.exe utility to remove this security update. The Hotfix.exe utility is located in the %Windir%\$NTUninstallKB885835$ folder. The Hotfix.exe utility supports the following setup switches:

/y: Perform removal (only with the /m or /q switch)

/f: Force programs to quit during the shutdown process

/n: Do not create an Uninstall folder

/z: Do not restart when the installation is complete

/q: Use Quiet or Unattended mode with no user interface (this switch is a superset of the /m switch)

/m: Use Unattended mode with a user interface

/l: List the installed hotfixes

File Information

The English version of this update has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Note Date, time, file name, or size information could change during installation. See the Verifying Update Installation section for details about how to verify an installation.

Windows NT Server 4.0:

File Name Version Date Time Size Ntkrnlmp.exe 4.0.1381.7268 11-Oct-2004 14:39 958,336

Ntoskrnl.exe 4.0.1381.7268 11-Oct-2004 14:39 938,048

Windows NT Server 4.0 Terminal Server Edition:

File Name Version Date Time Size Ntkrnlmp.exe 4.0.1381.33591 11-Oct-2004 15:09 1,004,224

Ntoskrnl.exe 4.0.1381.33591 11-Oct-2004 15:09 983,104

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.

1. Click Start, and then click Search.

2. In the Search Results pane, click All files and folders under Search Companion.

3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.

4. 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.

5. 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\Windows NT\CurrentVersion\Hotfix\KB885835\File 1

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 885835 security update into the Windows installation source files.

Top of section

Top of section Acknowledgments

Microsoft thanks the following for working with us to help protect customers:

• Cesar Cerrudo of Application Security Inc. for reporting the Windows Kernel Vulnerability (CAN-2004-0893) and the LSASS Vulnerability (CAN-2004-0894).

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 (December 14, 2004): Bulletin published