Security Bulletin

Microsoft Security Bulletin MS09-023 - Moderate

Vulnerability in Windows Search Could Allow Information Disclosure (963093)

Published: June 09, 2009

Version: 1.0

General Information

Executive Summary

This security update resolves a privately reported vulnerability in Windows Search. The vulnerability could allow information disclosure if a user performs a search that returns a specially crafted file as the first result or if the user previews a specially crafted file from the search results. By default, the Windows Search component is not preinstalled on Microsoft Windows XP and Windows Server 2003. It is an optional component available for download. Windows Search installed on supported editions of Windows Vista and Windows Server 2008 is not affected by this vulnerability.

This security update is rated Moderate for Windows Search installed on all supported editions of Windows XP and Windows Server 2003. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses this vulnerability by modifying how Windows Search restricts the environment within which scripts execute. 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. The majority of customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.

For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers consider applying the security update using update management software, or by checking for updates using the Microsoft Update service.

See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.

Known Issues. Microsoft Knowledge Base Article 963093 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues.

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	Component	Maximum Security Impact	Aggregate Severity Rating	Bulletins Replaced by this Update
Windows XP Service Pack 2 and Windows XP Service Pack 3	Windows Search 4.0	Information Disclosure	Moderate	None
Windows XP Professional x64 Edition Service Pack 2	Windows Search 4.0	Information Disclosure	Moderate	None
Windows Server 2003 Service Pack 2	Windows Search 4.0	Information Disclosure	Moderate	None
Windows Server 2003 x64 Edition Service Pack 2	Windows Search 4.0	Information Disclosure	Moderate	None

Non-Affected Software

Operating System	Component
Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2	Windows Search 4.0
Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2	Windows Search 4.0
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2	Windows Search 4.0
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2	Windows Search 4.0

Frequently Asked Questions (FAQ) Related to This Security Update

Where are the file information details?
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.

I am using an older release 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 releases are affected. Other releases are past their support life cycle. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.

It should be a priority for customers who have older releases of the software to migrate to supported releases 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 releases 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

The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the June bulletin summary. For more information, see Microsoft Exploitability Index.

Vulnerability Severity Rating and Maximum Security Impact by Affected Software

Software	Script Execution in Windows Search Vulnerability - CVE-2009-0239	Aggregate Severity Rating
Windows Search 4.0 installed on Windows XP Service Pack 2	Moderate  Information Disclosure	Moderate
Windows Search 4.0 installed on Windows XP Service Pack 3	Moderate  Information Disclosure	Moderate
Windows Search 4.0 installed on Windows XP Professional x64 Edition Service Pack 2	Moderate  Information Disclosure	Moderate
Windows Search 4.0 installed on Windows Server 2003 Service Pack 2	Moderate  Information Disclosure	Moderate
Windows Search 4.0 installed on Windows Server 2003 x64 Edition Service Pack 2	Moderate  Information Disclosure	Moderate

