Microsoft Security Bulletin MS09-070 - Important

General Information

Executive Summary

This security update resolves two privately reported vulnerabilities in Microsoft Windows. The more severe of these vulnerabilities could allow remote code execution if an attacker sent a specially crafted HTTP request to an ADFS-enabled Web server. An attacker would need to be an authenticated user in order to exploit either of these vulnerabilities.

This security update is rated Important for affected releases of Windows Server 2003, Windows Server 2003 x64 Edition, Windows Server 2008, and Windows Server 2008 x64 Edition. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerabilities by correcting the validation that ADFS-enabled Web servers apply to request headers submitted by a Web client. For more information about the vulnerabilities, 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 apply the update at the earliest opportunity 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 971726 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.

*Server Core installation not affected. The vulnerabilities addressed by this update do not affect supported editions of Windows Server 2008 as indicated, when installed using the Server Core installation option. For more information on this installation option, see the MSDN article, Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.

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.

What are the known issues that customers may experience when installing this security update?Microsoft Knowledge Base Article 971726 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues.

Why does this update address several reported security vulnerabilities?
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers need to install this update only.

What is Active Directory Federation Services?
Active Directory Federation Services (ADFS) is based on the emerging, industry-supported Web Services Architecture, which is defined in WS-* specifications. ADFS helps you use single sign-on (SSO) to authenticate users to multiple, related Web applications throughout the duration of a single online session. ADFS accomplishes this by securely sharing digital identity and entitlement rights across security and enterprise boundaries.

How can I verify whether ADFS is installed on my server?
To verify that ADFS is installed on your server, click Start, click Control Panel, click Add/Remove Programs, double-click Windows Components, and then look for Federation Services as an installed component.

What is Windows Server 2003 R2?
Windows Server 2003 R2 extends the Windows Server 2003 operating system, providing a more efficient way to manage and control access to local and remote resources while easily integrating into your existing Windows Server 2003 environment. Windows Server 2003 R2 provides a scalable, security-enhanced Web platform, seamless interoperability with UNIX-based systems, and enables new scenarios including simplified branch server management, improved identity and access management, and more efficient storage management. Windows Server 2003 R2 Datacenter Edition and Windows Server 2003 R2 Enterprise Edition also deliver dynamic new licensing that allows customers to get even more value out of server virtualization.

The specifications for a Web Services Architecture that is based on industry standards such as Simple Object Access Protocol (SOAP); XML; Web Service Description Language (WSDL); and Universal Description, Discovery, and Integration (UDDI). WS-* provides a foundation for delivering complete, interoperable business solutions for the extended enterprise, including the ability to manage federated identity and security.

The Web services model is based on the idea that enterprise systems are written in different languages, with different programming models, which run on and are accessed from many different types of devices. Web services are a means of building distributed systems that can connect and interact with one another easily and efficiently across the Internet, regardless of what language they are written in or what platform they run on.

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. For more information about the product lifecycle, visit the Microsoft Support Lifecycle Web site.

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. To determine the support lifecycle for your software release, see Select a Product for Lifecycle Information. For more information about service packs for these software releases, see Lifecycle Supported Service Packs.

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 the Microsoft Worldwide Information Web site, select the country in the Contact Information list, 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 Microsoft Support Lifecycle Policy 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 December bulletin summary. For more information, see Microsoft Exploitability Index.

