Article
12/03/2019
25 minutes to read

Security Bulletin

Microsoft Security Bulletin MS13-090 - Critical

Cumulative Security Update of ActiveX Kill Bits (2900986)

Published: November 12, 2013 | Updated: February 28, 2014

Version: 1.1

General Information

Executive Summary

This security update resolves a privately reported vulnerability that is currently being exploited. The vulnerability exists in the InformationCardSigninHelper Class ActiveX control. The vulnerability could allow remote code execution if a user views a specially crafted webpage with Internet Explorer, instantiating the ActiveX control. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

This security update is rated Critical for all supported editions of Windows XP, Windows Vista, Windows 7, Windows 8, Windows RT, Windows 8.1, and Windows RT 8.1. For all supported editions of Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2, this security update is rated Moderate. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerability by setting kill bits so that the vulnerable control does not run in Internet Explorer. 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 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.

Knowledge Base Article

Knowledge Base Article	2900986
File information	No
SHA1/SHA2 hashes	No
Known issues	None

Affected and Non-Affected Software

The following software has 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	Maximum Security Impact	Aggregate Severity Rating	Updates Replaced
Windows XP Service Pack 3 (2900986)	Remote Code Execution	Critical	2618451 in MS11-090
Windows XP Professional x64 Edition Service Pack 2 (2900986)	Remote Code Execution	Critical	2618451 in MS11-090
Windows Server 2003 Service Pack 2 (2900986)	Remote Code Execution	Moderate	2618451 in MS11-090
Windows Server 2003 x64 Edition Service Pack 2 (2900986)	Remote Code Execution	Moderate	2618451 in MS11-090
Windows Server 2003 with SP2 for Itanium-based Systems (2900986)	Remote Code Execution	Moderate	2618451 in MS11-090
Windows Vista Service Pack 2 (2900986)	Remote Code Execution	Critical	2618451 in MS11-090
Windows Vista x64 Edition Service Pack 2 (2900986)	Remote Code Execution	Critical	2618451 in MS11-090
Windows Server 2008 for 32-bit Systems Service Pack 2 (2900986)	Remote Code Execution	Moderate	2618451 in MS11-090
Windows Server 2008 for x64-based Systems Service Pack 2 (2900986)	Remote Code Execution	Moderate	2618451 in MS11-090
Windows Server 2008 for Itanium-based Systems Service Pack 2 (2900986)	Remote Code Execution	Moderate	2618451 in MS11-090
Windows 7 for 32-bit Systems Service Pack 1 (2900986)	Remote Code Execution	Critical	2618451 in MS11-090
Windows 7 for x64-based Systems Service Pack 1 (2900986)	Remote Code Execution	Critical	2618451 in MS11-090
Windows Server 2008 R2 for x64-based Systems Service Pack 1 (2900986)	Remote Code Execution	Moderate	2618451 in MS11-090
Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 (2900986)	Remote Code Execution	Moderate	2618451 in MS11-090
Windows 8 for 32-bit Systems (2900986)	Remote Code Execution	Critical	None
Windows 8 for x64-based Systems (2900986)	Remote Code Execution	Critical	None
Windows 8.1 for 32-bit Systems (2900986)	Remote Code Execution	Critical	None
Windows 8.1 for x64-based Systems (2900986)	Remote Code Execution	Critical	None
Windows Server 2012 (2900986)	Remote Code Execution	Moderate	None
Windows Server 2012 R2 (2900986)	Remote Code Execution	Moderate	None
Windows RT^[1] (2900986)	Remote Code Execution	Critical	None
Windows RT 8.1^[1] (2900986)	Remote Code Execution	Critical	None