Script Execution in Windows Search Vulnerability - CVE-2009-0239 ---------------------------------------------------------------- An information disclosure vulnerability exists in Windows Search due to the way file previews are generated. Attempts to exploit this vulnerability require user interaction. An attacker who successfully exploited this vulnerability could run a malicious HTML script that could disclose information, forward user data to a third party, or access any data on the affected systems that was accessible to the logged-on user. Note that this vulnerability would not allow an attacker to execute code or to elevate their user rights directly, but it could be used to produce information that could be used to try to further compromise the affected system. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2009-0239](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2009-0239). #### Mitigating Factors for Script Execution in Windows Search Vulnerability - CVE-2009-0239 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: - By default, the Windows Search component is not preinstalled on Microsoft Windows XP and Windows Server 2003. This is an optional component available for download. - Windows Search installed on supported editions of Windows Vista and Windows Server 2008 is not affected by this vulnerability. #### Workarounds for Script Execution in Windows Search Vulnerability - CVE-2009-0239 Microsoft has not identified any workarounds for this vulnerability. #### FAQ for Script Execution in Windows Search Vulnerability - CVE-2009-0239 **What is the scope of the vulnerability?**  This is an information disclosure vulnerability. An attacker who successfully exploited this vulnerability could run a malicious HTML script that could disclose information, forward user data to a third party, or access any data on the affected systems that was accessible to the logged-on user. Note that this vulnerability would not allow an attacker to execute code or to elevate their user rights directly, but it could be used to produce useful information that could be used to try to further compromise the affected system. **What causes the vulnerability?**  Windows Search does not properly restrict the environment within which scripts execute. **What is Windows Search?**  Windows Search allows instant search capabilities for most common file and data types such as e-mail, contacts, calendar appointments, documents, photos, multimedia, and other formats extended by third parties. These capabilities enable consumers and information workers to more efficiently find, manage, and organize the increasing amount of data common in home and enterprise environments. For more information, see [Microsoft Knowledge Base Article 940157](http://support.microsoft.com/kb/940157). **What might an attacker use the vulnerability to do?**  An attacker who successfully exploited this vulnerability could run a malicious client-side script. If this malicious script were run, it would run with special permission that would not normally be granted to a script running on an Internet web page. These permissions could allow the disclosure sensitive information, the forwarding of user data to a third party, or access to data on the affected systems that was accessible to the logged-on user. **How could an attacker exploit the vulnerability?**  This vulnerability requires a specially crafted file to be placed on the system or in an e-mail message in an indexed mail box. If a user performs a search that returns this file as the first result, arbitrary HTML script execution could occur. If the specially crafted file is not the first result, the user would need to select and preview the file in order for the exploit to occur. **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 security update addresses this vulnerability by modifying how Windows Search restricts the environment within which scripts execute. **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 systems 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.1 | |-----------------------------------------------------------------------------------------|----------| | Windows Search 4.0 installed on Windows XP Service Pack 2 and Windows XP Service Pack 3 | Yes | | Windows Search 4.0 installed on Windows XP Professional x64 Edition Service Pack 2 | Yes | | Windows Search 4.0 installed on Windows Server 2003 Service Pack 2 | Yes | | Windows Search 4.0 installed on Windows Server 2003 x64 Edition Service Pack 2 | Yes | For more information about MBSA 2.1, see [MBSA 2.1 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. 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. | Software | SMS 2.0 | SMS 2003 with SUSFP | SMS 2003 with ITMU | Configuration Manager 2007 | |-----------------------------------------------------------------------------------------|---------|---------------------|--------------------|----------------------------| | Windows Search 4.0 installed on Windows XP Service Pack 2 and Windows XP Service Pack 3 | No | No | Yes | Yes | | Windows Search 4.0 installed on Windows XP Professional x64 Edition Service Pack 2 | No | No | Yes | Yes | | Windows Search 4.0 installed on Windows Server 2003 Service Pack 2 | No | No | Yes | Yes | | Windows Search 4.0 installed on Windows Server 2003 x64 Edition Service Pack 2 | No | No | Yes | Yes | For SMS 2.0 and SMS 2003, the SMS SUS Feature Pack (SUSFP), 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 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 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. **Update Compatibility Evaluator and Application Compatibility Toolkit** Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the [Update Compatibility Evaluator](http://technet2.microsoft.com/windowsvista/en/library/4279e239-37a4-44aa-aec5-4e70fe39f9de1033.mspx?mfr=true) components included with [Application Compatibility Toolkit 5.0](https://www.microsoft.com/download/details.aspx?familyid=24da89e9-b581-47b0-b45e-492dd6da2971&displaylang=en). The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment. Security Update Deployment -------------------------- **Affected Software** For information about the specific security update for your affected software, click the appropriate link: #### 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 Windows XP Service Pack 2 and Windows XP Service Pack 3: WindowsServer2003.WindowsXP-KB963093-x86-ENU /quiet
	For Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB963093-x64-ENU /quiet
Installing without restarting	For Windows XP Service Pack 2 and Windows XP Service Pack 3: WindowsServer2003.WindowsXP-KB963093-x86-ENU /norestart
	For Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB963093-x64-ENU /norestart
Update log file	KB963093.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%\$NTUninstallKB963093$\Spuninst folder
File Information	See Microsoft Knowledge Base Article 963093
Registry Key Verification	For all supported 32-bit editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB963093
	For all supported x64-based editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB963093

Note For supported versions of Windows XP Professional x64 Edition, this security update is the same as supported versions of the Windows Server 2003 x64 Edition security update.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.

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

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**	Displays 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).

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**	Displays 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 editions of Microsoft Windows, the following steps may be different on your system. 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 edition of the operating system, or the programs that are installed on your system, 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 system 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.WindowsXP-KB963093-x86-ENU /quiet
	For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB963093-x64-ENU /quiet
Installing without restarting	For all supported 32-bit editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB963093-x86-ENU /norestart
	For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB963093-x64-ENU /norestart
Update log file	KB963093.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	Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB963093$\Spuninst folder
File Information	See Microsoft Knowledge Base Article 963093
Registry Key Verification	HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB963093

#### 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. If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see [Microsoft Knowledge Base Article 824994](http://support.microsoft.com/kb/824994). For more information about the 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). 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**	Displays 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).

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**	Displays 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 editions of Microsoft Windows, the following steps may be different on your system. 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 edition of the operating system, or the programs that are installed on your system, 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 system 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:

• Yair Amit of IBM Rational Application Security for reporting the Script Execution in Windows Search Vulnerability (CVE-2009-0239)

Microsoft Active Protections Program (MAPP)

To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.

Support

• Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support.
• 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 (June 9, 2009): Bulletin published.

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