**\*Server Core installation not affected.** The vulnerabilities addressed by this update do not affect supported editions of Windows Server 2008 when installed using the Server Core installation option. For more information on this installation option, see the MSDN article, [Server Core](http://msdn.microsoft.com/en-us/library/ms723891(vs.85).aspx). Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see [Compare Server Core Installation Options](http://www.microsoft.com/windowsserver2008/en/us/compare-core-installation.aspx).
[1]Only affected when updated with Windows Server 2003 R2, which deploys Active Directory Federation Services.
[2]Only affected when updated with Windows Server 2003 R2 x64 Edition, which deploys Active Directory Federation Services.
Single Sign On Spoofing in ADFS Vulnerability - CVE-2009-2508
-------------------------------------------------------------
A spoofing vulnerability in Active Directory Federation Services could allow an attacker to impersonate an authenticated user if the attacker has access to a workstation and Web browser recently used by the targeted user to access a Web site that offers single sign on.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2009-2508](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2009-2508).
#### Mitigating Factors for Single Sign On Spoofing in ADFS Vulnerability - CVE-2009-2508
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 cannot choose whom to impersonate. An attacker can only impersonate someone whose authentication token the attacker has been able to obtain, for example, from an Internet kiosk.
- An attack is only possible before the session times out on the server. By default, sessions remain open for 600 minutes on the server. If an attacker tried to re-use a victim's authentication token after that time-out period has elapsed, the attack would fail.
- An attacker must have access to the authentication token used by the previous user on that terminal. In the case of an HTTPS-enabled server, that authentication token will have been protected in transit, and an attacker must have access to the victim's computer (for example, an Internet kiosk) to exploit the vulnerability. On an Internet kiosk, the user might sign in to an ADFS Single Sign-On (SSO) Web application, then sign off the application. An attacker could then use that computer to access the Web application as the previous user, even though the user has logged out.
#### Workarounds for Single Sign On Spoofing in ADFS Vulnerability - CVE-2009-2508
Microsoft has not identified any workarounds for this vulnerability.
#### FAQ for Single Sign On Spoofing in ADFS Vulnerability - CVE-2009-2508
**What is the scope of the vulnerability?**
This is a spoofing vulnerability. An attacker who successfully exploited this vulnerability could impersonate another user, allowing the attacker to gain access as the targeted user to a Web site that uses the single sign-on functionality of Active Directory Federation Services (ADFS).
**What causes the vulnerability?**
This vulnerability exists because ADFS lacks sufficient session management validation.
**What might an attacker use the vulnerability to do?**
On systems with shared access, such as Internet kiosks, an attacker who successfully exploited this vulnerability could access resources belonging to another, previously authenticated, user. This attack could only be executed within the session timeout configured by the ADFS administrator which is by default configured to 600 minutes.
**How could an attacker exploit the vulnerability?**
An attacker could exploit this vulnerability by accessing specific data from the browser's cache and reusing it to authenticate against the Web application implementing ADFS single sign-on (SSO). After the session times out on the server, ADFS will disable the authenticated session on the server side and will no longer allow the attacker to re-use these credentials.
**What systems are primarily at risk from the vulnerability?**
Web servers using ADFS for single sign-on purposes are affected by this vulnerability. This vulnerability does not directly affect client systems.
**What does the update do?**
The update addresses the vulnerability by properly discarding authentication credentials when the user logs off the network.
**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 when this security bulletin was originally issued.
Remote Code Execution in ADFS Vulnerability - CVE-2009-2509
-----------------------------------------------------------
A remote code execution vulnerability exists in implementations of Active Directory Federation Services (ADFS). The vulnerability is due to incorrect validation of request headers when an authenticated user connects to an ADFS enabled Web server. An attacker who successfully exploited this vulnerability could take complete control of an affected system.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2009-2509](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2009-2509).
#### Mitigating Factors for Remote Code Execution in ADFS Vulnerability - CVE-2009-2509
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:
- The attacker must have valid logon credentials to the vulnerable server. An attack can only be carried out after authenticating successfully to the server that supports ADFS.
#### Workarounds for Remote Code Execution in ADFS Vulnerability - CVE-2009-2509
Microsoft has not identified any workarounds for this vulnerability.
#### FAQ for Remote Code Execution in ADFS Vulnerability - CVE-2009-2509
**What is the scope of the vulnerability?**
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could then perform actions on the IIS server with the same rights as the Worker Process Identity (WPI), which by default is configured with Network Service account privileges.
**What causes the vulnerability?**
This vulnerability exists because ADFS does not correctly validate request headers submitted by authenticated clients.
**What might an attacker use the vulnerability to do?**
An attacker who successfully exploited this vulnerability could then perform actions on the IIS server with the same rights as the Worker Process Identity (WPI). The WPI is configured with Network Service account privileges by default. IIS servers with ASP pages whose application pools are configured with a WPI that uses an account with administrative privileges could be more seriously impacted than IIS servers whose application pool is configured with the default WPI settings.
**How could an attacker exploit the vulnerability?**
An attacker could try to exploit the vulnerability by sending a specially crafted HTTP request to an ADFS-enabled Web server. An attacker would need to be an authenticated user in order to exploit this vulnerability.
**What systems are primarily at risk from the vulnerability?**
ADFS-enabled Web servers are at risk. Client systems are not affected by this vulnerability.
**What does the update do?**
This update corrects the validation that ADFS-enabled Web servers apply to request headers submitted by a Web client.
**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 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) and [Windows Update](http://go.microsoft.com/fwlink/?linkid=21130). 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).
**Note** Microsoft discontinued support for Office Update and the Office Update Inventory Tool as of August 1, 2009. To continue getting the latest updates for Microsoft Office products, use [Microsoft Update](http://go.microsoft.com/fwlink/?linkid=40747). For more information, see [About Microsoft Office Update: Frequently Asked Questions](http://office.microsoft.com/en-us/downloads/fx010402221033.aspx).
**Detection and Deployment Guidance**
Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see [Microsoft Knowledge Base Article 961747](http://support.microsoft.com/kb/961747).
**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.1 |
|--------------------------------------------------------------------------------------------------------|------------|
| Windows Server 2003 Service Pack 2 | Yes |
| Windows Server 2003 x64 Edition Service Pack 2 | Yes |
| Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 | Yes |
| Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 | Yes |
The latest version of MBSA has been released: [Microsoft Baseline Security Analyzer 2.1.1](http://www.microsoft.com/downloads/details.aspx?familyid=b1e76bbe-71df-41e8-8b52-c871d012ba78&displaylang=en). For more information, see [Microsoft Baseline Security Analyzer 2.1](http://technet.microsoft.com/en-us/security/cc184923.aspx).
**Windows Server Update Services**
By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Microsoft 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 SUIT | SMS 2003 with ITMU | Configuration Manager 2007 |
|--------------------------------------------------------------------------------------------------------|---------|--------------------|--------------------|----------------------------|
| Windows Server 2003 Service Pack 2 | Yes | Yes | Yes | Yes |
| Windows Server 2003 x64 Edition Service Pack 2 | No | No | Yes | Yes |
| Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 | No | No | Yes | Yes |
| Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 | No | No | Yes | Yes |
For SMS 2.0 and SMS 2003, 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). For more information about SMS 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](http://www.microsoft.com/downloads/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 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 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.

Click Start, and then click Search.

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

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

In the list of files, right-click a file name from the appropriate file information table, and then click Properties.Note Depending on the 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.

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 2008 (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 2008 with ADFS:
Windows6.0-KB971726-x86 /quiet

For all supported x64-based editions of Windows Server 2008 with ADFS:
Windows6.0-KB971726-x64 /quiet

Yes, you must restart your system after you apply this security update.

HotPatching

Not applicable.

Removal Information

WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.

Note A registry key does not exist to validate the presence of this 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.
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.
| Switch | Description |
|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------|
| **/?, /h, /help** | Displays help on supported switches. |
| **/quiet** | Suppresses the display of status or error messages. |
| **/norestart** | When combined with **/quiet**, the system will not be restarted after installation even if a restart is required to complete installation. |
**Note** For more information about the wusa.exe installer, see [Microsoft Knowledge Base Article 934307](http://support.microsoft.com/kb/934307).
**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 enter an update file name in **Start Search**.
2. When the file appears under **Programs**, right-click on the file name and click **Properties**.
3. Under the **General** tab, compare the file size with the file information tables provided in the bulletin KB article.
4. You may also click on the **Details** tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
5. Finally, you may also click on the **Previous Versions** tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
### Other Information
#### 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](http://www.microsoft.com/security/msrc/mapp/partners.mspx).
#### Support
- Customers in the U.S. and Canada can receive technical support from [Security Support](http://go.microsoft.com/fwlink/?linkid=21131) 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](http://support.microsoft.com/).
- 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](http://go.microsoft.com/fwlink/?linkid=21155).
#### Disclaimer
The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
#### Revisions
- V1.0 (December 8, 2009): Bulletin published.
- V1.1 (December 9, 2009): Corrected the **SMS 2.0** and **SMS 2003 with SUIT** entries for Windows Server 2003 x64 Edition Service Pack 2 in the SMS table. This is an information change only.
*Built at 2014-04-18T13:49:36Z-07:00*