^[1]This update is available via [Windows Update](http://go.microsoft.com/fwlink/?linkid=21130). **Non-Applicable** **Software** | Operating System | |----------------------------------------------------------------------------------------| | Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation) | | Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) | | Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) | | Windows Server 2012 (Server Core installation) | | Windows Server 2012 R2 (Server Core installation) | Update FAQ ---------- **Are Windows 8.1 Preview and Windows RT 8.1 Preview** **affected by** **the vulnerability** **addressed in this** **bulletin?** Yes. The 2900986 update is available for Windows 8.1 Preview and Windows RT 8.1 Preview. Customers running these operating systems are encouraged to apply the updates to their systems. The updates are available on [Windows Update](http://go.microsoft.com/fwlink/?linkid=21130). **How are Server Core installations affected by the vulnerabilities addressed in this bulletin?** The vulnerability addressed by this update does not affect supported editions of Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 as indicated in the Non-Applicable Software table, when installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, [Managing a Server Core Installation: Overview](http://technet.microsoft.com/library/ee441255), [Servicing a Server Core Installation](http://technet.microsoft.com/library/ff698994), and [Server Core and Full Server Integration Overview](http://technet.microsoft.com/library/hh831758). **What kill bits does this Cumulative Security Update of ActiveX Kill Bits contain?** This Cumulative Security Update of ActiveX Kill Bits contains new kill bits and all kill bits previously released in the following updates: | Update | Title | |-----------------------------------------------------------------------------------------------|-------------------------------------------------| | [MS08-023](http://go.microsoft.com/fwlink/?linkid=112366) | Security Update of ActiveX Kill Bits | | [MS08-032](http://go.microsoft.com/fwlink/?linkid=116368) | Cumulative Security Update of ActiveX Kill Bits | | [Microsoft Security Advisory 953839](http://technet.microsoft.com/security/advisory/953839) | Update Rollup for ActiveX Kill Bits | | [Microsoft Security Advisory 956391](http://technet.microsoft.com/security/advisory/956391) | Update Rollup for ActiveX Kill Bits | | [Microsoft Security Advisory 960715](http://technet.microsoft.com/security/advisory/960715) | Update Rollup for ActiveX Kill Bits | | [Microsoft Security Advisory 969898](http://technet.microsoft.com/security/advisory/969898) | Update Rollup for ActiveX Kill Bits | | [MS09-032](http://go.microsoft.com/fwlink/?linkid=157386) | Cumulative Security Update of ActiveX Kill Bits | | [MS09-055](http://technet.microsoft.com/security/bulletin/ms09-055) | Cumulative Security Update of ActiveX Kill Bits | | [MS10-008](http://go.microsoft.com/fwlink/?linkid=179106) | Cumulative Security Update of ActiveX Kill Bits | | [MS10-034](http://go.microsoft.com/fwlink/?linkid=185159) | Cumulative Security Update of ActiveX Kill Bits | | [MS11-027](http://go.microsoft.com/fwlink/?linkid=214005) | Cumulative Security Update of ActiveX Kill Bits | | [Microsoft Security Advisory 2562937](http://technet.microsoft.com/security/advisory/2562937) | Update Rollup for ActiveX Kill Bits | | [MS11-090](http://go.microsoft.com/fwlink/?linkid=232507) | Cumulative Security Update of ActiveX Kill Bits | | [Microsoft Security Advisory 2647518](http://technet.microsoft.com/security/advisory/2647518) | Update Rollup for ActiveX Kill Bits | | [Microsoft Security Advisory 2695962](http://technet.microsoft.com/security/advisory/2695962) | Update Rollup for ActiveX Kill Bits | | [Microsoft Security Advisory 2736233](http://technet.microsoft.com/security/advisory/2736233) | Update Rollup for ActiveX Kill Bits | | [Microsoft Security Advisory 2820197](http://technet.microsoft.com/security/advisory/2820197) | Update Rollup for ActiveX Kill Bits | **What is a kill bit?** A security feature in Microsoft Internet Explorer makes it possible to prevent an ActiveX control from ever being loaded by the Internet Explorer HTML-rendering engine. This is done by making a registry setting and is referred to as setting the kill bit. After the kill bit is set, the control can never be loaded, even when it is fully installed. Setting the kill bit makes sure that even if a vulnerable component is introduced or is re-introduced to a system, it remains inert and harmless. For more information on kill bits, see [Microsoft Knowledge Base Article 240797](http://support.microsoft.com/kb/240797). **What is a security update of ActiveX kill bits?** A security update of ActiveX kill bits contains the class IDs (CLSID) of certain ActiveX controls that are the basis of the security update. **Why does this update not contain any binary files?** This update only makes changes to the registry to disable the controls from instantiating in Internet Explorer. **Should I install this update if I do not have the affected component installed or use the affected platform?** Yes. Installing this update will block the vulnerable control from running in Internet Explorer. **Do I need to reapply this update if I install an ActiveX control discussed in this security update at a later date?** No, reapplying this update is not required. The kill bit will block Internet Explorer from running the control even if the control is installed at a later date. **Does this update contain kill bits that were previously released in an Internet Explorer security update?** No, this update does not include kill bits that were previously released in an Internet Explorer security update. We recommend that you install the latest Cumulative Security Update for Internet Explorer. **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 has 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](http://go.microsoft.com/fwlink/?linkid=21742) 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](http://go.microsoft.com/fwlink/?linkid=169555). For more information about service packs for these software releases, see [Service Pack Lifecycle Support Policy](http://go.microsoft.com/fwlink/?linkid=89213). 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](http://go.microsoft.com/fwlink/?linkid=33329) 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](http://go.microsoft.com/fwlink/?linkid=169557). ### **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 [November bulletin summary](http://technet.microsoft.com/security/bulletin/ms13-nov). For more information, see [Microsoft Exploitability Index](http://technet.microsoft.com/security/cc998259).

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software	InformationCardSigninHelper Vulnerability - CVE-2013-3918	Aggregate Severity Rating
Windows XP Service Pack 3	Critical Remote Code Execution	Critical
Windows XP Professional x64 Edition Service Pack 2	Critical Remote Code Execution	Critical
Windows Server 2003 Service Pack 2	Moderate Remote Code Execution	Moderate
Windows Server 2003 x64 Edition Service Pack 2	Moderate Remote Code Execution	Moderate
Windows Server 2003 with SP2 for Itanium-based Systems	Moderate Remote Code Execution	Moderate
Windows Vista Service Pack 2	Critical Remote Code Execution	Critical
Windows Vista x64 Edition Service Pack 2	Critical Remote Code Execution	Critical
Windows Server 2008 for 32-bit Systems Service Pack 2	Moderate Remote Code Execution	Moderate
Windows Server 2008 for x64-based Systems Service Pack 2	Moderate Remote Code Execution	Moderate
Windows Server 2008 for Itanium-based Systems Service Pack 2	Moderate Remote Code Execution	Moderate
Windows 7 for 32-bit Systems Service Pack 1	Critical Remote Code Execution	Critical
Windows 7 for x64-based Systems Service Pack 1	Critical Remote Code Execution	Critical
Windows Server 2008 R2 for x64-based Systems Service Pack 1	Moderate Remote Code Execution	Moderate
Windows Server 2008 R2 for Itanium-based Systems Service Pack 1	Moderate Remote Code Execution	Moderate
Windows 8 for 32-bit Systems	Critical Remote Code Execution	Critical
Windows 8 for x64-based Systems	Critical Remote Code Execution	Critical
Windows 8.1 for 32-bit Systems	Critical Remote Code Execution	Critical
Windows 8.1 for x64-based Systems	Critical Remote Code Execution	Critical
Windows Server 2012	Moderate Remote Code Execution	Moderate
Windows Server 2012 R2	Moderate Remote Code Execution	Moderate
Windows RT	Critical Remote Code Execution	Critical
Windows RT 8.1	Critical Remote Code Execution	Critical

InformationCardSigninHelper Vulnerability - CVE-2013-3918 --------------------------------------------------------- A remote code execution vulnerability exists in the InformationCardSigninHelper Class ActiveX control, icardie.dll. An attacker could exploit the vulnerability by constructing a specially crafted webpage. When a user views the webpage, the vulnerability could allow remote code execution. An attacker who successfully exploited this vulnerability could gain the same user rights as the current user. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2013-3918](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2013-3918). #### Mitigating Factors 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: - In a web-based attack scenario, an attacker could take advantage of compromised websites and websites that accept or host user-provided content or advertisements. These websites could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to view the attacker-controlled content. Instead, an attacker would have to convince users to take action, typically by getting them to click a link in an email message or in an Instant Messenger message that takes users to the attacker's website, or by getting them to open an attachment sent through email. - By default, all supported versions of Microsoft Outlook, Microsoft Outlook Express, and Windows Mail open HTML email messages in the Restricted sites zone. The Restricted sites zone, which disables script and ActiveX controls, helps reduce the risk of an attacker being able to use these vulnerabilities to execute malicious code. If a user clicks a link in an email message, the user could still be vulnerable to exploitation of this vulnerability through the web-based attack scenario. - An attacker who successfully exploited this vulnerability could gain the same user rights as the current user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. - By default, Internet Explorer on Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 runs in a restricted mode that is known as [Enhanced Security Configuration](http://technet.microsoft.com/library/dd883248). This mode mitigates the vulnerability. See the FAQ section for these vulnerabilities for more information about Internet Explorer Enhanced Security Configuration. #### Workarounds 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: - **Prevent binary behaviors from being used in Internet Explorer** You can disable attempts to use a specific binary behavior in Internet Explorer by setting the kill bit for the behavior in the registry. **Warning** If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. To set the kill bits for CLSIDs with value of {19916e01-b44e-4e31-94a4-4696df46157b}, {c2c4f00a-720e-4389-aeb9-e9c4b0d93c6f}, and {53001f3a-f5e1-4b90-9c9f-00e09b53c5f1}, paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension. ``` Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{19916e01-b44e-4e31-94a4-4696df46157b}] "Compatibility Flags"=dword:04000400

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\ActiveX Compatibility\{19916e01-b44e-4e31-94a4-4696df46157b}]
"Compatibility Flags"=dword:04000400

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{c2c4f00a-720e-4389-aeb9-e9c4b0d93c6f}]
"Compatibility Flags"=dword:04000400

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\ActiveX Compatibility\{c2c4f00a-720e-4389-aeb9-e9c4b0d93c6f}]
"Compatibility Flags"=dword:04000400

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{53001f3a-f5e1-4b90-9c9f-00e09b53c5f1}]
"Compatibility Flags"=dword:04000400

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\ActiveX Compatibility\{53001f3a-f5e1-4b90-9c9f-00e09b53c5f1}]
"Compatibility Flags"=dword:04000400
```

You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy. For more information about Group Policy, see the TechNet article, [Group Policy collection](http://go.microsoft.com/fwlink/?linkid=215719).

**Note** You must restart Internet Explorer for your changes to take effect.

**Impact of workaround**. There is no impact as long as the behavior is not intended to be used in Internet Explorer.

**How to undo the workaround.** Delete the registry keys previously added in implementing this workaround.

FAQ

What is the scope of the vulnerability?
This is a remote code execution vulnerability.

What causes the vulnerability?
When the InformationCardSigninHelper Class ActiveX control is instantiated in Internet Explorer, the control may corrupt the system state in such a way that an attacker could run arbitrary code.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could gain the same user rights as the current user. If the current user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an 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?
An attacker could host a specially crafted website that is designed to exploit these vulnerabilities through Internet Explorer, and then convince a user to view the website. The attacker could also take advantage of compromised websites and websites that accept or host user-provided content or advertisements. These websites could contain specially crafted content that could exploit these vulnerabilities. In all cases, however, an attacker would have no way to force users to view the attacker-controlled content. Instead, an attacker would have to convince users to take action, typically by getting them to click a link in an email message or in an Instant Messenger message that takes users to the attacker's website, or by getting them to open an attachment sent through email.

What systems are primarily at risk from the vulnerability?
This vulnerability requires that a user be logged on and visiting a website for any malicious action to occur. Therefore, any system where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from the vulnerability.

I am running Internet Explorer for Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2. Does this mitigate these vulnerabilities?
Yes. By default, Internet Explorer on Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 runs in a restricted mode that is known as Enhanced Security Configuration. Enhanced Security Configuration is a group of preconfigured settings in Internet Explorer that can reduce the likelihood of a user or administrator downloading and running specially crafted web content on a server. This is a mitigating factor for websites that you have not added to the Internet Explorer Trusted sites zone.

What does the update do?
The update disables the binary behavior by setting the following kill bits for the Class Identifiers hosted in the library file listed below:

Class Identifier	File	Description
{19916e01-b44e-4e31-94a4-4696df46157b}	icardie.dll	Information Card Sign-in Helper ActiveX Control
{c2c4f00a-720e-4389-aeb9-e9c4b0d93c6f}	icardie.dll	Card Space Element Behavior Factory ActiveX Control
{53001f3a-f5e1-4b90-9c9f-00e09b53c5f1}	icardie.dll	Card Space Claim Collection ActiveX Control

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?
Yes. Microsoft is aware of limited, targeted attacks that attempt to exploit this vulnerability.

Update Information

Detection and Deployment Tools and Guidance

Several resources are available to help administrators deploy security updates.

Microsoft Baseline Security Analyzer (MBSA) lets administrators scan local and remote systems for missing security updates and common security misconfigurations.
Windows Server Update Services (WSUS), Systems Management Server (SMS), and System Center Configuration Manager help administrators distribute security updates.
The Update Compatibility Evaluator components included with Application Compatibility Toolkit aid in streamlining the testing and validation of Windows updates against installed applications.

For information about these and other tools that are available, see Security Tools for IT Pros.

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.

Security update file names	For Windows XP Service Pack 3: WindowsXP-KB2900986-x86-enu.exe
	For Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB2900986-x64-enu.exe
Installation switches	See Microsoft Knowledge Base Article 262841
Update log file	KB2900986.log
Restart requirement	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.
Removal information	Use Add or Remove Programs item in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB2900986$\Spuninst folder
File information	Not applicable
Registry key verification	For all supported 32-bit editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2900986\Filelist
	For all supported x64-based editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB2900986\Filelist

Note The update for supported versions of Windows XP Professional x64 Edition also applies to supported versions of Windows Server 2003 x64 Edition.

Windows Server 2003 (all editions)

Reference Table

The following table contains the security update information for this software.

Security update file names	For all supported 32-bit editions of Windows Server 2003: WindowsServer2003-KB2900986-x86-enu.exe
	For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB2900986-x64-enu.exe
	For all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB2900986-ia64-enu.exe
Installation switches	See Microsoft Knowledge Base Article 262841
Update log file	KB2900986.log
Restart requirement	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.
Removal information	Use Add or Remove Programs item in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB2900986$\Spuninst folder
File information	Not applicable
Registry key verification	HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2900986\Filelist

**Note** The update for supported versions of Windows Server 2003 x64 Edition also applies to supported versions of Windows XP Professional x64 Edition. #### Windows Vista (all editions) **Reference Table** The following table contains the security update information for this software.

Security update file names	For all supported 32-bit editions of Windows Vista: Windows6.0-KB2900986-x86.msu
	For all supported x64-based editions of Windows Vista: Windows6.0-KB2900986-x64.msu
Installation switches	See Microsoft Knowledge Base Article 934307
Restart requirement	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.
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	Not applicable
Registry key verification	Note A registry key does not exist to validate the presence of this update.

#### Windows Server 2008 (all editions) **Reference Table** The following table contains the security update information for this software.

Security update file names	For all supported 32-bit editions of Windows Server 2008: Windows6.0-KB2900986-x86.msu
	For all supported x64-based editions of Windows Server 2008: Windows6.0-KB2900986-x64.msu
	For all supported Itanium-based editions of Windows Server 2008: Windows6.0-KB2900986-ia64.msu
Installation switches	See Microsoft Knowledge Base Article 934307
Restart requirement	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.
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	Not applicable
Registry key verification	Note A registry key does not exist to validate the presence of this update.

#### Windows 7 (all editions) **Reference Table** The following table contains the security update information for this software.

Security update file name	For all supported 32-bit editions of Windows 7: Windows6.1-KB2900986-x86.msu
	For all supported x64-based editions of Windows 7: Windows6.1-KB2900986-x64.msu
Installation switches	See Microsoft Knowledge Base Article 934307
Restart requirement	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.
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	Not applicable
Registry key verification	Note A registry key does not exist to validate the presence of this update.

#### Windows Server 2008 R2 (all editions) **Reference Table** The following table contains the security update information for this software.

Security update file name	For all supported x64-based editions of Windows Server 2008 R2: Windows6.1-KB2900986-x64.msu
	For all supported Itanium-based editions of Windows Server 2008 R2: Windows6.1-KB2900986-ia64.msu
Installation switches	See Microsoft Knowledge Base Article 934307
Restart requirement	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.
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	Not applicable
Registry key verification	Note A registry key does not exist to validate the presence of this update.

#### Windows 8 and Windows 8.1 (all editions) **Reference Table** The following table contains the security update information for this software.

Security update file name	For all supported 32-bit editions of Windows 8: Windows8-RT-KB2900986-x86.msu
	For all supported x64-based editions of Windows 8: Windows8-RT-KB2900986-x64.msu
	For all supported 32-bit editions of Windows 8.1: Windows8.1-KB2900986-x86.msu
	For all supported x64-based editions of Windows 8: Windows8.1-KB2900986-x64.msu
Installation switches	See Microsoft Knowledge Base Article 934307
Restart requirement	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.
Removal information	To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, click Windows Update, and then under See also, click Installed updates and select from the list of updates.
File information	Not applicable
Registry key verification	Note A registry key does not exist to validate the presence of this update.

#### Windows Server 2012 and Windows Server 2012 R2 (all editions) **Reference Table** The following table contains the security update information for this software.

Security update file name	For all supported editions of Windows Server 2012: Windows8-RT-KB2900986-x64.msu
	For all supported editions of Windows Server 2012 R2: Windows8.1-KB2900986-x64.msu
Installation switches	See Microsoft Knowledge Base Article 934307
Restart requirement	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.
Removal information	To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, click Windows Update, and then under See also, click Installed updates and select from the list of updates.
File information	Not applicable
Registry key verification	Note A registry key does not exist to validate the presence of this update.

#### Windows RT and Windows RT 8.1 (all editions) **Reference Table** The following table contains the security update information for this software. | | | |-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Deployment** | This update is available via [Windows Update](http://go.microsoft.com/fwlink/?linkid=21130). | | **Restart Requirement** | 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. | | **Removal Information** | Click **Control Panel**, click **System and Security**, click **Windows Update**, and then under See also, click **Installed updates** and select from the list of updates. | | **File information** | Not applicable | ### Other Information #### Acknowledgments Microsoft [thanks](http://go.microsoft.com/fwlink/?linkid=21127) the following for working with us to help protect customers: - ucq and Daiki Fukumori of the [Cyber Defense Institute, Inc.](http://www.cyberdefense.jp/) for reporting the InformationCardSigninHelper Vulnerability (CVE-2013-3918) - [iSIGHT Partners](http://www.isightpartners.com/) for working with us on the InformationCardSigninHelper Vulnerability (CVE-2013-3918) - Dan Caselden and Xiaobo Chen of [FireEye](http://www.fireeye.com/) for working with us on the InformationCardSigninHelper Vulnerability (CVE-2013-3918) #### 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](http://go.microsoft.com/fwlink/?linkid=215201). #### Support **How to obtain help and support for this security update** - Help installing updates: [Support for Microsoft Update](http://support.microsoft.com/ph/6527) - Security solutions for IT professionals: [TechNet Security Troubleshooting and Support](http://technet.microsoft.com/security/bb980617.aspx) - Help protect your computer that is running Windows from viruses and malware: [Virus Solution and Security Center](http://support.microsoft.com/contactus/cu_sc_virsec_master) - Local support according to your country: [International Support](http://support.microsoft.com/common/international.aspx) #### 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 (November 12, 2013): Bulletin published. - V1.1 (February 28, 2014): Bulletin revised to announce a detection change in the 2900986 update for Windows 8.1 for 32-bit Systems, Windows 8.1 for x64-based Systems, Windows RT 8.1, and Windows Server 2012 R2. This is a detection change only. There were no changes to the update files. Customers who have already successfully updated their systems do not need to take any action. *Built at 2014-04-18T13:49:36Z-07:00*