• 30 minutes to read

Security Bulletin

Microsoft Security Bulletin MS08-002 - Important

Vulnerability in LSASS Could Allow Local Elevation of Privilege (943485)

Published: January 08, 2008

Version: 1.0

General Information

Executive Summary

This important update resolves a privately reported vulnerability in Microsoft Windows Local Security Authority Subsystem Service (LSASS). The vulnerability could allow an attacker to run arbitrary code with elevated privileges. 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.

This is an important security update for all supported editions of Windows 2000, Windows XP, and Windows Server 2003. For more information, see the subsection, Affected and Non-Affected Software, in this section.

This security update addresses the vulnerability by validating parameters passed to LSASS APIs. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

Recommendation.  Microsoft recommends that customers apply the update at the earliest opportunity.

Known Issues. None

Affected and Non-Affected Software

The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.

Affected Software

Operating System Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by this Update
Microsoft Windows 2000 Service Pack 4 Local Elevation of privilege Important None
Windows XP Service Pack 2 Local Elevation of privilege Important None
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Local Elevation of privilege Important None
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Local Elevation of privilege Important None
Windows Server 2003 x64 Edition and Windows 2003 Server x64 Edition Service Pack 2 Local Elevation of privilege Important None
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium based Systems Local Elevation of privilege Important None

Non-Affected Software

Operating System
Windows Vista
Windows Vista x64 Edition

I am using an older version of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which versions or editions are affected. Other versions or editions are past their support life cycle. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.

It should be a priority for customers who have older versions or editions of the software to migrate to supported versions or editions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services.

Customers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit Microsoft Worldwide Information, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.

Vulnerability Information

Severity Ratings and Vulnerability Identifiers

