Export (0) Print
Expand All

Microsoft Security Bulletin MS05-010 - Critical

Vulnerability in the License Logging Service Could Allow Code Execution (885834)

Published: February 08, 2005 | Updated: April 12, 2005

Version: 1.2

Issued: February 8, 2005
Updated: April 12, 2005
Version: 1.2

Summary

Who should read this document: Customers who use Microsoft Windows

Impact of Vulnerability: Remote Code Execution

Maximum Severity Rating: Critical

Recommendation: Customers should apply the update immediately.

Security Update Replacement: None

Caveats: Microsoft Knowledge Base Article 885834 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 885834.

Tested Software and Security Update Download Locations:

Affected Software:

Non-Affected Software:

  • Microsoft Windows 2000 Professional Service Pack 3 and Microsoft Windows 2000 Professional Service Pack 4
  • Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2
  • Microsoft Windows XP 64-Bit Edition Service Pack 1 (Itanium)
  • Microsoft Windows XP 64-Bit Edition Version 2003 (Itanium)
  • Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME)

The software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

General Information

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

We recommend that customers apply the update immediately.

Severity Ratings and Vulnerability Identifiers:

Vulnerability IdentifiersImpact of VulnerabilityWindows NT 4.0Windows 2000 Server Service Pack 3Windows 2000 Server Service Pack 4Windows Server 2003
License Logging Service Vulnerability - CAN-2005-0050Remote Code ExecutionCriticalCriticalImportantModerate

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.

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 Lifecycle, 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, see the Windows Operating System Product Support Lifecycle FAQ.

I am still using Windows NT Server 4.0 Service Pack 6a or Windows NT Server 4.0 Terminal Server Edition Service Pack 6 but extended security update support ended on December 31st, 2004. However, this bulletin has security updates for these operating system versions. Why is that?

Windows NT Server 4.0 Service Pack 6a and Windows NT Server 4.0 Terminal Server Edition Service Pack 6 reached the end of their life cycles on December 31, 2004. On this rare occasion, we believe that this vulnerability presents a serious risk to a broad number of customers. We have previously communicated that we reserve the right to produce updates in these situations. We determined that the best course of action to help protect customers was to release this security update. Therefore, we have decided to release a security update for this operating system version as part of this security bulletin. However, since Windows NT Server 4.0 is no longer in support, this security update will only be available on the Microsoft Download Center and will not be available through Windows Update.

We do not anticipate doing this for future vulnerabilities that may affect this operating system version, but as mentioned previously, we reserve the right to produce updates and to make these updates available when necessary. 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 whether this update is required?
Yes. MBSA will determine whether 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 by using 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 (MBSA) 1.2.1 Q&A Web site.

Can I use Systems Management Server (SMS) to determine whether this update is required?
Yes. SMS can help detect and deploy this security update. For information about SMS, visit the SMS Web site. The Security Update Inventory Tool 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

License Logging Service Vulnerability - CAN-2005-0050

A remote code execution vulnerability exists in the License Logging service that could allow an attacker who successfully exploited this vulnerability to take complete control of the affected system.

Mitigating Factors for License Logging Service Vulnerability - CAN-2005-0050:

  • On Windows Server 2003 the License Logging service is disabled by default. Typically only administrators can change the startup type of a service. An attacker would first have to change the startup type from Disabled, and then start the service to try to exploit this vulnerability.

    If the License Logging service is manually started on Windows Server 2003, attempts to exploit this vulnerability could cause in a denial of service for the affected service. This vulnerability does not allow remote code execution on Windows Server 2003.
  • On Small Business Server 2000 and on Windows Small Business Server 2003, the License Logging service is installed and running. However, by default, on Windows Small Business Server 2003 and earlier, the License Logging service communication ports are blocked from the Internet and the License Logging service is available only on the local network.
  • On Windows 2000 Server Service Pack 4 and Windows Server 2003, only authenticated users or programs can establish a connection to the License Logging service. However, this does not apply to installations of Windows 2000 Server where Service Pack 4 has been ‘slipstreamed’ into the operating system directory. For more information, see Microsoft Knowledge Base Article 896589.
  • Disabling the License Logging service helps prevent the possibility of a remote attack. Customers that have disabled this service would be at a reduced risk to attack from this vulnerability. See the “Workarounds” section for instructions that describe how to disable this service. By default, affected operating systems other than Windows Server 2003 have the License Logging service startup type set to Automatic instead of Disabled.
  • Chapter 6 of Microsoft Solution for Securing Windows 2000 Server, Hardening the Base Windows 2000 Server recommends disabling the License Logging service. Environments that comply with these guidelines could be at a reduced risk from this vulnerability.
  • 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 License Logging Service Vulnerability - CAN-2005-0050:

