Security Bulletin
Microsoft Security Bulletin MS13-007 - Important
Vulnerability in Open Data Protocol Could Allow Denial of Service (2769327)
Published: January 08, 2013 | Updated: April 03, 2013
Version: 1.1
General Information
Executive Summary
This security update resolves a privately reported vulnerability in the Open Data (OData) protocol. The vulnerability could allow denial of service if an unauthenticated attacker sends specially crafted HTTP requests to an affected site. Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems that are connected to the Internet have a minimal number of ports exposed.
This security update is rated Important for Microsoft .NET Framework 3.5, Microsoft .NET Framework 3.5 Service Pack 1, Microsoft .NET Framework 3.5.1, and Microsoft .NET Framework 4. It is also rated Important for Management OData IIS Extension when installed on Microsoft Windows Server 2012. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerability by turning off the WCF Replace function by default. 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. Most 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 2769327 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, see Microsoft Support Lifecycle.
Affected Software
| Operating System | Component | Maximum Security Impact | Aggregate Severity Rating | Updates Replaced |
|---|---|---|---|---|
| Windows XP | ||||
| Windows XP Service Pack 3 | Microsoft .NET Framework 3.5 Service Pack 1 (KB2736416) Microsoft .NET Framework 4[1](KB2736428) | Denial of Service | Important | None |
| Windows XP Professional x64 Edition Service Pack 2 | Microsoft .NET Framework 3.5 Service Pack 1 (KB2736416) Microsoft .NET Framework 4[1](KB2736428) | Denial of Service | Important | None |
| Windows Server 2003 Service Pack 2 | ||||
| Windows Server 2003 Service Pack 2 | Microsoft .NET Framework 3.5 Service Pack 1 (KB2736416) Microsoft .NET Framework 4[1](KB2736428) | Denial of Service | Important | None |
| Windows Server 2003 x64 Edition Service Pack 2 | Microsoft .NET Framework 3.5 Service Pack 1 (KB2736416) Microsoft .NET Framework 4[1](KB2736428) | Denial of Service | Important | None |
| Windows Server 2003 with SP2 for Itanium-based Systems | Microsoft .NET Framework 3.5 Service Pack 1 (KB2736416) Microsoft .NET Framework 4[1](KB2736428) | Denial of Service | Important | None |
| Windows Vista | ||||
| Windows Vista Service Pack 2 | Microsoft .NET Framework 3.5 Service Pack 1 (KB2736416) Microsoft .NET Framework 4[1](KB2736428) | Denial of Service | Important | None |
| Windows Vista x64 Edition Service Pack 2 | Microsoft .NET Framework 3.5 Service Pack 1 (KB2736416) Microsoft .NET Framework 4[1](KB2736428) | Denial of Service | Important | None |
| Windows Server 2008 | ||||
| Windows Server 2008 for 32-bit Systems Service Pack 2 | Microsoft .NET Framework 3.5 Service Pack 1 (KB2736416) Microsoft .NET Framework 4[1](KB2736428) | Denial of Service | Important | None |
| Windows Server 2008 for x64-based Systems Service Pack 2 | Microsoft .NET Framework 3.5 Service Pack 1 (KB2736416) Microsoft .NET Framework 4[1](KB2736428) | Denial of Service | Important | None |
| Windows Server 2008 for Itanium-based Systems Service Pack 2 | Microsoft .NET Framework 3.5 Service Pack 1 (KB2736416) Microsoft .NET Framework 4[1](KB2736428) | Denial of Service | Important | None |
| Windows 7 | ||||
| Windows 7 for 32-bit Systems | Microsoft .NET Framework 3.5.1 (KB2736418) Microsoft .NET Framework 4[1](KB2736428) | Denial of Service | Important | None |
| Windows 7 for 32-bit Systems Service Pack 1 | Microsoft .NET Framework 3.5.1 (KB2736422) Microsoft .NET Framework 4[1](KB2736428) | Denial of Service | Important | None |
| Windows 7 for x64-based Systems | Microsoft .NET Framework 3.5.1 (KB2736418) Microsoft .NET Framework 4[1](KB2736428) | Denial of Service | Important | None |
| Windows 7 for x64-based Systems Service Pack 1 | Microsoft .NET Framework 3.5.1 (KB2736422) Microsoft .NET Framework 4[1](KB2736428) | Denial of Service | Important | None |
| Windows Server 2008 R2 | ||||
| Windows Server 2008 R2 for x64-based Systems | Microsoft .NET Framework 3.5.1 (KB2736418) Microsoft .NET Framework 4[1](KB2736428) | Denial of Service | Important | None |
| Windows Server 2008 R2 for x64-based Systems Service Pack 1 | Microsoft .NET Framework 3.5.1 (KB2736422) Microsoft .NET Framework 4[1](KB2736428) | Denial of Service | Important | None |
| Windows Server 2008 R2 for Itanium-based Systems | Microsoft .NET Framework 3.5.1 (KB2736418) Microsoft .NET Framework 4[1](KB2736428) | Denial of Service | Important | None |
| Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | Microsoft .NET Framework 3.5.1 (KB2736422) Microsoft .NET Framework 4[1](KB2736428) | Denial of Service | Important | None |
| Windows 8 | ||||
| Windows 8 for 32-bit Systems | Microsoft .NET Framework 3.5 (KB2736693) | Denial of Service | Important | None |
| Windows 8 for 64-bit Systems | Microsoft .NET Framework 3.5 (KB2736693) | Denial of Service | Important | None |
| Windows Server 2012 | ||||
| Windows Server 2012 | Microsoft .NET Framework 3.5 (KB2736693) Management OData IIS Extension (KB2753596) | Denial of Service | Important | None |
| Server Core installation option | ||||
| Windows Server 2008 R2 for x64-based Systems (Server Core installation) | Microsoft .NET Framework 3.5.1 (Server Core installation) (KB2736418) | Denial of Service | Important | None |
| Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) | Microsoft .NET Framework 3.5.1 (Server Core installation) (KB2736422) Microsoft .NET Framework 4[1] (Server Core installation) (KB2736428) | Denial of Service | Important | None |
| Windows Server 2012 (Server Core installation) | Microsoft .NET Framework 3.5 (Server Core installation) (KB2736693) Management OData IIS Extension (Server Core installation) (KB2753596) | Denial of Service | Important | None |
[1].NET Framework 4 and .NET Framework 4 Client Profile affected. The .NET Framework version 4 redistributable packages are available in two profiles: .NET Framework 4 and .NET Framework 4 Client Profile. .NET Framework 4 Client Profile is a subset of .NET Framework 4. The vulnerability addressed in this update affects both .NET Framework 4 and .NET Framework 4 Client Profile. For more information, see the MSDN article, Installing the .NET Framework.
Non-Affected Software
| Software |
|---|
| Microsoft .NET Framework 1.0 Service Pack 3 |
| Microsoft .NET Framework 1.1 Service Pack 1 |
| Microsoft .NET Framework 2.0 Service Pack 2 |
| Microsoft .NET Framework 3.0 Service Pack 2 |
| Microsoft .NET Framework 4.5 |
| Operating System |
| Windows RT |
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.
How do I determine which version of the Microsoft .NET Framework is installed?
You can install and run multiple versions of the .NET Framework on a system, and you can install the versions in any order. There are several ways to determine which versions of the .NET Framework are currently installed. For more information, see Microsoft Knowledge Base Article 318785.
What is the difference between .NET Framework 4 and .NET Framework 4 Client Profile?
The .NET Framework version 4 redistributable packages are available in two profiles: .NET Framework 4 and .NET Framework 4 Client Profile. The .NET Framework 4 Client Profile is a subset of the .NET Framework 4 profile that is optimized for client applications. It provides functionality for most client applications, including Windows Presentation Foundation (WPF), Windows Forms, Windows Communication Foundation (WCF), and ClickOnce features. This enables faster deployment and a smaller install package for applications that target the .NET Framework 4 Client Profile. For more information, see the MSDN article, .NET Framework Client Profile.
Where are the hashes of the security updates?
The SHA1 and SHA2 hashes of the security updates can be used to verify the authenticity of downloaded security update packages. For the hash information pertaining to this update, see Microsoft Knowledge Base Article 2769327.
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, see the Microsoft Support Lifecycle website.
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 Service Pack Lifecycle Support Policy.
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, see the Microsoft Worldwide Information website, 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 January bulletin summary. For more information, see Microsoft Exploitability Index.
| Affected Software | Replace Denial of Service Vulnerability - CVE-2013-0005 | Aggregate Severity Rating |
|---|---|---|
| Microsoft .NET Framework 3.5 | ||
| Microsoft .NET Framework 3.5 on Windows 8 for 32-bit Systems | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5 on Windows 8 for 64-bit Systems | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5 on Windows Server 2012 | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5 Service Pack 1 | ||
| Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows XP Service Pack 3 | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows XP Professional x64 Edition Service Pack 2 | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Server 2003 Service Pack 2 | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Server 2003 x64 Edition Service Pack 2 | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Server 2003 with SP2 for Itanium-based Systems | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Vista Service Pack 2 | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Vista x64 Edition Service Pack 2 | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Server 2008 for 32-bit Systems Service Pack 2 | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Server 2008 for x64-based Systems Service Pack 2 | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Server 2008 for Itanium-based Systems Service Pack 2 | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5.1 | ||
| Microsoft .NET Framework 3.5.1 on Windows 7 for 32-bit Systems | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5.1 on Windows 7 for 32-bit Systems Service Pack 1 | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5.1 on Windows 7 for x64-based Systems | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5.1 on Windows 7 for x64-based Systems Service Pack 1 | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5.1 on Windows Server 2008 R2 for x64-based Systems | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5.1 on Windows Server 2008 R2 for x64-based Systems Service Pack 1 | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5.1 on Windows Server 2008 R2 for Itanium-based Systems | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5.1 on Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | Important Denial of Service | Important |
| Microsoft .NET Framework 4 | ||
| Microsoft .NET Framework 4 when installed on Windows XP Service Pack 3 | Important Denial of Service | Important |
| Microsoft .NET Framework 4 when installed on Windows XP Professional x64 Edition Service Pack 2 | Important Denial of Service | Important |
| Microsoft .NET Framework 4 when installed on Windows Server 2003 Service Pack 2 | Important Denial of Service | Important |
| Microsoft .NET Framework 4 when installed on Windows Server 2003 x64 Edition Service Pack 2 | Important Denial of Service | Important |
| Microsoft .NET Framework 4 when installed on Windows Server 2003 with SP2 for Itanium-based Systems | Important Denial of Service | Important |
| Microsoft .NET Framework 4 when installed on Windows Vista Service Pack 2 | Important Denial of Service | Important |
| Microsoft .NET Framework 4 when installed on Windows Vista x64 Edition Service Pack 2 | Important Denial of Service | Important |
| Microsoft .NET Framework 4 when installed on Windows Server 2008 for 32-bit Systems Service Pack 2 | Important Denial of Service | Important |
| Microsoft .NET Framework 4 when installed on Windows Server 2008 for x64-based Systems Service Pack 2 | Important Denial of Service | Important |
| Microsoft .NET Framework 4 when installed on Windows Server 2008 for Itanium-based Systems Service Pack 2 | Important Denial of Service | Important |
| Microsoft .NET Framework 4 when installed on Windows 7 for 32-bit Systems | Important Denial of Service | Important |
| Microsoft .NET Framework 4 when installed on Windows 7 for 32-bit Systems Service Pack 1 | Important Denial of Service | Important |
| Microsoft .NET Framework 4 when installed on Windows 7 for x64-based Systems | Important Denial of Service | Important |
| Microsoft .NET Framework 4 when installed on Windows 7 for x64-based Systems Service Pack 1 | Important Denial of Service | Important |
| Microsoft .NET Framework 4 when installed on Windows Server 2008 R2 for x64-based Systems | Important Denial of Service | Important |
| Microsoft .NET Framework 4 when installed on Windows Server 2008 R2 for x64-based Systems Service Pack 1 | Important Denial of Service | Important |
| Microsoft .NET Framework 4 when installed on Windows Server 2008 R2 for Itanium-based Systems | Important Denial of Service | Important |
| Microsoft .NET Framework 4 when installed on Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | Important Denial of Service | Important |
| Management OData IIS Extension | ||
| Management OData IIS Extension when installed on Windows Server 2012 | Important Denial of Service | Important |
| Server Core installation option | ||
| Microsoft .NET Framework 3.5 on Windows Server 2012 (Server Core installation) | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5.1 on Windows Server 2008 R2 for x64-based Systems (Server Core installation) | Important Denial of Service | Important |
| Microsoft .NET Framework 3.5.1 on Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) | Important Denial of Service | Important |
| Microsoft .NET Framework 4 when installed on Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) | Important Denial of Service | Important |
| Management OData IIS Extension when installed on Windows Server 2012 (Server Core installation) | Important Denial of Service | Important |
Replace Denial of Service Vulnerability - CVE-2013-0005
A denial of service vulnerability exists in the OData specification that could allow denial of service. The vulnerability could cause the server or service to stop responding and restart.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2013-0005.
Mitigating Factors for Replace Denial of Service Vulnerability - CVE-2013-0005
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:
- Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems that are connected to the Internet have a minimal number of ports exposed.
- Systems running Windows Server 2012 in its default configuration are not at risk from this vulnerability since the Management OData IIS extension is not enabled by default. Only Windows Server 2012 systems where the Management OData IIS extension has been enabled are vulnerable.
Workarounds for Replace Denial of Service Vulnerability - CVE-2013-0005
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:
Block OData Web Application ports at the firewall
OData ports are typically hosted on TCP ports 80 and 443, but could be hosted on other non-standard ports as well. Evaluating your environment and blocking inbound and outbound connections to all ports where an OData service is hosted at the enterprise firewall will help protect systems from attempts to exploit this vulnerability. We recommend that you block all unsolicited inbound communication from the Internet to help prevent attacks that may use other ports. For more information about ports, see the TechNet article, TCP and UDP Port Assignments.
Require Authentication for clients connecting to IIS
You can enable authentication in IIS to block unauthenticated attackers from exploiting this vulnerability. For information on how to implement authentication in your environment, refer to the TechNet documentation for your version of IIS. For IIS 7, see Configuring Authentication in IIS 7
For IIS 6.0, see Integrated Windows Authentication in IIS 6.0
FAQ for Replace Denial of Service Vulnerability - CVE-2013-0005
What is the scope of the vulnerability?
This is a denial of service vulnerability.
What causes the vulnerability?
The vulnerability is caused when the WCF Replace function improperly sanitizes specially crafted values, allowing the replication of data and the exhaustion of system resources.
What is OData?
The Open Data (OData) protocol is a web protocol for querying and updating data that provides a way to unlock your data and free it from silos that exist in applications today. OData does this by applying and building upon web technologies, such as HTTP, Atom Publishing Protocol (AtomPub), and JSON, to provide access to information from a variety of applications, services, and stores. The protocol emerged from experiences implementing AtomPub clients and servers in a variety of products over the past several years. OData is being used to expose and access information from a variety of sources including, but not limited to, relational databases, file systems, content management systems, and traditional websites. For more information about the OData specification, see the Open Data Protocol website.
What is the Management OData IIS Extension Web Service? The Management OData IIS Extension is a framework for easily exposing Windows PowerShell cmdlets through an OData-based web service running under IIS. For more information, see Creating a Management OData IIS Extension Web Service.
What is WCF? Windows Communication Foundation (WCF) is Microsoft's unified programming model for building service-oriented applications that enable developers to build secure, reliable, transacted solutions that integrate across platforms and interoperate with existing investments. For more information about WCF, see Windows Communication Foundation.
What might an attacker use the vulnerability to do?
An attacker could use this vulnerability to cause a denial of service attack and disrupt the availability of sites that use .NET WCF Services.
How could an attacker exploit the vulnerability?
An unauthenticated attacker could send a small number of specially crafted HTTP requests to an affected site, causing a denial of service condition.
What systems are primarily at risk from the vulnerability?
Internet-facing systems with .NET Framework and WCF services installed are primarily at risk from this vulnerability. Windows Server 2012 systems running IIS with the Management OData IIS Extension are also primarily at risk from this vulnerability.
What does the update do?
The update addresses the vulnerability by turning off the WCF Replace function by default.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through coordinated vulnerability 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
Security Central
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. The Microsoft TechNet Security website provides additional information about security in Microsoft products.
Security updates are available from Microsoft Update and Windows Update. Security updates are also available from the Microsoft Download Center. 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. 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, "MS12-001"), you can add all 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.
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.
Microsoft Baseline Security Analyzer
Microsoft Baseline Security Analyzer (MBSA) lets administrators scan local and remote systems for missing security updates as well as common security misconfigurations. For more information, see Microsoft Baseline Security Analyzer.
The following table provides the MBSA detection summary for this security update.
| Software | MBSA |
|---|---|
| Windows XP Service Pack 3 | Yes |
| Windows XP Professional x64 Edition Service Pack 2 | Yes |
| Windows Server 2003 Service Pack 2 | Yes |
| Windows Server 2003 x64 Edition Service Pack 2 | Yes |
| Windows Server 2003 with SP2 for Itanium-based Systems | Yes |
| Windows Vista Service Pack 2 | Yes |
| Windows Vista x64 Edition Service Pack 2 | Yes |
| Windows Server 2008 for 32-bit Systems Service Pack 2 | Yes |
| Windows Server 2008 for x64-based Systems Service Pack 2 | Yes |
| Windows Server 2008 for Itanium-based Systems Service Pack 2 | Yes |
| Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 | Yes |
| Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 | Yes |
| Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1 | Yes |
| Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | Yes |
| Windows 8 for 32-bit Systems | No |
| Windows 8 for 64-bit Systems | No |
| Windows Server 2012 | No |
Note For customers using legacy software not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, please see Microsoft Baseline Security Analyzer and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools.
Windows Server Update Services
Windows Server Update Services (WSUS) enables information technology administrators to deploy the latest Microsoft product updates to computers that are running the Windows operating system. For more information about how to deploy security updates using Windows Server Update Services, see the TechNet article, Windows Server Update Services.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
| Software | SMS 2003 with ITMU | System Center Configuration Manager |
|---|---|---|
| Windows XP Service Pack 3 | Yes | Yes |
| Windows XP Professional x64 Edition Service Pack 2 | Yes | Yes |
| Windows Server 2003 Service Pack 2 | Yes | Yes |
| Windows Server 2003 x64 Edition Service Pack 2 | Yes | Yes |
| Windows Server 2003 with SP2 for Itanium-based Systems | Yes | Yes |
| Windows Vista Service Pack 2 | Yes | Yes |
| Windows Vista x64 Edition Service Pack 2 | Yes | Yes |
| Windows Server 2008 for 32-bit Systems Service Pack 2 | Yes | Yes |
| Windows Server 2008 for x64-based Systems Service Pack 2 | Yes | Yes |
| Windows Server 2008 for Itanium-based Systems Service Pack 2 | Yes | Yes |
| Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 | Yes | Yes |
| Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 | Yes | Yes |
| Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1 | Yes | Yes |
| Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | Yes | Yes |
| Windows 8 for 32-bit Systems | Yes | Yes |
| Windows 8 for 64-bit Systems | Yes | Yes |
| Windows Server 2012 | Yes | Yes |
Note Microsoft discontinued support for SMS 2.0 on April 12, 2011. For SMS 2003, Microsoft also discontinued support for the Security Update Inventory Tool (SUIT) on April 12, 2011. Customers are encouraged to upgrade to System Center Configuration Manager. For customers remaining on SMS 2003 Service Pack 3, the Inventory Tool for Microsoft Updates (ITMU) is also an option.
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 and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.
System Center Configuration Manager uses WSUS 3.0 for detection of updates. For more information, see System Center.
For more detailed information, see Microsoft Knowledge Base Article 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 components included with Application Compatibility Toolkit.
The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying 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 Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows XP Service Pack 3:\ NDP35SP1-KB2736416-x86.exe /quiet |
| For Microsoft .NET Framework 4 when installed on Windows XP Service Pack 3:\ NDP40-KB2736428-x86.exe /quiet | |
| For Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows XP Professional x64 Edition Service Pack 2:\ NDP35SP1-KB2736416-x64.exe /quiet | |
| For Microsoft .NET Framework 4 when installed on Windows XP Professional x64 Edition Service Pack 2:\ NDP40-KB2736428-x64.exe /quiet | |
| Installing without restarting | For Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows XP Service Pack 3:\ NDP35SP1-KB2736416-x86.exe /norestart |
| For Microsoft .NET Framework 4 when installed on Windows XP Service Pack 3:\ NDP40-KB2736428-x86.exe /norestart | |
| For Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows XP Professional x64 Edition Service Pack 2:\ NDP35SP1-KB2736416-x64.exe /norestart | |
| For Microsoft .NET Framework 4 when installed on Windows XP Professional x64 Edition Service Pack 2:\ NDP40-KB2736428-x64.exe /norestart | |
| Update log file | For Microsoft .NET Framework 3.5 Service Pack 1:\ Microsoft .NET Framework 3.5-KB2736416_*-msi0.txt Microsoft .NET Framework 3.5-KB2736416_*.html |
| For Microsoft .NET Framework 4:\ KB2736428_*_*-Microsoft .NET Framework 4 Client Profile-MSP0.txt\ KB2736428_*_*.html | |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.\ \ To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
| HotPatching | Not applicable |
| Removal Information | For all supported versions of Microsoft .NET Framework, use the Add or Remove Programs item in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 2736416\ See Microsoft Knowledge Base Article 2736428 |
| Registry Key Verification | For Microsoft .NET Framework 3.5 Service Pack 1:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 3.5 Service Pack 1\SP1\KB2736416\ "ThisVersionInstalled" = "Y" |
| For Microsoft .NET Framework 4 when installed on Windows XP Service Pack 3:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2736428\ "ThisVersionInstalled" = "Y" | |
| For Microsoft .NET Framework 4 when installed on Windows XP Professional x64 Edition Service Pack 2:\ HKEY_LOCAL_MACHINE\SOFTWARE\ Wow6432Node\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2736428\ "ThisVersionInstalled" = "Y" |
Note The update for supported versions of Windows XP Professional x64 Edition also applies to supported versions of Windows Server 2003 x64 Edition.
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.
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /? | Displays help on supported switches. |
| /quiet | Quiet mode, no user input required or output shown. |
| /v | Turns on verbose mode |
| /log | Turns on logging and creates log file in specified location.\ e.g. /log <full path to log file> |
| /passive | Installs and shows progress bar advancing but requires no user interaction. |
| /norestart | If any of the patches required restart, neither prompt nor cause a restart. |
| /promptrestart | If any of the patches required restart, prompt for restart after install, and trigger restart if user agrees. |
| /extract | Extract the package. |
| /uninstall | Uninstalls the security update. |
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 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 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 Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Server 2003 Service Pack 2:\ NDP35SP1-KB2736416-x86.exe /quiet |
| For Microsoft .NET Framework 4 when installed on Windows Server 2003 Service Pack 2:\ NDP40-KB2736428-x86.exe /quiet | |
| Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Server 2003 x64 Edition Service Pack 2:\ NDP35SP1-KB2736416-x64.exe /quiet | |
| Microsoft .NET Framework 4 when installed on Windows Server 2003 x64 Edition Service Pack 2:\ NDP40-KB2736428-x64.exe /quiet | |
| Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Server 2003 with SP2 for Itanium-based Systems:\ NDP35SP1-KB2736416-IA64.exe /quiet | |
| Microsoft .NET Framework 4 when installed on Windows Server 2003 with SP2 for Itanium-based Systems:\ NDP40-KB2736428-IA64.exe /quiet | |
| Installing without restarting | For Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Server 2003 Service Pack 2:\ NDP35SP1-KB2736416-x86.exe /norestart |
| For Microsoft .NET Framework 4 when installed on Windows Server 2003 Service Pack 2:\ NDP40-KB2736428-x86.exe /norestart | |
| Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Server 2003 x64 Edition Service Pack 2:\ NDP35SP1-KB2736416-x64.exe /norestart | |
| Microsoft .NET Framework 4 when installed on Windows Server 2003 x64 Edition Service Pack 2:\ NDP40-KB2736428-x64.exe /norestart | |
| Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Server 2003 with SP2 for Itanium-based Systems:\ NDP35SP1-KB2736416-IA64.exe /norestart | |
| Microsoft .NET Framework 4 when installed on Windows Server 2003 with SP2 for Itanium-based Systems:\ NDP40-KB2736428-IA64.exe /norestart | |
| Update log file | For Microsoft .NET Framework 3.5 Service Pack 1:\ Microsoft .NET Framework 3.5-KB2736416_*-msi0.txt\ Microsoft .NET Framework 3.5-KB2736416_*.html |
| For Microsoft .NET Framework 4:\ KB2736428_*_*-Microsoft .NET Framework 4 Client Profile-MSP0.txt\ KB2736428_*_*.html | |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.\ \ To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
| HotPatching | This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341. |
| Removal Information | For all supported versions of Microsoft .NET Framework, use the Add or Remove Programs item in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 2736416\ See Microsoft Knowledge Base Article 2736428 |
| Registry Key Verification | Microsoft .NET Framework 3.5 Service Pack 1\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 3.5 Service Pack 1\SP1\KB2736416\ "ThisVersionInstalled" = "Y" |
| For Microsoft .NET Framework 4 when installed on all supported 32-bit editions of Windows Server 2003:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2736428\ "ThisVersionInstalled" = "Y" | |
| For Microsoft .NET Framework 4 when installed on all x64-based and Itanium-based editions of Windows Server 2003:\ HKEY_LOCAL_MACHINE\SOFTWARE\ Wow6432Node\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2736428\ "ThisVersionInstalled" = "Y" |
Note The update for supported versions of Windows Server 2003 x64 Edition also applies to supported versions of Windows XP Professional x64 Edition.
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.
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /? | Displays help on supported switches. |
| /quiet | Quiet mode, no user input required or output shown. |
| /v | Turns on verbose mode |
| /log | Turns on logging and creates log file in specified location.\ e.g. /log <full path to log file> |
| /passive | Installs and shows progress bar advancing but requires no user interaction. |
| /norestart | If any of the patches required restart, neither prompt nor cause a restart. |
| /promptrestart | If any of the patches required restart, prompt for restart after install, and trigger restart if user agrees. |
| /extract | Extract the package. |
| /uninstall | Uninstalls the security update. |
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 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 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 3.5 Service Pack 1 when installed on Windows Vista Service Pack 2:\ NDP35SP1-KB2736416-x86.exe /quiet |
| For Microsoft .NET Framework 4 when installed on Windows Vista Service Pack 2:\ NDP40-KB2736428-x86.exe /quiet | |
| For Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Vista x64 Edition Service Pack 2:\ NDP35SP1-KB2736416-x64.exe /quiet | |
| For Microsoft .NET Framework 4 when installed on Windows Vista x64 Edition Service Pack 2:\ NDP40-KB2736428-x64.exe /quiet | |
| Installing without restarting | For Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Vista Service Pack 2:\ NDP35SP1-KB2736416-x86.exe /norestart |
| For Microsoft .NET Framework 4 when installed on Windows Vista Service Pack 2:\ NDP40-KB2736428-x86.exe /norestart | |
| For Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Vista x64 Edition Service Pack 2:\ NDP35SP1-KB2736416-x64.exe /norestart | |
| For Microsoft .NET Framework 4 when installed on Windows Vista x64 Edition Service Pack 2:\ NDP40-KB2736428-x64.exe /norestart | |
| Update log file | For Microsoft .NET Framework 3.5 Service Pack 1:\ Microsoft .NET Framework 3.5-KB2736416_*-msi0.txt\ Microsoft .NET Framework 3.5-KB2736416_*.html |
| For Microsoft .NET Framework 4:\ KB2736428_*_*-Microsoft .NET Framework 4 Client Profile-MSP0.txt\ KB2736428_*_*.html | |
| 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 | For all supported versions of Microsoft .NET Framework, use the Add or Remove Programs item in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 2736416\ See Microsoft Knowledge Base Article 2736428 |
| Registry Key Verification | For Microsoft .NET Framework 3.5 Service Pack 1:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 3.5 Service Pack 1\SP1\KB2736416\ "ThisVersionInstalled" = "Y" |
| For Microsoft .NET Framework 4 when installed on all supported 32-bit editions of Windows Vista:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2736428\ "ThisVersionInstalled" = "Y" | |
| For Microsoft .NET Framework 4 when installed on all supported x64-based and Itanium-based editions of Windows Vista:\ HKEY_LOCAL_MACHINE\SOFTWARE\ Wow6432Node\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2736428\ "ThisVersionInstalled" = "Y" |
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.
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /? | Displays help on supported switches. |
| /quiet | Quiet mode, no user input required or output shown. |
| /v | Turns on verbose mode |
| /log | Turns on logging and creates log file in specified location.\ e.g. /log <full path to log file> |
| /passive | Installs and shows progress bar advancing but requires no user interaction. |
| /norestart | If any of the patches required restart, neither prompt nor cause a restart. |
| /promptrestart | If any of the patches required restart, prompt for restart after install, and trigger restart if user agrees. |
| /extract | Extract the package. |
| /uninstall | Uninstalls the security update. |
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 enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
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. - Finally, you can also click 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 3.5 Service Pack 1 when installed on Windows Server 2008 for 32-bit Systems Service Pack 2:\ NDP35SP1-KB2736416-x86.exe /quiet |
| For Microsoft .NET Framework 4 when installed on all supported 32-bit editions of Windows Server 2008:\ NDP40-KB2736428-x86.exe /quiet | |
| For Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Server 2008 for x64-based Systems Service Pack 2:\ NDP35SP1-KB2736416-x64.exe /quiet | |
| For Microsoft .NET Framework 4 when installed on Windows Server 2008 for x64-based Systems Service Pack 2:\ NDP40-KB2736428-x64.exe /quiet | |
| For Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Server 2008 for Itanium-based Systems Service Pack 2:\ NDP35SP1-KB2736416-IA64.exe /quiet | |
| For Microsoft .NET Framework 4 when installed on all supported Itanium-based editions of Windows Server 2008:\ NDP40-KB2736428-IA64.exe /quiet | |
| Installing without restarting | For Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Server 2008 for 32-bit Systems Service Pack 2:\ NDP35SP1-KB2736416-x86.exe /norestart |
| For Microsoft .NET Framework 4 when installed on all supported 32-bit editions of Windows Server 2008:\ NDP40-KB2736428-x86.exe /norestart | |
| For Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Server 2008 for x64-based Systems Service Pack 2:\ NDP35SP1-KB2736416-x64.exe /norestart | |
| For Microsoft .NET Framework 4 when installed on Windows Server 2008 for x64-based Systems Service Pack 2:\ NDP40-KB2736428-x64.exe /norestart | |
| For Microsoft .NET Framework 3.5 Service Pack 1 when installed on Windows Server 2008 for Itanium-based Systems Service Pack 2:\ NDP35SP1-KB2736416-IA64.exe /norestart | |
| For Microsoft .NET Framework 4 when installed on all supported Itanium-based editions of Windows Server 2008:\ NDP40-KB2736428-IA64.exe /norestart | |
| Update log file | For Microsoft .NET Framework 3.5 Service Pack 1:\ Microsoft .NET Framework 3.5-KB2736416_*-msi0.txt\ Microsoft .NET Framework 3.5-KB2736416_*.html |
| For Microsoft .NET Framework 4:\ KB2736428_*_*-Microsoft .NET Framework 4 Client Profile-MSP0.txt\ KB2736428_*_*.html | |
| 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 | For all supported versions of Microsoft .NET Framework, use the Add or Remove Programs item in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 2736416\ See Microsoft Knowledge Base Article 2736428 |
| Registry Key Verification | For Microsoft .NET Framework 3.5 Service Pack 1:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 3.5 Service Pack 1\SP1\KB2736416\ "ThisVersionInstalled" = "Y" |
| For Microsoft .NET Framework 4 when installed on all supported 32-bit editions of Windows Server 2008: \ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2736428\ "ThisVersionInstalled" = "Y" | |
| For Microsoft .NET Framework 4 when installed on all supported x64-based and Itanium-based editions of Windows Server 2008: \ HKEY_LOCAL_MACHINE\SOFTWARE\ Wow6432Node\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2736428\ "ThisVersionInstalled" = "Y" |
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.
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /? | Displays help on supported switches. |
| /quiet | Quiet mode, no user input required or output shown. |
| /v | Turns on verbose mode |
| /log | Turns on logging and creates log file in specified location.\ e.g. /log <full path to log file> |
| /passive | Installs and shows progress bar advancing but requires no user interaction. |
| /norestart | If any of the patches required restart, neither prompt nor cause a restart. |
| /promptrestart | If any of the patches required restart, prompt for restart after install, and trigger restart if user agrees. |
| /extract | Extract the package. |
| /uninstall | Uninstalls the security update. |
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 enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
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. - Finally, you can also click 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 7 (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 3.5.1 on Windows 7 for 32-bit Systems:\ Windows6.1-KB2736418-x86.msu /quiet |
| For Microsoft .NET Framework 3.5.1 on Windows 7 for 32-bit Systems Service Pack 1:\ Windows6.1-KB2736422-x86.msu /quiet | |
| For Microsoft .NET Framework 4 when installed on Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1:\ NDP40-KB2736428-x86.exe /quiet | |
| For Microsoft .NET Framework 3.5.1 on Windows 7 for x64-based Systems:\ Windows6.1-KB2736418-x64.msu /quiet | |
| For Microsoft .NET Framework 3.5.1 on Windows 7 for x64-based Systems Service Pack 1:\ Windows6.1-KB2736422-x64.msu /quiet | |
| For Microsoft .NET Framework 4 when installed on Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1:\ NDP40-KB2736428-x64.exe /quiet | |
| Installing without restarting | For Microsoft .NET Framework 3.5.1 on Windows 7 for 32-bit Systems:\ Windows6.1-KB2736418-x86.msu /quiet /norestart |
| For Microsoft .NET Framework 3.5.1 on Windows 7 for 32-bit Systems Service Pack 1:\ Windows6.1-KB2736422-x86.msu /quiet /norestart | |
| For Microsoft .NET Framework 4 when installed on Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1:\ NDP40-KB2736428-x86.exe /norestart | |
| For Microsoft .NET Framework 3.5.1 on Windows 7 for x64-based Systems:\ Windows6.1-KB2736418-x64.msu /quiet /norestart | |
| For Microsoft .NET Framework 3.5.1 on Windows 7 for x64-based Systems Service Pack 1:\ Windows6.1-KB2736422-x64.msu /quiet /norestart | |
| For Microsoft .NET Framework 4 when installed on Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1:\ NDP40-KB2736428-x64.exe /norestart | |
| Update log file | For Microsoft .NET Framework 4:\ KB2736428_*_*-Microsoft .NET Framework 4 Client Profile-MSP0.txt\ KB2736428_*_*.html |
| 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 | For all supported versions of Microsoft .NET Framework, use the Add or Remove Programs item in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 2736418\ See Microsoft Knowledge Base Article 2736422\ See Microsoft Knowledge Base Article 2736428 |
| Registry Key Verification | For Microsoft .NET Framework 3.5.1:\ Note A registry key does not exist to validate the presence of this update. |
| For Microsoft .NET Framework 4 when installed on all supported 32-bit editions of Windows 7:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2736428\ "ThisVersionInstalled" = "Y" | |
| For Microsoft .NET Framework 4 when installed on all supported x64-based editions of Windows 7:\ HKEY_LOCAL_MACHINE\SOFTWARE\ Wow6432Node\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2736428\ "ThisVersionInstalled" = "Y" |
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.
The security updates for Microsoft .NET Framework 3.5.1 support 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 "Windows Update Stand-alone Installer" in the TechNet article, Miscellaneous Changes in Windows 7.
The security updates for Microsoft .NET Framework 4 support the following setup switches.
| Switch | Description |
|---|---|
| /? | Displays help on supported switches. |
| /quiet | Quiet mode, no user input required or output shown. |
| /v | Turns on verbose mode |
| /log | Turns on logging and creates log file in specified location.\ e.g. /log <full path to log file> |
| /passive | Installs and shows progress bar advancing but requires no user interaction. |
| /norestart | If any of the patches required restart, neither prompt nor cause a restart. |
| /promptrestart | If any of the patches required restart, prompt for restart after install, and trigger restart if user agrees. |
| /extract | Extract the package. |
| /uninstall | Uninstalls the security update. |
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 enter an update file name in the Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
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. - Finally, you can also click 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 R2 (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 3.5.1 on Windows Server 2008 R2 for x64-based Systems:\ Windows6.1-KB2736418-x64.msu /quiet |
| For Microsoft .NET Framework 3.5.1 on Windows Server 2008 R2 for x64-based Systems Service Pack 1:\ Windows6.1- KB2736422--x64.msu /quiet | |
| For Microsoft .NET Framework 3.5.1 on Windows Server 2008 R2 for Itanium-based Systems:\ Windows6.1-KB2736418-ia64.msu /quiet | |
| For Microsoft .NET Framework 3.5.1 on Windows Server 2008 R2 for Itanium-based Systems Service Pack 1:\ Windows6.1- KB2736422-ia64.msu /quiet | |
| For Microsoft .NET Framework 4 when installed on Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1:\ NDP40-KB2736428-x64.exe /quiet | |
| For Microsoft .NET Framework 4 when installed on Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1:\ NDP40-KB2736428-IA64.exe /quiet | |
| Installing without restarting | For Microsoft .NET Framework 3.5.1 on Windows Server 2008 R2 for x64-based Systems:\ Windows6.1-KB2736418-x64.msu /quiet |
| For Microsoft .NET Framework 3.5.1 on Windows Server 2008 R2 for x64-based Systems Service Pack 1:\ Windows6.1-KB2736422-x64.msu /quiet /norestart | |
| For Microsoft .NET Framework 3.5.1 on Windows Server 2008 R2 for Itanium-based Systems:\ Windows6.1-KB2736418-ia64.msu /quiet /norestart | |
| For Microsoft .NET Framework 3.5.1 on Windows Server 2008 R2 for Itanium-based Systems Service Pack 1:\ Windows6.1- KB2736422-ia64.msu /quiet /norestart | |
| For Microsoft .NET Framework 4 when installed on Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1:\ NDP40-KB2736428-x64.exe /norestart | |
| For Microsoft .NET Framework 4 when installed on Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1:\ NDP40-KB2736428-IA64.exe /norestart | |
| Update log file | For Microsoft .NET Framework 4:\ KB2736428_*_*-Microsoft .NET Framework 4 Client Profile-MSP0.txt\ KB2736428_*_*.html |
| 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 | For all supported versions of Microsoft .NET Framework, use the Add or Remove Programs item in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 2736418\ See Microsoft Knowledge Base Article 2736422\ See Microsoft Knowledge Base Article 2736428 |
| Registry Key Verification | For Microsoft .NET Framework 3.5.1:\ Note A registry key does not exist to validate the presence of this update. |
| For Microsoft .NET Framework 4 when installed on all supported x64-based and Itanium-based editions of Windows Server 2008 R2:\ HKEY_LOCAL_MACHINE\SOFTWARE\ Wow6432Node\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2736428\ "ThisVersionInstalled" = "Y" |
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.
The security updates for Microsoft .NET Framework 3.5.1 support 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 "Windows Update Stand-alone Installer" in the TechNet article, Miscellaneous Changes in Windows 7.
The security updates for Microsoft .NET Framework 4 support the following setup switches.
| Switch | Description |
|---|---|
| /? | Displays help on supported switches. |
| /quiet | Quiet mode, no user input required or output shown. |
| /v | Turns on verbose mode |
| /log | Turns on logging and creates log file in specified location.\ e.g. /log <full path to log file> |
| /passive | Installs and shows progress bar advancing but requires no user interaction. |
| /norestart | If any of the patches required restart, neither prompt nor cause a restart. |
| /promptrestart | If any of the patches required restart, prompt for restart after install, and trigger restart if user agrees. |
| /extract | Extract the package. |
| /uninstall | Uninstalls the security update. |
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 enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
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. - Finally, you can also click 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 8 (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 3.5 on Windows 8 for 32-bit Systems:\ Windows8-RT-KB2736693-x86.msu /quiet |
| For Microsoft .NET Framework 3.5 on Windows 8 for 64-bit Systems:\ Windows8-RT-KB2736693-x64.msu /quiet | |
| Installing without restarting | For Microsoft .NET Framework 3.5 on Windows 8 for 32-bit Systems:\ Windows8-RT-KB2736693-x86.msu /quiet /norestart |
| For Microsoft .NET Framework 3.5 on Windows 8 for 64-bit Systems:\ Windows8-RT-KB2736693-x64.msu /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 | For all supported versions of Microsoft .NET Framework, use the Add or Remove Programs item in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 2736693 |
| Registry Key Verification | For Microsoft .NET Framework 3.5:\ 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.
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 "Windows Update Stand-alone Installer" in the TechNet article, Miscellaneous Changes in Windows 7.
Verifying That the Update Has Been Applied
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 enter an update file name in the Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
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. - Finally, you can also click 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 2012 (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 3.5 on Windows Server 2012:\ Windows8-RT-KB2736693-x64.msu /quiet |
| For Management OData IIS Extension when installed on Windows Server 2012:\ Windows8-RT-KB2753596-x64.msu /quiet | |
| Installing without restarting | For Microsoft .NET Framework 3.5 on Windows Server 2012:\ Windows8-RT-KB2736693-x64.msu /quiet /norestart |
| For Management OData IIS Extension when installed on Windows Server 2012:\ Windows8-RT-KB2753596-x64.msu /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 | For all supported versions of Microsoft .NET Framework, use the Add or Remove Programs item in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 2736693\ See Microsoft Knowledge Base Article 2753596 |
| Registry Key Verification | For Microsoft .NET Framework 3.5:\ Note A registry key does not exist to validate the presence of this update. |
| For Management OData IIS Extension when installed on Windows Server 2012:\ 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.
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 "Windows Update Stand-alone Installer" in the TechNet article, Miscellaneous Changes in Windows 7.
Verifying That the Update Has Been Applied
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 enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
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. - Finally, you can also click 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 go to the active protections websites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.
Support
How to obtain help and support for this security update
- Help installing updates: Support for Microsoft Update
- Security solutions for IT professionals: TechNet Security Troubleshooting and Support
- Help protect your computer that is running Windows from viruses and malware: Virus Solution and Security Center
- Local support according to your country: International Support
Disclaimer
The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Revisions
- V1.0 (January 8, 2013): Bulletin published.
- V1.1 (April 3, 2013): Added a mitigation to CVE-2013-0005 for systems running Windows Server 2012.
Built at 2014-04-18T13:49:36Z-07:00