Affected Software LSASS Bypass Vulnerability - CVE-2007-5352 Aggregate Severity Rating
Microsoft Windows 2000 Service Pack 4 Important 
Local Elevation of Privilege		 Important
Windows XP Service Pack 2 Important 
Local Elevation of Privilege		 Important
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Important 
Local Elevation of Privilege		 Important
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Important 
Local Elevation of Privilege		 Important
Windows Server 2003 x64 Edition and Windows 2003 Server x64 Edition Service Pack 2 Important 
Local Elevation of Privilege		 Important
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium based Systems Important 
Local Elevation of Privilege		 Important
LSASS Bypass Vulnerability - CVE-2007-5352 ------------------------------------------ An elevation of privilege vulnerability exists in the Microsoft Windows Local Security Authority Subsystem Service (LSASS) due to its improper handling of local procedure call (LPC) requests. The vulnerability could allow an attacker to run code with elevated privileges. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2007-5352](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2007-5352). #### Mitigating Factors for LSASS Bypass Vulnerability - CVE-2007-5352 Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation: - An attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability. The vulnerability could not be exploited remotely or by anonymous users. #### Workarounds for LSASS Bypass Vulnerability - CVE-2007-5352 Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality: - Microsoft has not identified any workarounds for this vulnerability. #### FAQ for LSASS Bypass Vulnerability - CVE-2007-5352 **What is the scope of the vulnerability?**  An elevation of privilege vulnerability exists in the Local Security Authority Subsystem Service (LSASS). An attacker who successfully exploited this vulnerability could run code with elevated privileges. An attacker could then take complete control of an affected system. **What causes the vulnerability?**  The LSASS process does not properly handle specially crafted LPC requests. When the LSASS process receives a specially crafted LCP request it is possible for an attacker to execute code with local system privileges. **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 gain complete control over the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full administrative rights. **How could an attacker exploit the vulnerability?**  To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and gain complete control over the affected system. **What systems are primarily at risk from the vulnerability?**  Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this. **What does the update do?**  The update removes the vulnerability by validating parameters that are passed to the LSASS API, preventing access to invalid addresses. **When this security bulletin was issued, had this vulnerability been publicly disclosed?**  No. Microsoft received information about this vulnerability through responsible disclosure. **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. ### Update Information Detection and Deployment Tools and Guidance ------------------------------------------- Manage the software and security updates you need to deploy to the servers, desktop, and mobile computers in your organization. For more information see the [TechNet Update Management Center](http://go.microsoft.com/fwlink/?linkid=69903). The [Microsoft TechNet Security Web site](http://go.microsoft.com/fwlink/?linkid=21132) provides additional information about security in Microsoft products. Security updates are available from [Microsoft Update](http://go.microsoft.com/fwlink/?linkid=40747), [Windows Update](http://go.microsoft.com/fwlink/?linkid=21130), and [Office Update](http://go.microsoft.com/fwlink/?linkid=21135). Security updates are also available from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?linkid=21129). You can find them most easily by doing a keyword search for "security update." Finally, security updates can be downloaded from the [Microsoft Update Catalog](http://go.microsoft.com/fwlink/?linkid=96155). The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, “MS07-036”), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the [Microsoft Update Catalog FAQ](http://go.microsoft.com/fwlink/?linkid=97900). **Detection and Deployment Guidance** Microsoft has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), and the Extended Security Update Inventory Tool. For more information, see [Microsoft Knowledge Base Article 910723](http://support.microsoft.com/kb/910723). **Microsoft Baseline Security Analyzer** Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit [Microsoft Baseline Security Analyzer](http://www.microsoft.com/technet/security/tools/mbsahome.mspx). The following table provides the MBSA detection summary for this security update. | Software | MBSA 2.0.1 | |-------------------------------------------------------------------------------------------------------------------|------------| | Microsoft Windows 2000 Service Pack 4 | Yes | | Windows XP Service Pack 2 | Yes | | Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Yes | | Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Yes | | Windows Server 2003 x64 Edition and Windows 2003 Server x64 Edition Service Pack 2 | Yes | | Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium based Systems | Yes | For more information about MBSA 2.0.1, see [MBSA 2.0 Frequently Asked Questions](http://www.microsoft.com/technet/security/tools/mbsa2/qa.mspx). **Windows Server Update Services** By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 to Windows 2000 and later operating systems. For more information about how to deploy this security update using Windows Server Update Services, visit the [Windows Server Update Services Web site](http://go.microsoft.com/fwlink/?linkid=50120). **Systems Management Server** The following table provides the SMS detection and deployment summary for this security update. | Product | SMS 2.0 | SMS 2003 | SCCM 2007 | |-------------------------------------------------------------------------------------------------------------------|---------|----------|-----------| | Microsoft Windows 2000 Service Pack 4 | Yes | Yes | Yes | | Windows XP Service Pack 2 | Yes | Yes | Yes | | Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | No | Yes | Yes | | Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Yes | Yes | Yes | | Windows Server 2003 x64 Edition and Windows 2003 Server x64 Edition Service Pack 2 | No | Yes | Yes | | Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium based Systems | No | Yes | Yes | For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. See also [Downloads for Systems Management Server 2.0](http://technet.microsoft.com/en-us/sms/bb676799.aspx). For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by [Microsoft Update](http://update.microsoft.com/microsoftupdate) and that are supported by [Windows Server Update Services](http://go.microsoft.com/fwlink/?linkid=50120). For more information about the SMS 2003 ITMU, see [SMS 2003 Inventory Tool for Microsoft Updates](http://technet.microsoft.com/en-us/sms/bb676783.aspx). SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about the Office Inventory Tool and other scanning tools, see [SMS 2003 Software Update Scanning Tools](http://technet.microsoft.com/en-us/sms/bb676786.aspx). See also [Downloads for Systems Management Server 2003](http://technet.microsoft.com/en-us/sms/bb676766.aspx). System Center Configuration Manager (SCCM) 2007 uses WSUS 3.0 for detection of updates. For more information about SCCM 2007 Software Update Management, visit [System Center Configuration Manager 2007](http://technet.microsoft.com/en-us/library/bb735860.aspx). For more information about SMS, visit the [SMS Web site](http://go.microsoft.com/fwlink/?linkid=21158). For more detailed information, see [Microsoft Knowledge Base Article 910723](http://support.microsoft.com/kb/910723): Summary list of monthly detection and deployment guidance articles. Security Update Information --------------------------- **Affected Software** For information about the specific security update for your affected software, click the appropriate link: #### Windows 2000 (all editions) **Reference Table** The following table contains the security update information for this software. You can find additional information in the subsection, **Deployment Information**, in this section.