Microsoft has tested the following workarounds. While these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section.

  • Disable the License Logging service

    Disabling the License Logging service will help protect from remote attempts to exploit this vulnerability.

    Note Do not perform this procedure on Small Business Server 2000 or Windows Small Business Server 2003. These operating system versions require the License Logging service. These operating system versions may fail to function correctly if the License Logging service is disabled.

    You can disable the License Logging service services by following these steps:

    1. Click Start, and then click Control Panel (or point to Settings, and then click Control Panel).
    2. Double-click Administrative Tools.
    3. Double-click Services.
    4. Double-click License Logging Service.
    5. In the Startup type list, click Disabled.
    6. Click Stop, and then click OK.

    Impact of Workaround: If the License Logging service is disabled, any services that explicitly depend on the License Logging services may log an error message in the system event log. For more information, see Microsoft Knowledge Base Article 316631.

  • Use the Group Policy settings to disable License Logging Service on all affected systems that do not require this feature.
    Because the License Logging serviceis a possible attack vector, disable it by using the Group Policy settings. You can disable the startup of this service at the local, site, domain, or organizational unit level by using Group Policy object functionality in Windows 2000 domain environments or in Windows Server 2003 domain environments.

    Note Do not perform this procedure on Small Business Server 2000 or Windows Small Business Server 2003. These operating system versions require the License Logging service. These operating system versions may fail to function correctly if the License Logging service is disabled.

    Note You may also review the Windows 2000 Security Hardening Guide. This guide includes information about how to disable services.

    For more information about Group Policy, visit the following Web sites:

    Impact of Workaround: If the License Logging service is disabled, any services that explicitly depend on the License Logging service may log an error message in the system event log. For more information, see Microsoft Knowledge Base Article 316631.

  • On Windows NT Server 4.0 Service Pack 6a, Windows NT Server 4.0 Terminal Server Edition Service Pack 6, and Windows 2000 Server Service Pack 3 remove the License Logging service from the NullSessionPipes registry key:
    Affected operating systems that are earlier than Windows 2000 Server Service Pack 4 allowed anonymous connections to the License Logging service. Removing the License Logging service from the NullSessionPipes subkey registry key will help prevent attempts to exploit this vulnerability by an anonymous attacker. This workaround will not prevent attacks from authenticated users and should only be used if the License Logging service cannot be disabled. For more information about this change, see Microsoft Knowledge Base Article 815458.

    Note Using Registry Editor incorrectly can cause serious problems that may require that you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to modify the registry, view the "Change Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    Note We recommend backing up the registry before you modify it.

    1. Click Start, click Run, type "regedt32" (without the quotation marks), and then click OK.
    2. In Registry Editor, locate the following registry key:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\NullSessionPipes

    3. Edit the registry key and remove the Llsrpc value.
    4. Restart the affected system after performing these actions.

    Impact of Workaround: Anonymous connections to the License Logging service will not be allowed. There is no known impact of this change. This is the default configuration of Windows 2000 Server Service Pack 4.

  • Use a personal firewall, such as the Internet Connection Firewall , which is included with Windows Server 2003.

    By default, the Internet Connection Firewall feature in Windows Server 2003 helps protect your Internet connection by blocking unsolicited incoming traffic. We recommend that you block all unsolicited incoming communication from the Internet.

    Note Do not perform this procedure on Small Business Server 2000 or Windows Small Business Server 2003. Use the instructions provided in the “Run the Configure E-mail and Internet Connection Wizard” workaround instead of this procedure.

    To enable the Internet Connection Firewall feature by using the Network Setup Wizard, follow these steps:

    1. Click Start, and then click Control Panel.
    2. 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:

    1. Click Start, and then click Control Panel.
    2. In the default Category View, click Networking and Internet Connections, and then click Network Connections.
    3. Right-click the connection on which you want to enable Internet Connection Firewall, and then click Properties.
    4. Click the Advanced tab.
    5. 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 certain programs and services to communicate through the firewall, click Settings on the Advanced tab, and then select the programs, the protocols, and the services that are required.

  • Block TCP ports 139 and 445 at the firewall:

    These ports are used to initiate a connection with the License Logging service using named pipe connections. Blocking them at the firewall will help prevent systems that are behind that firewall from attempts to exploit this vulnerability. We recommend that you block all unsolicited inbound communication from the Internet to help prevent attacks that may use other ports. For more information about ports, visit the following Web site.

  • Run the Configure E-mail and Internet Connection Wizard

    Small Business Server 2000 and Windows Small Business Server 2003 include firewall technology that helps protect your Internet connection by blocking unsolicited incoming traffic. The firewall technology in Small Business Server 2000 and Windows Small Business Server 2003 is configured automatically when you run the Configure E-mail and Internet Connection Wizard.

    To configure the firewall technology using the Configure E-mail and Internet Connection Wizard, follow these steps:

    1. Click Start, and then click Server Management.
    2. In the console tree, click Internet and E-mail

    In the details pane, click Connect to the Internet.

    1. Accept the default values in the wizard.
  • 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 about how to apply filters is available in Microsoft Knowledge Base Article 313190 and Microsoft Knowledge Base Article 813878.

