Security Bulletin

Microsoft Security Bulletin MS09-036 - Important

Vulnerability in ASP.NET in Microsoft Windows Could Allow Denial of Service (970957)

Published: August 11, 2009 | Updated: August 13, 2009

Version: 1.1

General Information

Executive Summary

This security update addresses a privately reported Denial of Service vulnerability in the Microsoft .NET Framework component of Microsoft Windows. This vulnerability can be exploited only when Internet Information Services (IIS) 7.0 is installed and ASP.NET is configured to use integrated mode on affected versions of Microsoft Windows. An attacker could create specially crafted anonymous HTTP requests that could cause the affected Web server to become non-responsive until the associated application pool is restarted. Customers who are running IIS 7.0 application pools in classic mode are not affected by this vulnerability.

This security update is rated Important for all affected versions of Microsoft Windows. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerability by changing the way ASP.NET manages request scheduling. 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 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. 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 Component Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by this Update
Windows Vista* Microsoft .NET Framework 2.0 Service Pack 1 and Microsoft .NET Framework 3.5 (KB972591) and Microsoft .NET Framework 2.0 Service Pack 2 and Microsoft .NET Framework 3.5 Service Pack 1 (KB972592) Denial of Service Important None
Windows Vista Service Pack 1* Microsoft .NET Framework 2.0 Service Pack 1 and Microsoft .NET Framework 3.5 (KB972593) and Microsoft .NET Framework 2.0 Service Pack 2 and Microsoft .NET Framework 3.5 Service Pack 1 (KB972594) Denial of Service Important None
Windows Vista x64 Edition* Microsoft .NET Framework 2.0 Service Pack 1 and Microsoft .NET Framework 3.5 (KB972591) and Microsoft .NET Framework 2.0 Service Pack 2 and Microsoft .NET Framework 3.5 Service Pack 1 (KB972592) Denial of Service Important None
Windows Vista x64 Edition Service Pack 1* Microsoft .NET Framework 2.0 Service Pack 1 and Microsoft .NET Framework 3.5 (KB972593) and Microsoft .NET Framework 2.0 Service Pack 2 and Microsoft .NET Framework 3.5 Service Pack 1 (KB972594) Denial of Service Important None
Windows Server 2008 for 32-bit Systems** Microsoft .NET Framework 2.0 Service Pack 1 and Microsoft .NET Framework 3.5 (KB972593) and Microsoft .NET Framework 2.0 Service Pack 2 and Microsoft .NET Framework 3.5 Service Pack 1 (KB972594) Denial of Service Important None
Windows Server 2008 for x64-based Systems** Microsoft .NET Framework 2.0 Service Pack 1 and Microsoft .NET Framework 3.5 (KB972593) and Microsoft .NET Framework 2.0 Service Pack 2 and Microsoft .NET Framework 3.5 Service Pack 1 (KB972594) Denial of Service Important None
Windows Server 2008 for Itanium-based Systems Microsoft .NET Framework 2.0 Service Pack 1 and Microsoft .NET Framework 3.5 (KB972593) and Microsoft .NET Framework 2.0 Service Pack 2 and Microsoft .NET Framework 3.5 Service Pack 1 (KB972594) Denial of Service Important None

*Because IIS 7.0 does not run on Windows Vista Starter and Windows Vista Home Basic, the following editions are not affected: Windows Vista Starter (32-bit), Windows Vista Home Basic (32-bit), and Windows Vista Home Basic (64-bit).

**Windows Server 2008 server core installation not affected. The vulnerability addressed by this update does not affect supported editions of Windows Server 2008 if Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see 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.

Non-Affected Software

Operating System
Microsoft Windows 2000 Service Pack 4
Windows XP Service Pack 2
Windows XP Service Pack 3
Windows XP Professional x64 Edition Service Pack 2
Windows Server 2003 Service Pack 2
Windows Server 2003 x64 Edition Service Pack 2
Windows Server 2003 with SP2 for Itanium-based Systems
Windows Vista Service Pack 2
Windows Vista x64 Edition Service Pack 2
Windows Server 2008 for 32-bit Systems Service Pack 2
Windows Server 2008 for x64-based Systems Service Pack 2
Windows Server 2008 for Itanium-based Systems Service Pack 2
Windows 7 for 32-bit Systems
Windows 7 for x64-based Systems
Windows Server 2008 R2 for x64-based Systems
Windows Server 2008 R2 for Itanium-based Systems

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.