Inclusion in Future Service Packs The update for this issue may be included in a future update rollup
Deployment
Installing without user intervention Windows 2000 Service Pack 4:
Windows2000-kb943485-x86-enu /quiet
Installing without restarting Windows 2000 Service Pack 4:
Windows2000-kb943485-x86-enu /norestart
Update log file Windows 2000 Service Pack 4:
KB943485.log
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required Yes, you must restart your system after you apply this security update
Hotpatching Not applicable
Removal Information Windows 2000 Service Pack 4:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB943485$\Spuninst folder
File Information See the next subsection, File Information, for the full file manifest.
Registry Key Verification For Windows 2000 Service Pack 4:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB943485\Filelist

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.

For all supported editions of Windows 2000:

File Name Version Date Time Size
lsasrv.dll 5.0.2195.7147 15-Oct-2007 23:04 513,808
sp3res.dll 5.0.2195.7136 27-May-2007 19:26 6,258,688

Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

Deployment Information

Installing the Update

When you install this security update, 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.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch Description
**/help** Displays the command-line options
Setup Modes
**/passive** Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
**/quiet** Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
**/norestart** Does not restart when installation has completed
**/forcerestart** Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
**/warnrestart\[:x\]** Presents a dialog box with a timer warning the user that the computer will restart in *x* seconds. (The default setting is 30 seconds.) Intended for use with the **/quiet** switch or the **/passive** switch.
**/promptrestart** Display a dialog box prompting the local user to allow a restart
Special Options
**/overwriteoem** Overwrites OEM files without prompting
**/nobackup** Does not back up files needed for uninstall
**/forceappsclose** Forces other programs to close when the computer shuts down
**/log:path** Allows the redirection of installation log files
**/extract\[:path\]** Extracts files without starting the Setup program
**/ER** Enables extended error reporting
**/verbose** Enables verbose logging. During installation, creates %Windir%\\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.
**Note** You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see [Microsoft Knowledge Base Article 262841](http://support.microsoft.com/kb/262841). For more information about the Update.exe installer, visit the [Microsoft TechNet Web site](http://go.microsoft.com/fwlink/?linkid=38951). For more information about the terminology that appears in this bulletin, such as *hotfix*, see [Microsoft Knowledge Base Article 824684](http://support.microsoft.com/kb/824684).

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
Switch Description
**/help** Displays the command-line options
Setup Modes
**/passive** Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
**/quiet** Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
**/norestart** Does not restart when installation has completed
**/forcerestart** Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
**/warnrestart\[:x\]** Presents a dialog box with a timer warning the user that the computer will restart in *x* seconds. (The default setting is 30 seconds.) Intended for use with the **/quiet** switch or the **/passive** switch.
**/promptrestart** Display a dialog box prompting the local user to allow a restart
Special Options
**/forceappsclose** Forces other programs to close when the computer shuts down
**/log:path** Allows the redirection of installation log files
**Verifying That the Update Has Been Applied**

  • Microsoft Baseline Security Analyzer

    To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification

    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 registry keys listed in the Reference Table in this section.

    These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Windows XP (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention For all supported 32-bit editions of Windows XP:
Windowsxp-kb943485-x86-enu /quiet

For all supported x64-based Editions of Windows XP:
Windowsserver-2003.Windows XP-KB943485-x64-ENU.exe /quiet
Installing without restarting For all supported 32-bit editions of Windows XP:
WindowsXP-KB943485-x86-ENU.exe /norestart

For all supported x64-based editions of Windows XP:
Windowsserver-2003.Windows XP-KB943485-x64-ENU.exe /norestart
Update log file KB943485.log
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required Yes, you must restart your system after you apply this security update
Hotpatching Not applicable
Removal Information Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB943485$\Spuninst folder
File Information See the next subsection, File Information, for the full file manifest.
Registry Key Verification For all supported 32-bit editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB943485\Filelist For all supported x64-based editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB943485\Filelist

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.

For all supported 32-bit editions of Windows XP:

File Name Version Date Time Size Folder
lsasrv.dll 5.1.2600.3249 06-Nov-2007 19:56 721,920 SP2GDR
lsasrv.dll 5.1.2600.3249 06-Nov-2007 20:20 727,040 SP2QFE

For all supported x64-based editions of Windows XP:

File Name Version Date Time Size CPU Folder
lsasrv.dll 5.2.3790.3041 09-Nov-2007 07:16 1,567,744 x64 SP1GDR
lsasrv.dll 5.2.3790.3041 09-Nov-2007 07:31 1,566,720 x64 SP1QFE
lsasrv.dll 5.2.3790.4186 09-Nov-2007 07:12 1,566,208 x64 SP2GDR
lsasrv.dll 5.2.3790.4186 09-Nov-2007 07:19 1,567,232 x64 SP2QFE

Note For a complete list of supported editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

Deployment Information

Installing the Update

When you install this security update, 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.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch Description
**/help** Displays the command-line options
Setup Modes
**/passive** Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
**/quiet** Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
**/norestart** Does not restart when installation has completed
**/forcerestart** Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
**/warnrestart\[:x\]** Presents a dialog box with a timer warning the user that the computer will restart in *x* seconds. (The default setting is 30 seconds.) Intended for use with the **/quiet** switch or the **/passive** switch.
**/promptrestart** Display a dialog box prompting the local user to allow a restart
Special Options
**/overwriteoem** Overwrites OEM files without prompting
**/nobackup** Does not back up files needed for uninstall
**/forceappsclose** Forces other programs to close when the computer shuts down
**/log:path** Allows the redirection of installation log files
**/integrate:path** Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
**/extract\[:path\]** Extracts files without starting the Setup program
**/ER** Enables extended error reporting
**/verbose** Enables verbose logging. During installation, creates %Windir%\\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.
**Note** You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see [Microsoft Knowledge Base Article 262841](http://support.microsoft.com/kb/262841). For more information about the Update.exe installer, visit the [Microsoft TechNet Web site](http://go.microsoft.com/fwlink/?linkid=38951).

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
Switch Description
**/help** Displays the command-line options
Setup Modes
**/passive** Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
**/quiet** Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
**/norestart** Does not restart when installation has completed
**/forcerestart** Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
**/warnrestart\[:x\]** Presents a dialog box with a timer warning the user that the computer will restart in *x* seconds. (The default setting is 30 seconds.) Intended for use with the **/quiet** switch or the **/passive** switch.
**/promptrestart** Display a dialog box prompting the local user to allow a restart
Special Options
**/forceappsclose** Forces other programs to close when the computer shuts down
**/log:path** Allows the redirection of installation log files
**Verifying That the Update Has Been Applied**

  • Microsoft Baseline Security Analyzer

    To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification

    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 registry keys listed in the Reference Table in this section.

    These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Windows Server 2003 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention For all supported 32-bit editions of Windows Server 2003:
Windowsserver2003-kb943485-x86-enu /quiet

For all supported x64-based editions of Windows Server 2003:
Windowsserver2003.WindowsXP-kb943485-x64-enu /quiet

For all supported Itanium-based editions of Windows Server 2003:
Windowsserver2003-kb943485-ia64-enu /quiet
Installing without restarting For all supported 32-bit editions of Windows Server 2003:
Windowsserver2003-kb943485-x86-enu /norestart

For all supported x64-based editions of Windows Server 2003:
Windowsserver2003.WindowsXP-kb943485-x64-enu / norestart

For all supported Itanium-based editions of Windows Server 2003:
Windowsserver2003-kb943485-ia64-enu / norestart
Update log file KB943485.log
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required Yes, you must restart your system after you apply this security update
Hotpatching This security update does not support HotPatching. For more information about HotPatching see Microsoft Knowledge Base Article 897341.
Removal Information For all supported 32-bit editions, x64-based editions, and Itanium-based editions of Windows Server 2003:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility, located in the %Windir%\$NTUninstallKB943485$\Spuninst folder
File Information See the next subsection, File Information, for the full file manifest.
Registry Key Verification For all supported 32-bit editions, Itanium-based editions, and x64-based editions of Windows Server 2003:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB943485\Filelist

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.

For all supported 32-bit editions of Windows Server 2003:

File Name Version Date Time Size Folder
lsasrv.dll 5.2.3790.3041 08-Nov-2007 06:18 822,784 SP1GDR
lsasrv.dll 5.2.3790.3041 08-Nov-2007 05:29 822,784 SP1QFE
lsasrv.dll 5.2.3790.4186 08-Nov-2007 07:45 815,616 SP2GDR
lsasrv.dll 5.2.3790.4186 08-Nov-2007 07:39 815,616 SP2QFE

For all supported Itanium-based editions of Windows Server 2003:

File Name Version Date Time Size CPU Folder
lsasrv.dll 5.2.3790.3041 09-Nov-2007 07:02 2,163,200 IA-64 SP1GDR
lsasrv.dll 5.2.3790.3041 09-Nov-2007 07:07 2,162,688 IA-64 SP1QFE
lsasrv.dll 5.2.3790.4186 09-Nov-2007 07:07 2,163,712 IA-64 SP2GDR
lsasrv.dll 5.2.3790.4186 09-Nov-2007 07:02 2,164,736 IA-64 SP2QFE

For all supported x64-based editions of Windows Server 2003:

File Name Version Date Time Size CPU Folder
lsasrv.dll 5.2.3790.3041 09-Nov-2007 07:16 1,567,744 x64 SP1GDR
lsasrv.dll 5.2.3790.3041 09-Nov-2007 07:31 1,566,720 x64 SP1QFE
lsasrv.dll 5.2.3790.4186 09-Nov-2007 07:12 1,566,208 x64 SP2GDR
lsasrv.dll 5.2.3790.4186 09-Nov-2007 07:19 1,567,232 x64 SP2QFE

Note For a complete list of supported editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

Deployment Information

Installing the Update

When you install this security update, 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.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch Description
**/help** Displays the command-line options
Setup Modes
**/passive** Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
**/quiet** Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
**/norestart** Does not restart when installation has completed
**/forcerestart** Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
**/warnrestart\[:x\]** Presents a dialog box with a timer warning the user that the computer will restart in *x* seconds. (The default setting is 30 seconds.) Intended for use with the **/quiet** switch or the **/passive** switch.
**/promptrestart** Display a dialog box prompting the local user to allow a restart
Special Options
**/overwriteoem** Overwrites OEM files without prompting
**/nobackup** Does not back up files needed for uninstall
**/forceappsclose** Forces other programs to close when the computer shuts down
**/log:path** Allows the redirection of installation log files
**/integrate:path** Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
**/extract\[:path\]** Extracts files without starting the Setup program
**/ER** Enables extended error reporting
**/verbose** Enables verbose logging. During installation, creates %Windir%\\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.
**Note** You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see [Microsoft Knowledge Base Article 262841](http://support.microsoft.com/kb/262841). For more information about the Update.exe installer, visit the [Microsoft TechNet Web site](http://go.microsoft.com/fwlink/?linkid=38951).

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
Switch Description
**/help** Displays the command-line options
Setup Modes
**/passive** Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
**/quiet** Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
**/norestart** Does not restart when installation has completed
**/forcerestart** Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
**/warnrestart\[:x\]** Presents a dialog box with a timer warning the user that the computer will restart in *x* seconds. (The default setting is 30 seconds.) Intended for use with the **/quiet** switch or the **/passive** switch.
**/promptrestart** Display a dialog box prompting the local user to allow a restart
Special Options
**/forceappsclose** Forces other programs to close when the computer shuts down
**/log:path** Allows the redirection of installation log files
**Verifying that the Update Has Been Applied**

  • Microsoft Baseline Security Analyzer

    To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification

    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 registry keys listed in the Reference Table in this section.

    These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Other Information

Acknowledgments

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

  • Thomas Garnier of SkyRecon for reporting the LSASS Bypass Vulnerability (CVE-2007-5352).

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.

Disclaimer

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

Revisions

  • V1.0 (January 8, 2008): Bulletin published.

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