FAQ for License Logging Service Vulnerability - CAN-2005-0050:

What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could remotely 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.

On Windows Server 2003, the most likely attack scenario is a denial of service. An attacker who successfully exploited this vulnerability could cause the License Logging service to fail on Windows Server 2003. Restarting the License Logging service allows the service to function correctly. However, the License Logging service could remain vulnerable to another denial of service attack.

On Windows 2000 Server Service Pack 4 and Windows Server 2003, only authenticated users or programs can establish a connection to the License Logging service.

What causes the vulnerability?
An unchecked buffer in the License Logging service.

What is the License Logging service?
The License Logging service is a tool that was originally designed to help customers manage licenses for the Microsoft server products that are licensed in the Server Client Access License (CAL) model. License Logging service is one of the services used by Windows Small Business Server 2003 or earlier to manage CALs. By default, the License Logging service is disabled in Windows Server 2003. The License Logging service will not be included in future versions of the Windows operating system. For more information about the License Logging service, see Microsoft Knowledge Base Article 842196.

How do I know if I use the License Logging service on my server?

The License Logging service is not available on Windows 2000 Professional or Windows XP. By default, the License Logging service is installed and running on Windows NT Server 4.0, on Windows NT Server 4.0 Terminal Server Edition, and on Windows 2000 Server. By default, the License Logging service is installed but not running on Windows Server 2003. By default, the License Logging service is installed and running on Small Business Server 2000 and on Windows Small Business Server 2003. You can determine if the License Logging service is installed by following this procedure. These steps apply only to Windows 2000 and later versions. For Windows NT 4.0, follow the procedure that is included in the product documentation.

To verify the License Logging service:

  1. Click Start, click Programs, click Administrative Tools, and then click Services.
  2. Verify that the License Logging service is present.
  3. If the License Logging service is running, follow the instructions in the “Workarounds” section of this security bulletin to disable the service.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system. The vulnerability, if exploited, could allow an attacker to cause the License Logging service on Windows Server 2003 to stop responding to all requests.

Who could exploit the vulnerability?
On Windows NT Server 4.0 Service Pack 6a, Windows NT Server 4.0 Terminal Server Edition Service Pack 6, and Windows 2000 Server Service Pack 3 any anonymous user who could establish a connection with an affected system by using the affected ports could attempt to exploit this vulnerability.

On Windows 2000 Server Service Pack 4 and Windows Server 2003, only authenticated users or programs can establish a connection to the License Logging service. However, this does not apply to installations of Windows 2000 Server where Service Pack 4 has been ‘slipstreamed’ into the operating system directory. For more information, see Microsoft Knowledge Base Article 896589.

On Small Business Server 2000 running on Windows 2000 Server Service Pack 3, any anonymous user who could establish a connection with an affected system by using the affected ports could attempt to exploit this vulnerability. On Windows Small Business Server 2003 and Small Business Server 2000 running on Windows 2000 Server Service Pack 4, only authenticated users or programs on the local network can establish a connection to the License Logging service.

How could an attacker exploit the vulnerability?
An attacker could attempt to exploit this vulnerability by creating a specially-crafted network message and by sending the message to the affected system. On Windows Server 2003, receipt of such a message could cause the service to fail causing a denial of service.

What systems are primarily at risk from the vulnerability?
Windows NT Server 4.0 Service Pack 6a, Windows NT Server 4.0 Terminal Server Edition Service Pack 6, and Windows 2000 Server are primarily at risk from this vulnerability.

Windows 2000 Professional and Windows XP are not at risk from this vulnerability. Windows Server 2003 is impacted at a lower severity rating partly because the License Logging service startup type is set to Disabled. An attacker would first have to change the setting from Disabled to Manual or Automatic, and then start the service to attempt to remotely exploit this vulnerability. Typically, only administrators can change the startup type of a service. Operating systems other than Windows Server 2003 have the License Logging service set to a startup type of Automatic instead of Disabled. After the License Logging service is started, the affected system could be vulnerable to a remote attack. To help prevent this, see the “Workarounds” section for instructions that explain how you can disable the License Logging service.