Why are Windows Vista Service Pack 2 and Windows Server 2008 Service Pack 2 not affected?
The fix for this issue is already included in the versions of Microsoft .NET Framework that ship with Windows Vista Service Pack 2 and Windows Server 2008 Service Pack 2.

Why are Microsoft .NET Framework 3.5 and Microsoft .NET Framework 3.5 Service Pack 1 affected?
Microsoft .NET Framework 3.5 includes Microsoft .NET Framework 2.0 Service Pack 1 and Microsoft .NET Framework 3.0 Service Pack 1 subcomponents. Microsoft .NET Framework 3.5 Service Pack 1 contains Microsoft .NET Framework 2.0 Service Pack 2 and Microsoft .NET Framework 3.0 Service Pack 2 subcomponents. As a result, both Microsoft .NET Framework 3.5 and Microsoft .NET Framework 3.5 Service Pack 1 contain vulnerable subcomponents.

Why am I not being offered this security update through Automatic Update?
This security update is offered only to systems that have IIS 7.0 installed on an operating system listed in the Affected Software table. Systems that are listed in the Affected Software section of this bulletin, but on which IIS 7.0 is not installed, will not be offered this update through Automatic Update, as this vulnerability can only be exploited when IIS 7.0 is installed.

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 August bulletin summary. For more information, see Microsoft Exploitability Index.

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software Remote Unauthenticated Denial of Service in ASP.NET Vulnerability - CVE-2009-1536 Aggregate Severity Rating
Microsoft .NET Framework 2.0 Service Pack 1 and Microsoft .NET Framework 3.5 on Windows Vista and Windows Vista Service Pack 1 Important 
Denial of Service
Important
Microsoft .NET Framework 2.0 Service Pack 1 and Microsoft .NET Framework 3.5 on Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 Important 
Denial of Service
Important
Microsoft .NET Framework 2.0 Service Pack 1 and Microsoft .NET Framework 3.5 on Windows Server 2008 Important 
Denial of Service
Important
Microsoft .NET Framework 2.0 Service Pack 1 and Microsoft .NET Framework 3.5 on Windows Server 2008 x64 Edition Important 
Denial of Service
Important
Microsoft .NET Framework 2.0 Service Pack 1 and Microsoft .NET Framework 3.5 on Windows Server 2008 for Itanium-based Systems Important 
Denial of Service
Important
Microsoft .NET Framework 2.0 Service Pack 2 and Microsoft .NET Framework 3.5 Service Pack 1 on Windows Vista and Windows Vista Service Pack 1 Important 
Denial of Service
Important
Microsoft .NET Framework 2.0 Service Pack 2 and Microsoft .NET Framework 3.5 Service Pack 1 on Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 Important 
Denial of Service
Important
Microsoft .NET Framework 2.0 Service Pack 2 and Microsoft .NET Framework 3.5 Service Pack 1 on Windows Server 2008\* Important 
Denial of Service
Important
Microsoft .NET Framework 2.0 Service Pack 2 and Microsoft .NET Framework 3.5 Service Pack 1 on Windows Server 2008 x64 Edition\* Important 
Denial of Service
Important
Microsoft .NET Framework 2.0 Service Pack 2 and Microsoft .NET Framework 3.5 Service Pack 1 on Windows Server 2008 Itanium-based Systems Important 
Denial of Service
Important
**\*Windows Server 2008 server core installation not affected.** The vulnerability addressed by this update does not affect supported editions of Windows Server 2008 if Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see [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). Remote Unauthenticated Denial of Service in ASP.NET Vulnerability - CVE-2009-1536 --------------------------------------------------------------------------------- A Denial of Service vulnerability exists in the way ASP.NET manages request scheduling. An attacker could exploit this vulnerability by creating specially crafted anonymous HTTP requests that would cause the affected Web server to become non-responsive until the associated application pool is restarted. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2009-1536](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2009-1536). #### Mitigating Factors for Remote Unauthenticated Denial of Service in ASP.NET Vulnerability - CVE-2009-1536 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 vulnerable code in Microsoft .NET Framework is exposed only through IIS 7.0. For systems not running IIS 7.0, there are no known attack vectors for this vulnerability. - Systems running ASP.NET on IIS 7.0 in classic mode are not affected by this vulnerability. #### Workarounds for Remote Unauthenticated Denial of Service in ASP.NET Vulnerability - CVE-2009-1536 Workarounds refer to settings or configuration changes that do 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: - **Switch to the IIS native thread pool** When ASP.NET 2.0 is hosted on IIS 7.0 in integrated mode, ASP.NET manages requests using the common language runtime (CLR) thread pool. Systems on which the requests are managed by the IIS 7.0 native thread pool instead of by the CLR thread pool are not affected by this issue. For more information, see the MSDN article, [.NET: The CLR's Thread Pool](http://msdn.microsoft.com/en-us/magazine/cc164139.aspx). Use one of the following two methods to configure IIS 7.0 to use the native thread pool for process handling. **Method 1: Specify the value for maxConcurrentRequestsPerCPU in the registry** This setting is global and affects all application pools. In order to configure this setting for individual application pools, refer to Method 2 in this section. **Warning** Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. **Note** We recommend backing up the registry before you edit it. 1. Click **Start**, click **Run**, type **Regedit** in the **Open** box, and then click **OK**. 2. Locate and then click the following registry subkey: HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\ASP.NET\\2.0.50727.0 3. On the **Edit** menu, point to **New**, and then click **Key**. 4. Type **maxConcurrentRequestsPerCPU**, and then press **Enter**. 5. Click the **maxConcurrentRequestsPerCPU** key. 6. On the **Edit** menu, point to **New**, and then click **DWORD**. 7. Type **maxConcurrentRequestsPerCPU**, and then press **Enter**. 8. On the **Edit** menu, click **Modify** to modify the **maxConcurrentRequestsPerCPU** registry entry. 9. In the **Value** data box, type **0**, and then click **OK**. 10. Exit Registry Editor. 11. Use iisreset.exe to restart Microsoft Internet Information Services (IIS) on the Web server that is hosting the application by running the following command at a command line: iisreset /restart **Specify the value for maxConcurrentRequestsPerCPUvia .REG file** Windows Registry Editor Version 5.00 \[HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\ASP.NET\\2.0.50727.0\] "MaxConcurrentRequestsPerCPU"=dword:00000000 You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy. For more information about Group Policy, visit the following Microsoft Web sites: [Group Policy collection](http://technet2.microsoft.com/windowsserver/en/library/6d7cb788-b31d-4d17-9f1e-b5ddaa6deecd1033.mspx?mfr=true) [What is Group Policy Object Editor?](http://technet2.microsoft.com/windowsserver/en/library/47ba1311-6cca-414f-98c9-2d7f99fca8a31033.mspx?mfr=true) [Core Group Policy tools and settings](http://technet2.microsoft.com/windowsserver/en/library/e926577a-5619-4912-b5d9-e73d4bdc94911033.mspx?mfr=true) **Impact of workaround.** Depending on the nature of applications running in this application pool, application performance may be affected. **How to undo the workaround.** Undoing the workaround manually 1. Click **Start**, click **Run**, type **Regedit** in the **Open** box, and then click **OK**. Locate and then click the following registry subkey: HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\ASP.NET\\2.0.50727.0\\maxConcurrentRequestsPerCPU 2. Right-click the **maxConcurrentRequestsPerCPU** subkey, click **Delete**, and then click **Yes**. 3. Exit the Registry Editor. Use Iisreset.exe to restart Microsoft Internet Information Services (IIS) on the Web server that is hosting the application by running the following command from a command line: iisreset /restart Undoing the workaround via a .REG file Version 5.00 \[HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\ASP.NET\\2.0.50727.0\] "MaxConcurrentRequestsPerCPU"=dword:00000000 You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy. For more information about Group Policy, visit the following Microsoft Web sites: [Group Policy collection](http://technet2.microsoft.com/windowsserver/en/library/6d7cb788-b31d-4d17-9f1e-b5ddaa6deecd1033.mspx?mfr=true) [What is Group Policy Object Editor?](http://technet2.microsoft.com/windowsserver/en/library/47ba1311-6cca-414f-98c9-2d7f99fca8a31033.mspx?mfr=true) [Core Group Policy tools and settings](http://technet2.microsoft.com/windowsserver/en/library/e926577a-5619-4912-b5d9-e73d4bdc94911033.mspx?mfr=true) **Method 2: Specify the value for maxConcurrentRequestsPerCPUfor an application pool in the ASP.NET config section of an ASPNET.Config file** **Note** This workaround only applies to systems on which the Microsoft .NET Framework 2.0 SP2 or Microsoft .NET Framework 3.5 SP1 is running. Earlier versions of the Microsoft .NET Framework do not read aspnet.config for this information. This value overrides the value that is specified for maxConcurrentRequestsPerCPU in the registry. **Note** In order to undo this workaround, you need to restore the original version of the aspnet.config file. Before editing this file, create a backup. Open the aspnet.config file for the application pool and then enter new values for the maxConcurrentRequestsPerCPU parameter as follows: <system.web> <applicationPool maxConcurrentRequestsPerCPU="0"/> </system.web> **Impact of workaround.** Depending on the nature of applications running in this application pool, application performance may be affected. **How to undo the workaround.** Restore the original version of the aspnet.config file. #### FAQ for Remote Unauthenticated Denial of Service in ASP.NET Vulnerability - CVE-2009-1536 **What is the scope of the vulnerability?**  This is a Denial of Service vulnerability that could allow an attacker to cause a Web server to become non-responsive. **What causes the vulnerability?**  This vulnerability is caused by ASP.NET incorrectly managing request scheduling. **What might an attacker use the vulnerability to do?**  An attacker who successfully exploited this vulnerability could cause the application pool on the affected Web server to become non-responsive until the application pool is restarted. As a result, Web pages that use ASP.NET in the same application pool would no longer be reachable and would return an HTTP error. All non-ASP.NET features of the server are unaffected when a server is vulnerable to this issue and is attacked. For example, HTML pages will continue to load normally. This is an application-level denial of service vulnerability. In order to recover from a successful attack, either IIS must be reset or the affected application pool must be recycled, but the server operating system does not need to be restarted. **What is ASP.NET?**  ASP.NET is a collection of technologies within the Microsoft .NET Framework that enable developers to build Web applications and XML Web Services. Unlike traditional Web pages, which use a combination of static HTML and scripting, ASP.NET uses compiled, event-driven pages. Because ASP.NET is a Web-based application environment, requiring an underlying Web server to provide basic HTTP functionality, ASP.NET runs on top of Internet Information Services (IIS). For more information, see [The Official Microsoft ASP.NET Site](http://www.asp.net/). **What is the difference between Integrated Mode and Classic Mode in IIS 7.0?**  In IIS 7.0, each Web site hosted on the server can run in either Integrated Mode or Classic Mode. Integrated Mode is the default mode in IIS 7.0 and provides more granular control over the request process. Classic Mode reverts back to IIS 6.0 behavior when Integrated Mode was not yet available. For more information, see [How to Take Advantage of the IIS 7.0 Integrated Pipeline](http://learn.iis.net/page.aspx/244/how-to-take-advantage-of-the-iis7-integrated-pipeline). **What is an application pool?**  In IIS 7.0, an application pool is a group of one or more URLs that are served by a worker process or a set of worker processes. Application pools set boundaries for the applications they contain, which means that any applications that are running outside a given application pool cannot affect the applications that are running inside that application pool. For more information, see [IIS 7.0: Managing Application Pools in IIS 7.0](http://technet.microsoft.com/en-us/library/cc753449(ws.10).aspx). **How could an attacker exploit the vulnerability?**  An attacker could exploit this vulnerability by creating a specially crafted series of anonymous HTTP requests to an affected system and thereby cause the Web server running on this system to become non-responsive. **What systems are primarily at risk from the vulnerability?**  Servers on which ASP 2.0 is hosted on IIS 7.0 in integrated mode are at risk. **What does the update do?**  The update modifies the way in which ASP.NET manages request scheduling. **When this security bulletin was issued, had this vulnerability been publicly disclosed?**  No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued. **When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?**  Yes. Microsoft is aware of limited, targeted attacks attempting to exploit the reported vulnerability. ### 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** Starting August 1, 2009, Microsoft will discontinue support for Office Update and the Office Update Inventory Tool. 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 | |------------------------------------------------------------------------|----------| | Windows Vista and Windows Vista Service Pack 1 | Yes | | Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 | Yes | | Windows Server 2008 for 32-bit Systems | Yes | | Windows Server 2008 for x64-based Systems | Yes | | Windows Server 2008 for Itanium-based Systems | 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 SUIT | SMS 2003 with ITMU | Configuration Manager 2007 | |------------------------------------------------------------------------|---------|--------------------|--------------------|----------------------------| | Windows Vista and Windows Vista Service Pack 1 | No | No | Yes\* | Yes | | Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 | No | No | Yes\* | Yes | | Windows Server 2008 for 32-bit Systems | No | No | Yes\* | Yes | | Windows Server 2008 for x64-based Systems | No | No | Yes\* | Yes | | Windows Server 2008 for Itanium-based Systems | 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). **\* Note for Windows Vista and Windows Server 2008** Microsoft Systems Management Server 2003 with Service Pack 3 includes support for Windows Vista and Windows Server 2008 manageability. 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](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 Vista (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 Microsoft .NET Framework 2.0 Service Pack 1 or Microsoft .NET Framework 3.5 on Windows Vista:
Windows6.0-KB972591-x86 /quiet
For Microsoft .NET Framework 2.0 Service Pack 2 or Microsoft .NET Framework 3.5 Service Pack 1 on Windows Vista:
Windows6.0-KB972592-x86 /quiet
For Microsoft .NET Framework 2.0 Service Pack 1 or Microsoft .NET Framework 3.5 on Windows Vista Service Pack 1:
Windows6.0-KB972593-x86 /quiet
For Microsoft .NET Framework 2.0 Service Pack 2 or Microsoft .NET Framework 3.5 Service Pack 1 on Windows Vista Service Pack 1:
Windows6.0-KB972594-x86 /quiet
For Microsoft .NET Framework 2.0 Service Pack 1 or Microsoft .NET Framework 3.5 on Windows Vista x64 Edition:
Windows6.0-KB972591-x64 /quiet
For Microsoft .NET Framework 2.0 Service Pack 2 or Microsoft .NET Framework 3.5 Service Pack 1 on Windows Vista x64 Edition:
Windows6.0-KB972592-x64 /quiet
For Microsoft .NET Framework 2.0 Service Pack 1 or Microsoft .NET Framework 3.5 on Windows Vista x64 Edition Service Pack 1:
Windows6.0-KB972593-x64 /quiet
For Microsoft .NET Framework 2.0 Service Pack 2 or Microsoft .NET Framework 3.5 Service Pack 1 on Windows Vista x64 Edition Service Pack 1:
Windows6.0-KB972594-x64 /quiet
Installing without restarting For Microsoft .NET Framework 2.0 Service Pack 1 or Microsoft .NET Framework 3.5 on Windows Vista:
Windows6.0-KB972591-x86 /quiet /norestart
For Microsoft .NET Framework 2.0 Service Pack 2 or Microsoft .NET Framework 3.5 Service Pack 1 on Windows Vista:
Windows6.0-KB972592-x86 /quiet /norestart
For Microsoft .NET Framework 2.0 Service Pack 1 or Microsoft .NET Framework 3.5 on Windows Vista Service Pack 1:
Windows6.0-KB972593-x86 /quiet /norestart
For Microsoft .NET Framework 2.0 Service Pack 2 or Microsoft .NET Framework 3.5 Service Pack 1 on Windows Vista Service Pack 1:
Windows6.0-KB972594-x86 /quiet /norestart
For Microsoft .NET Framework 2.0 Service Pack 1 or Microsoft .NET Framework 3.5 on Windows Vista x64 Edition:
Windows6.0-KB972591-x64 /quiet /norestart
For Microsoft .NET Framework 2.0 Service Pack 2 or Microsoft .NET Framework 3.5 Service Pack 1 on Windows Vista x64 Edition:
Windows6.0-KB972592-x64 /quiet /norestart
For Microsoft .NET Framework 2.0 Service Pack 1 or Microsoft .NET Framework 3.5 on Windows Vista x64 Edition Service Pack 1:
Windows6.0-KB972593-x64 /quiet /norestart
For Microsoft .NET Framework 2.0 Service Pack 2 or Microsoft .NET Framework 3.5 Service Pack 1 on Windows Vista x64 Edition Service Pack 1:
Windows6.0-KB972594-x64 /quiet /norestart
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required? This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
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.
File Information See Microsoft Knowledge Base Article 970957
Registry Key Verification 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. #### 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 Microsoft .NET Framework 2.0 Service Pack 1 or Microsoft .NET Framework 3.5 on Windows Server 2008 for 32-bit Systems:
Windows6.0-KB972593-x86 /quiet
For Microsoft .NET Framework 2.0 Service Pack 2 or Microsoft .NET Framework 3.5 Service Pack 1 on Windows Server 2008 for 32-bit systems:
Windows6.0-KB972594-x86 /quiet
For Microsoft .NET Framework 2.0 Service Pack 1 or Microsoft .NET Framework 3.5 on Windows Server 2008 for x64-based Systems:
Windows6.0-KB972593-x64 /quiet
For Microsoft .NET Framework 2.0 Service Pack 2 or Microsoft .NET Framework 3.5 Service Pack 1 on Windows Server 2008 for x64-based Systems:
Windows6.0-KB972594-x64 /quiet
For Microsoft .NET Framework 2.0 Service Pack 1 or Microsoft .NET Framework 3.5 on Windows Server 2008 for Itanium-based Systems:
Windows6.0-KB972593-ia64 /quiet
For Microsoft .NET Framework 2.0 Service Pack 2 or Microsoft .NET Framework 3.5 Service Pack 1 on Windows Server 2008 for Itanium-based Systems:
Windows6.0-KB972594-ia64 /quiet
Installing without restarting For Microsoft .NET Framework 2.0 Service Pack 1 or Microsoft .NET Framework 3.5 on Windows Server 2008 for 32-bit Systems:
Windows6.0-KB972593-x86 /quiet /norestart
For Microsoft .NET Framework 2.0 Service Pack 2 or Microsoft .NET Framework 3.5 Service Pack 1 on Windows Server 2008 for 32-bit Systems:
Windows6.0-KB972594-x86 /quiet /norestart
For Microsoft .NET Framework 2.0 Service Pack 1 or Microsoft .NET Framework 3.5 on Windows Server 2008 for x64-based Systems:
Windows6.0-KB972593-x64 /quiet /norestart
For Microsoft .NET Framework 2.0 Service Pack 2 or Microsoft .NET Framework 3.5 Service Pack 1 on Windows Server 2008 for x64-based Systems:
Windows6.0-KB972594-x64 /quiet /norestart
For Microsoft .NET Framework 2.0 Service Pack 1 or Microsoft .NET Framework 3.5 on Windows Server 2008 for Itanium-based Systems:
Windows6.0-KB972593-ia64 /quiet /norestart
For Microsoft .NET Framework 2.0 Service Pack 2 or Microsoft .NET Framework 3.5 Service Pack 1 on Windows Server 2008 for Itanium-based Systems:
Windows6.0-KB972594-ia64 /quiet /norestart
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required? This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
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.
File Information See Microsoft Knowledge Base Article 970957
Registry Key Verification 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 #### Acknowledgments Microsoft [thanks](http://go.microsoft.com/fwlink/?linkid=21127) the following for working with us to help protect customers: - Alexander Pfandt of [Digitaria](http://www.digitaria.com/) for reporting the Remote Unauthenticated Denial of Service in ASP.NET Vulnerability (CVE-2009-1536) #### 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 (August 11, 2009): Bulletin published. - V1.1 (August 13, 2009): Clarified in **Frequently Asked Questions (FAQ) Related to This Security Update** that this security update will only be offered when IIS 7.0 is installed. Added information to the **FAQ for Remote Unauthenticated Denial of Service in ASP.NET Vulnerability – CVE-2009-1536** about the difference between Integrated Mode and Classic Mode in IIS 7.0. This is an informational change only. Customers who have successfully installed this update do not need to reinstall. *Built at 2014-04-18T13:49:36Z-07:00*