Security Bulletin
Microsoft Security Bulletin MS12-020 - Critical
Vulnerabilities in Remote Desktop Could Allow Remote Code Execution (2671387)
Published: March 13, 2012 | Updated: July 31, 2012
Version: 2.1
General Information
Executive Summary
This security update resolves two privately reported vulnerabilities in the Remote Desktop Protocol. The more severe of these vulnerabilities could allow remote code execution if an attacker sends a sequence of specially crafted RDP packets to an affected system. By default, the Remote Desktop Protocol (RDP) is not enabled on any Windows operating system. Systems that do not have RDP enabled are not at risk.
This security update is rated Critical for all supported releases of Microsoft Windows. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerabilities by modifying the way that the Remote Desktop Protocol processes packets in memory and the way that the RDP service processes packets. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. The majority of customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.
For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update immediately 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 2671387 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues.
Affected and Non-Affected Software
The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.
Affected Software
| Operating System | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by this Update |
|---|---|---|---|
| Windows XP Service Pack 3\ (KB2621440) | Remote Code Execution | Critical | KB2570222 in MS11-065 replaced by KB2621440 |
| Windows XP Professional x64 Edition Service Pack 2\ (KB2621440) | Remote Code Execution | Critical | KB2570222 in MS11-065 replaced by KB2621440 |
| Windows Server 2003 Service Pack 2\ (KB2621440) | Remote Code Execution | Critical | KB2570222 in MS11-065 replaced by KB2621440 |
| Windows Server 2003 x64 Edition Service Pack 2\ (KB2621440) | Remote Code Execution | Critical | KB2570222 in MS11-065 replaced by KB2621440 |
| Windows Server 2003 with SP2 for Itanium-based Systems\ (KB2621440) | Remote Code Execution | Critical | KB2570222 in MS11-065 replaced by KB2621440 |
| Windows Vista Service Pack 2\ (KB2621440) | Remote Code Execution | Critical | No bulletin replaced by KB2621440 |
| Windows Vista x64 Edition Service Pack 2\ (KB2621440) | Remote Code Execution | Critical | No bulletin replaced by KB2621440 |
| Windows Server 2008 for 32-bit Systems Service Pack 2*\ (KB2621440) | Remote Code Execution | Critical | No bulletin replaced by KB2621440 |
| Windows Server 2008 for x64-based Systems Service Pack 2*\ (KB2621440) | Remote Code Execution | Critical | No bulletin replaced by KB2621440 |
| Windows Server 2008 for Itanium-based Systems Service Pack 2\ (KB2621440) | Remote Code Execution | Critical | No bulletin replaced by KB2621440 |
| Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1\ (KB2621440)\ \ Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1\ (KB2667402) | Remote Code Execution | Critical[1] | No bulletin replaced by KB2621440\ \ \ No bulletin replaced by KB2667402 |
| Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1\ (KB2621440)\ \ Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1\ (KB2667402) | Remote Code Execution | Critical[1] | No bulletin replaced by KB2621440\ \ \ \ No bulletin replaced by KB2667402 |
| Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1*\ (KB2621440)\ \ Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1*\ (KB2667402) | Remote Code Execution | Critical[1] | No bulletin replaced by KB2621440\ \ \ \ No bulletin replaced by KB2667402 |
| Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1\ (KB2621440)\ \ Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1\ (KB2667402) | Remote Code Execution | Critical[1] | No bulletin replaced by KB2621440\ \ \ \ No bulletin replaced by KB2667402 |
*Server Core installation affected. This update applies, with the same severity rating, to supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, whether or not installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, Managing a Server Core Installation and Servicing a Server Core Installation. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.
[1]Update package KB2621440 addresses CVE-2012-0002 and update package KB2667402 addresses CVE-2012-0152. While CVE-2012-0152 has a lower severity rating than KB2621440 on affected versions of Microsoft Windows, the aggregate severity rating is Critical based on CVE-2012-0002. Customers should apply all updates offered for the version of Microsoft Windows installed on their systems.
Frequently Asked Questions (FAQ) Related to This Security Update
Why was this bulletin rereleased on June 12, 2012?
Microsoft rereleased this bulletin to reoffer security update KB2667402 for all editions of Windows 7 and Windows Server 2008 R2. The new offering of this update addresses an issue with the update originally offered on March 13, 2012, where the update is installed on Windows 7 or Windows Server 2008 R2 and then the operating system is subsequently updated to Service Pack 1. This scenario results in the incorrect binary version of rdpcorekmts.dll (6.1.7600.16952) being installed instead of the correct version (6.1.7601.17514). Systems running supported editions of Windows 7 and Windows Server 2008 R2 will automatically be offered the new version of this update. Customers using these operating systems, including those who have already successfully installed the update originally offered on March 13, 2012, should install the reoffered 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.
Is Windows Developer Preview affected by any of the vulnerabilities addressed in this bulletin?
Yes. The KB2621440 update is available for the Windows Developer Preview release. Customers with Windows Developer Preview are encouraged to apply the update to their systems. The update is only available on Windows Update.
I'm running an affected operating system, but I do not have Remote Desktop Protocol (RDP) enabled. Will I still be offered this update?
Yes. Although systems that do not have RDP enabled are not at risk from the vulnerabilities, customers who have not enabled RDP will still be offered this update in order to help ensure the protection of their systems.
There are two updates listed for the version of Microsoft Windows on my system. Do I need to install both updates? Yes. Customers should apply all updates offered for the version of Microsoft Windows installed on their systems.
Do I need to install these security updates in a particular sequence?
No. Multiple updates for one affected system can be applied in any sequence.
I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. For more information about the product lifecycle, visit the Microsoft Support Lifecycle 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, visit 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 March bulletin summary. For more information, see Microsoft Exploitability Index.
| Affected Software | Remote Desktop Protocol Vulnerability - CVE-2012-0002 (KB2621440) | Terminal Server Denial of Service Vulnerability - CVE-2012-0152 (KB2667402) | Aggregate Severity Rating |
|---|---|---|---|
| Windows XP Service Pack 3 | Critical \ Remote Code Execution | Not applicable | Critical |
| Windows XP Professional x64 Edition Service Pack 2 | Critical \ Remote Code Execution | Not applicable | Critical |
| Windows Server 2003 Service Pack 2 | Critical \ Remote Code Execution | Not applicable | Critical |
| Windows Server 2003 x64 Edition Service Pack 2 | Critical \ Remote Code Execution | Not applicable | Critical |
| Windows Server 2003 with SP2 for Itanium-based Systems | Critical \ Remote Code Execution | Not applicable | Critical |
| Windows Vista Service Pack 2 | Critical \ Remote Code Execution | Not applicable | Critical |
| Windows Vista x64 Edition Service Pack 2 | Critical \ Remote Code Execution | Not applicable | Critical |
| Windows Server 2008 for 32-bit Systems Service Pack 2* | Critical \ Remote Code Execution | Not applicable | Critical |
| Windows Server 2008 for x64-based Systems Service Pack 2* | Critical \ Remote Code Execution | Not applicable | Critical |
| Windows Server 2008 for Itanium-based Systems Service Pack 2 | Critical \ Remote Code Execution | Not applicable | Critical |
| Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 | Critical \ Remote Code Execution | Moderate \ Denial of Service | Critical |
| Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 | Critical \ Remote Code Execution | Moderate \ Denial of Service | Critical |
| Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1* | Critical \ Remote Code Execution | Important \ Denial of Service | Critical |
| Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | Critical \ Remote Code Execution | Important \ Denial of Service | Critical |
*Server Core installation affected. This update applies, with the same severity rating, to supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, whether or not installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, Managing a Server Core Installation and Servicing a Server Core Installation. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.
Remote Desktop Protocol Vulnerability - CVE-2012-0002
A remote code execution vulnerability exists in the way that the Remote Desktop Protocol accesses an object in memory that has been improperly initialized or has been deleted. An attacker who successfully exploited this vulnerability could run arbitrary code on the target system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2012-0002.
Mitigating Factors for Remote Desktop Protocol Vulnerability - CVE-2012-0002
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:
- By default, the Remote Desktop Protocol is not enabled on any Windows operating system. Systems that do not have RDP enabled are not at risk. Note that on Windows XP and Windows Server 2003, Remote Assistance can enable RDP.
- 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 connected directly to the Internet have a minimal number of ports exposed.
Workarounds for Remote Desktop Protocol Vulnerability - CVE-2012-0002
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:
Disable Terminal Services, Remote Desktop, Remote Assistance, and Windows Small Business Server 2003 Remote Web Workplace feature if no longer required
If you no longer need these services on your system, consider disabling them as a security best practice. Disabling unused and unneeded services helps reduce your exposure to security vulnerabilities.
For information about how to disable Remote Desktop manually, see To disable Remote Desktop.
For information about how to disable Remote Desktop by using Group Policy, see Microsoft Knowledge Base Article 306300.
For information about Remote Assistance, including instructions on how to disable Remote Assistance manually and by using Group Policy, see the TechNet article, Remote Assistance.
For information about how to disable the Windows Small Business Server 2003 Terminal Services and Remote Web Workplace features, see the TechNet article, Securing Your Windows Small Business Server 2003 Network.
Block TCP port 3389 at the enterprise perimeter firewall
TCP port 3389 is used to initiate a connection with the affected component. Blocking this port at the network perimeter firewall will help protect systems that are behind that firewall from attempts to exploit this vulnerability. This can help protect networks from attacks that originate outside the enterprise perimeter. Blocking the affected ports at the enterprise perimeter is the best defense to help avoid Internet-based attacks. However, systems could still be vulnerable to attacks from within their enterprise perimeter.
Additionally, on Windows XP and Windows Server 2003, the Windows Firewall can help protect individual systems. By default, the Windows Firewall does not allow connections to this port, except in Windows XP Service Pack 2 when the Remote Desktop feature is enabled. For information about how to disable the Windows Firewall exception for Remote Desktop on these platforms, see the TechNet article, Enable or Disable the Remote Desktop Firewall Rule. If you cannot disable the Windows Firewall exception for Remote Desktop, you may be able to reduce the scope of this vulnerability by setting the default value of all computers (including those on the Internet), to the local network. Doing this helps reduce the likelihood of attacks from the Internet.
Note Windows Small Business Server 2003 uses a feature named Remote Web Workplace. This feature uses TCP port 4125 to listen for RDP connections. If you are using this feature, you should validate that this port is also blocked from the Internet in addition to port 3389.
Note It is possible to manually change the affected components to use other ports. If you have performed these actions, you should also block those additional ports.
Enable Network Level Authentication on systems running supported editions of Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2
Note See Microsoft Knowledge Base Article 2671387 to use the automated Microsoft Fix it solution to enable this workaround.
You can enable Network Level Authentication to block unauthenticated attackers from exploiting this vulnerability. With Network Level Authentication turned on, an attacker would first need to authenticate to Remote Desktop Services using a valid account on the target system before the attacker could exploit the vulnerability.
In order to use Network Level Authentication, your environment must meet the following requirements:
- The client computer must be using at least Remote Desktop Connection 6.0.
- The client computer must be using an operating system, such as Windows 7 or Windows Vista that supports the Credential Security Support Provider (CredSSP) protocol.
- The RD Session Host server must be running Windows Server 2008 R2 or Windows Server 2008.
To configure Network Level Authentication for a connection, perform the following steps:
- On the RD Session Host server, open Remote Desktop Session Host Configuration. To open Remote Desktop Session Host Configuration, click Start, point to AdministrativeTools, point to Remote Desktop Services, and then click Remote Desktop Session Host Configuration.
- Under Connections, right-click the name of the connection, and then click Properties.
- On the General tab, select the Allow connections only from computers running Remote Desktop with Network Level Authentication check box.
If the Allow connections only from computers running Remote Desktop with Network Level Authentication check box is selected and is not enabled, the Require user authentication for remote connections by using Network Level Authentication Group Policy setting has been enabled and has been applied to the RD Session Host server. - Click OK.
Impact of workaround. Client computers that do not support Credential Security Support Provider (CredSSP) protocol will not be able to access servers protected with Network Level Authentication. Note For administrators deploying this workaround in a mixed network environment where Windows XP Service Pack 3 systems need to use Remote Desktop, see Microsoft Knowledge Base Article 951608 for information on how to enable CredSSP in Windows XP Service Pack 3.
For more information regarding Network Level Authentication, including how to enable Network Level Authentication using Group Policy, see the Technet article, Configure Network Level Authentication for Remote Desktop Services Connections.
FAQ for Remote Desktop Protocol Vulnerability - CVE-2012-0002
What is the scope of the vulnerability?
This is a remote code execution vulnerability.
What causes the vulnerability?
The vulnerability is caused when the Remote Desktop Protocol processes a sequence of specially crafted packets, resulting in the access of an object in memory that has not been properly initialized or has been deleted.
What is the Remote Desktop Protocol (RDP)?
Remote Desktop Protocol (RDP) lets users create a virtual session on their desktop computers. RDP allows remote users to access all of the data and applications on their computers. For more information, see the MSDN article, Remote Desktop Protocol.
Is remote desktop enabled by default?
No, RDP for administration is not enabled by default. However, customers who have not enabled RDP will still be offered this update in order to help ensure the protection of their systems. For more information regarding this configuration setting, see the TechNet article, How to enable and to configure Remote Desktop for Administration in Windows Server 2003.
What is Network Level Authentication for Remote Desktop Services?
Network Level Authentication is an authentication method that can be used to enhance RD Session Host server security by requiring that the user be authenticated to the RD Session Host server before a session is created. For more information regarding Network Level Authentication, please see the TechNet article, Configure Network Level Authentication for Remote Desktop Services Connections.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
How could an attacker exploit the vulnerability?
For systems running supported editions of Windows XP and Windows Server 2003, a remote unauthenticated attacker could exploit this vulnerability by sending a sequence of specially crafted RDP packets to the target system.
For systems running supported editions of Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2 with Network Level Authentication turned off, a remote unauthenticated attacker could exploit this vulnerability by sending a sequence of specially crafted RDP packets to the target system.
For systems running supported editions of Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2 with Network Level Authentication turned on, an attacker would first need to authenticate to Remote Desktop Services using a valid account on the target system. Then, the attacker could exploit this vulnerability by sending a sequence of specially crafted RDP packets to the target system.
What systems are primarily at risk from the vulnerability?
Terminal servers are primarily at risk from this vulnerability. Systems that do not have RDP enabled are not at risk. Additionally, systems running supported editions of Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2 that have Network Level Authentication enabled are at reduced risk as an attacker would first need to be authenticated to the service.
What does the update do?
The update addresses the vulnerability by modifying the way that the Remote Desktop Protocol processes packets in memory.
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.
Terminal Server Denial of Service Vulnerability - CVE-2012-0152
A denial of service vulnerability exists in the way that the Remote Desktop Protocol service processes packets. An attacker who successfully exploited this vulnerability could cause the target service to stop responding.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2012-0152.
Mitigating Factors for Terminal Server Denial of Service Vulnerability - CVE-2012-0152
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:
- By default, the Remote Desktop Protocol is not enabled on any Windows operating system. Systems that do not have RDP enabled are not at risk.
- 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 connected directly to the Internet have a minimal number of ports exposed.
Workarounds for Terminal Server Denial of Service Vulnerability - CVE-2012-0152
Microsoft has not identified any workarounds for this vulnerability.
FAQ for Terminal Server Denial of Service Vulnerability - CVE-2012-0152
What is the scope of the vulnerability?
This is a denial of service vulnerability.
What causes the vulnerability?
The vulnerability is caused when the Remote Desktop Protocol service processes a sequence of specially crafted packets, resulting in a condition where the service stops responding.
What is the Remote Desktop Protocol (RDP)?
Remote Desktop Protocol (RDP) lets users create a virtual session on their desktop computers. RDP allows remote users to access all of the data and applications on their computers. For more information, see the MSDN article, Remote Desktop Protocol.
Is remote desktop enabled by default?
No, RDP for administration is not enabled by default. However, customers who have not enabled RDP will still be offered this update in order to help ensure the protection of their systems. For more information regarding this configuration setting, see the TechNet article, How to enable and to configure Remote Desktop for Administration in Windows Server 2003.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could cause the RDP service to stop responding.
How could an attacker exploit the vulnerability?
A remote unauthenticated attacker could exploit this vulnerability by sending a sequence of specially crafted packets to the target system.
What systems are primarily at risk from the vulnerability?
Terminal servers are primarily at risk from this vulnerability. Systems that do not have RDP enabled are not at risk.
What does the update do?
The update addresses the vulnerability by modifying the way that the RDP service processes packets.
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, "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.
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) 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.
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 |
Note For customers using legacy software not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, please visit 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 | Configuration Manager 2007 |
|---|---|---|
| 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 |
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 2007. 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 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.
For more information about SMS, visit the SMS website.
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 Windows XP Service Pack 3:\ WindowsXP-KB2621440-x86-ENU.exe /quiet |
| For Windows XP Professional x64 Edition Service Pack 2:\ WindowsServer2003.WindowsXP-KB2621440-x64-ENU.exe /quiet | |
| Installing without restarting | For Windows XP Service Pack 3:\ WindowsXP-KB2621440-x86-ENU.exe /norestart |
| For Windows XP Professional x64 Edition Service Pack 2:\ WindowsServer2003.WindowsXP-KB2621440-x64-ENU.exe /norestart | |
| Update log file | KB2621440.log |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | Yes, you must restart your system after you apply this security update. |
| HotPatching | Not applicable |
| Removal Information | Use Add or Remove Programs item in Control Panel or the Spuninst.exe utility located in the %Windir%$NTUninstallKB2621440$\Spuninst folder |
| File Information | See Microsoft Knowledge Base Article 2621440 |
| Registry Key Verification | For all supported 32-bit editions of Windows XP:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2621440\Filelist |
| For all supported x64-based editions of Windows XP:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB2621440\Filelist |
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.
If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the installer, see Microsoft Knowledge Base Article 832475.
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 |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Displays a dialog box prompting the local user to allow a restart. |
| Special Options | |
| /overwriteoem | Overwrites OEM files without prompting. |
| /nobackup | Does not back up files needed for uninstall. |
| /forceappsclose | Forces other programs to close when the computer shuts down. |
| /log:path | Allows the redirection of installation log files. |
| /integrate:path | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. |
| /extract[:path] | Extracts files without starting the Setup program. |
| /ER | Enables extended error reporting. |
| /verbose | Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Displays a dialog box prompting the local user to allow a restart. |
| Special Options | |
| /forceappsclose | Forces other programs to close when the computer shuts down. |
| /log:path | Allows the redirection of installation log files. |
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Windows Server 2003 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
|---|---|
| Deployment | |
| Installing without user intervention | For all supported 32-bit editions of Windows Server 2003: WindowsServer2003-KB2621440-x86-ENU.exe /quiet |
| For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB2621440-x64-ENU.exe /quiet | |
| For all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB2621440-ia64-ENU.exe /quiet | |
| Installing without restarting | For all supported 32-bit editions of Windows Server 2003: WindowsServer2003-KB2621440-x86-ENU.exe /norestart |
| For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB2621440-x64-ENU.exe /norestart | |
| For all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB2621440-ia64-ENU.exe /norestart | |
| Update log file | KB2621440.log |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | Yes, you must restart your system after you apply this security update. |
| HotPatching | This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341. |
| Removal Information | Use Add or Remove Programs item in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB2621440$\Spuninst folder |
| File Information | See Microsoft Knowledge Base Article 2621440 |
| Registry Key Verification | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2621440\Filelist |
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.
If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the installer, see Microsoft Knowledge Base Article 832475.
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 |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Displays a dialog box prompting the local user to allow a restart. |
| Special Options | |
| /overwriteoem | Overwrites OEM files without prompting. |
| /nobackup | Does not back up files needed for uninstall. |
| /forceappsclose | Forces other programs to close when the computer shuts down. |
| /log:path | Allows the redirection of installation log files. |
| /integrate:path | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. |
| /extract[:path] | Extracts files without starting the Setup program. |
| /ER | Enables extended error reporting. |
| /verbose | Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Displays a dialog box prompting the local user to allow a restart. |
| Special Options | |
| /forceappsclose | Forces other programs to close when the computer shuts down. |
| /log:path | Allows the redirection of installation log files. |
Verifying that the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Windows 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 all supported 32-bit editions of Windows Vista:\ Windows6.0-KB2621440-x86.msu /quiet |
| For all supported x64-based editions of Windows Vista:\ Windows6.0-KB2621440-x64.msu /quiet | |
| Installing without restarting | For all supported 32-bit editions of Windows Vista:\ Windows6.0-KB2621440-x86.msu /quiet /norestart |
| For all supported x64-based editions of Windows Vista:\ Windows6.0-KB2621440-x64.msu /quiet /norestart | |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | Yes, you must restart your system after you apply this security update. |
| HotPatching | Not applicable. |
| Removal Information | 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 2621440 |
| 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.
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.
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 of the 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 all supported 32-bit editions of Windows Server 2008:\ Windows6.0-KB2621440-x86.msu /quiet |
| For all supported x64-based editions of Windows Server 2008:\ Windows6.0-KB2621440-x64.msu /quiet | |
| For all supported Itanium-based editions of Windows Server 2008:\ Windows6.0-KB2621440-ia64.msu /quiet | |
| Installing without restarting | For all supported 32-bit editions of Windows Server 2008:\ Windows6.0-KB2621440-x86.msu /quiet /norestart |
| For all supported x64-based editions of Windows Server 2008:\ Windows6.0-KB2621440-x64.msu /quiet /norestart | |
| For all supported Itanium-based editions of Windows Server 2008:\ Windows6.0-KB2621440-ia64.msu /quiet /norestart | |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | Yes, you must restart your system after you apply this security update. |
| HotPatching | Not applicable. |
| Removal Information | 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 2621440 |
| 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.
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.
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 of the 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 all supported 32-bit editions of Windows 7:\ Windows6.1-KB2621440-x86.msu /quiet\ Windows6.1-KB2667402-v2-x86.msu /quiet |
| For all supported x64-based editions of Windows 7:\ Windows6.1-KB2621440-x64.msu /quiet\ Windows6.1-KB2667402-v2-x64.msu /quiet | |
| Installing without restarting | For all supported 32-bit editions of Windows 7:\ Windows6.1-KB2621440-x86.msu /quiet /norestart\ Windows6.1-KB2667402-v2-x86.msu /quiet /norestart |
| For all supported x64-based editions of Windows 7:\ Windows6.1-KB2621440-x64.msu /quiet /norestart\ Windows6.1-KB2667402-v2-x64.msu /quiet /norestart | |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | Yes, you must restart your system after you apply this security update. |
| HotPatching | Not applicable. |
| Removal Information | To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates. |
| File Information | See Microsoft Knowledge Base Article 2621440 and Microsoft Knowledge Base Article 2667402 |
| 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.
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. |
| /warnrestart:<seconds> | When combined with /quiet, the installer will warn the user before initiating restart. |
| /promptrestart | When combined with /quiet, the installer will prompt before initiating restart. |
| /forcerestart | When combined with /quiet, the installer will forcefully close applications and initiate restart. |
| /log:<file name> | Enables logging to specified file. |
| /extract:<destination> | Extracts the package contents to the destination folder. |
| /uninstall /kb:<KB Number> | Uninstalls the security update. |
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
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 of the 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 all supported x64-based editions of Windows Server 2008 R2:\ Windows6.1-KB2621440-x64.msu /quiet\ Windows6.1-KB2667402-v2-x64.msu /quiet |
| For all supported Itanium-based editions of Windows Server 2008 R2:\ Windows6.1-KB2621440-ia64.msu /quiet\ Windows6.1-KB2667402-v2-ia64.msu /quiet | |
| Installing without restarting | For all supported x64-based editions of Windows Server 2008 R2:\ Windows6.1-KB2621440-x64.msu /quiet /norestart\ Windows6.1-KB2667402-v2-x64.msu /quiet /norestart |
| For all supported Itanium-based editions of Windows Server 2008 R2:\ Windows6.1-KB2621440-ia64.msu /quiet /norestart\ Windows6.1-KB2667402-v2-ia64.msu /quiet /norestart | |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | Yes, you must restart your system after you apply this security update. |
| HotPatching | Not applicable. |
| Removal Information | To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates. |
| File Information | See Microsoft Knowledge Base Article 2621440 and Microsoft Knowledge Base Article 2667402 |
| 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.
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. |
| /warnrestart:<seconds> | When combined with /quiet, the installer will warn the user before initiating restart. |
| /promptrestart | When combined with /quiet, the installer will prompt before initiating restart. |
| /forcerestart | When combined with /quiet, the installer will forcefully close applications and initiate restart. |
| /log:<file name> | Enables logging to specified file. |
| /extract:<destination> | Extracts the package contents to the destination folder. |
| /uninstall /kb:<KB Number> | Uninstalls the security update. |
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
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 of the 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
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Luigi Auriemma, working with TippingPoint'sZero Day Initiative, for reporting the Remote Desktop Protocol Vulnerability (CVE-2012-0002)
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 websites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.
Support
- Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY (1-866-727-2338). For more information about available support options, see Microsoft Help and Support.
- International customers can receive support from their local Microsoft subsidiaries. For more information about how to contact Microsoft for support issues, visit the International Support website.
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 (March 13, 2012): Bulletin published.
- V2.0 (June 12, 2012): Bulletin rereleased to reoffer security update KB2667402 on all supported editions of Windows 7 and Windows Server 2008 R2. Customers using Windows 7 or Windows Server 2008 R2, including those who have already successfully installed the update originally offered on March 13, 2012, should install the reoffered update. See the Update FAQ for details.
- V2.1 (July 31, 2012): Bulletin revised to announce a detection change in the Windows Vista packages for KB2621440 to correct a Windows Update reoffering issue. This is a detection change only. Customers who have already successfully updated their systems do not need to take any action.
Built at 2014-04-18T13:49:36Z-07:00