Could the vulnerability be exploited over the Internet?
Yes. An attacker could try 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 about 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 the License Logging 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 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.

Affected Software:

For information about the specific security update for your affected software, click the appropriate link:

Windows Server 2003 (all versions)

Prerequisites
This security update requires 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 has completed

/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 the Setup program

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 Windows Server 2003:

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

For information about how to deploy this security update by using 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 being used, this update will require a restart. If this behavior 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%\$NTUninstallKB885834$\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 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 NameVersionDateTimeSizeFolder
Llssrv.exe5.2.3790.24813-Jan-200503:2688,576RTMGDR
Llssrv.exe5.2.3790.24813-Jan-200503:2288,576RTMQFE

Windows Server 2003, Enterprise Edition for Itanium-based Systems and Windows Server 2003, Datacenter Edition for Itanium-based Systems:

File NameVersionDateTimeSizeCPUFolder
Llssrv.exe5.2.3790.24813-Jan-200503:26301,568IA-64RTMGDR
Wllssrv.exe5.2.3790.24813-Jan-200503:2688,576x86RTMGDR\WOW
Llssrv.exe5.2.3790.24813-Jan-200503:26301,568IA-64RTMQFE
Wllssrv.exe5.2.3790.24813-Jan-200503:2288,576x86RTMQFE\WOW

Note When you install this security update on Windows Server 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, 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 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. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.

  • File Version Verification

    Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

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

Windows 2000 Server (all versions)

Prerequisites
For Windows 2000, this security update requires Service Pack 3 (SP3) or Service Pack 4 (SP4). For Small Business Server 2000, this security update requires Small Business Server 2000 Service Pack 1a or Small Business Server 2000 running on Windows 2000 Server Service Pack 4.

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

For more information about how to obtain the latest service pack, see Microsoft Knowledge Base Article 260910.

Inclusion in Future Service Packs:
The update for this issue 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 has completed

/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 the Setup program

Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for Windows 2000 Service Pack 3 and Windows 2000 Service Pack 4:

Windows2000-kb885834-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-kb885834-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%\$NTUninstallKB885834$\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 security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Windows 2000 Service Pack 3, Windows 2000 Service Pack 4, and Small Business Server 2000:

File NameVersionDateTimeSize
Llsrpc.dll5.0.2195.660119-Jun-200320:0548,912
Llssrv.exe5.0.2195.702113-Jan-200517:1985,264
Ole32.dll5.0.2195.702118-Jan-200504:47957,200
Rpcrt4.dll5.0.2195.690411-Mar-200421:29449,808
Rpcss.dll5.0.2195.702118-Jan-200504:47212,240

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. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.

  • File Version Verification

    Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

    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 the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

  • Registry Key Verification

    You may also be able to verify the files that this security update has installed by reviewing the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB885834\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 885834 security update into the Windows installation source files.

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 whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

For more information about 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 finishes

   /q: Use Quiet or Unattended mode without a 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-kb885834-x86-enu /q

For Windows NT Server 4.0 Terminal Server Edition:

Windowsnt4terminalserver-kb885834-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-kb885834-x86-enu /z

For Windows NT Server 4.0 Terminal Server Edition:

Windowsnt4terminalserver-kb885834-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%\$NTUninstallKB885834$ 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 finishes

/q: Use Quiet or Unattended mode without a 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 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 NT Server 4.0:

File NameVersionDateTimeSize
Llssrv.exe4.0.1381.734517-Jan-200511:36134,928

Windows NT Server 4.0 Terminal Server Edition:

File NameVersionDateTimeSize
Llssrv.exe4.0.1381.3363217-Jan-200511:53134,928

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. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.

  • File Version Verification

    Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

    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 the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

  • Registry Key Verification

    You may also be able to verify the files that this security update has installed by reviewing the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB885834\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 885834 security update into the Windows installation source files.

Other Information

Acknowledgments

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

  • Kostya Kortchinsky from CERT RENATER for reporting the License Logging Service Vulnerability (CAN-2005-0050).

Obtaining Other Security Updates:

Updates for other security issues are available at the following locations:

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:

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 by using 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 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 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, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.

Disclaimer:

The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

Revisions:

  • V1.0 (February 8, 2005): Bulletin published
  • V1.1 (February 23, 2005): Bulletin updated to reflect a revised “Security Update Information” section for Windows Server 2003Microsoft Knowledge Base Article 896589
  • V1.2 (April 12, 2005): Bulletin updated to reflect a revised “Mitigating Factors” section for Windows 2000 Server Service Pack 4. This update documents a known issue with a mitigating factor and the availability of Microsoft Knowledge Base Article 896589.

Built at 2014-04-18T13:49:36Z-07:00

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft