Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Microsoft Security Bulletin MS14-005 - Important

Vulnerability in Microsoft XML Core Services Could Allow Information Disclosure (2916036)

Published: February 11, 2014 | Updated: February 28, 2014

Version: 1.1

General Information

Executive Summary

This security update resolves a publicly disclosed vulnerability in Microsoft XML Core Services included in Microsoft Windows. The vulnerability could allow information disclosure if a user views a specially crafted webpage using Internet Explorer. An attacker would have no way to force users to view specially crafted 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 an attacker's website, or by getting them to open an attachment sent through email.

This security update is rated Important for affected Windows clients and rated Low for affected Windows servers. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerability by correcting the way that MSXML verifies same-origin policy of URLs. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry later in this bulletin.

Recommendation. Most customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.

For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update at the earliest opportunity using update management software, or by checking for updates using the Microsoft Update service.

See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.

Knowledge Base Article

  • Knowledge Base Article: 2916036
  • File Information: Yes
  • SHA1/SHA2 hashes: Yes
  • Known issues: None

 

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

Component

Maximum Security Impact

Aggregate Severity Rating

Updates Replaced

Windows XP

Windows XP Service Pack 3  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Important

2079403 in MS10-051

Windows XP Professional x64 Edition Service Pack 2  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Important

2757638 in MS13-002

Windows Server 2003

Windows Server 2003 Service Pack 2  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Low

2719985 in MS12-043

Windows Server 2003 x64 Edition Service Pack 2  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Low

2757638 in MS13-002

Windows Server 2003 with SP2 for Itanium-based Systems  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Low

2757638 in MS13-002

Windows Vista

Windows Vista Service Pack 2  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Important

2079403 in MS10-051

Windows Vista x64 Edition Service Pack 2  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Important

2079403 in MS10-051

Windows Server 2008

Windows Server 2008 for 32-bit Systems Service Pack 2  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Low

2079403 in MS10-051

Windows Server 2008 for x64-based Systems Service Pack 2  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Low

2079403 in MS10-051

Windows Server 2008 for Itanium-based Systems Service Pack 2  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Low

2079403 in MS10-051

Windows 7

Windows 7 for 32-bit Systems Service Pack 1  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Important

None

Windows 7 for x64-based Systems Service Pack 1  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Important

None

Windows Server 2008 R2

Windows Server 2008 R2 for x64-based Systems Service Pack 1  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Low

None

Windows Server 2008 R2 for Itanium-based Systems Service Pack 1  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Low

None

Windows 8 and Windows 8.1

Windows 8 for 32-bit Systems  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Important

None

Windows 8 for x64-based Systems  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Important

None

Windows 8.1 for 32-bit Systems  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Important

None

Windows 8.1 for x64-based Systems  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Important

None

Windows Server 2012 and Windows Server 2012 R2

Windows Server 2012  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Low

None

Windows Server 2012 R2  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Low

None

Windows RT and Windows RT 8.1

Windows RT[1] 
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Important

None

Windows RT 8.1[1] 
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Important

None

Server Core installation option

Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Low

2079403 in MS10-051

Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Low

2079403 in MS10-051

Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Low

None

Windows Server 2012 (Server Core installation)  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Low

None

Windows Server 2012 R2 (Server Core installation)  
(2916036)

Microsoft XML Core Services 3.0

Information Disclosure

Low

None

[1]This update is available via Windows Update.

 

Non-Affected Software

Software

Microsoft XML Core Services 4.0

Microsoft XML Core Services 5.0

Microsoft XML Core Services 6.0

 

What version of Microsoft XML Core Services is installed on my system? 
Some versions of Microsoft XML Core Services are included with Microsoft Windows; others are installed with non-operating system software from Microsoft or third-party providers. Some are also available as separate downloads. The following table shows which versions of Microsoft XML Core Services are included with Microsoft Windows and which are installed with the installation of additional Microsoft or third-party software.

Operating System

MSXML 3.0 and MSXML 6.0

MSXML 4.0 and MSXML 5.0

Windows XP

Shipped with operating system

Installed with additional software

Windows Server 2003

Shipped with operating system

Installed with additional software

Windows Vista

Shipped with operating system

Installed with additional software

Windows Server 2008

Shipped with operating system

Installed with additional software

Windows 7

Shipped with operating system

Installed with additional software

Windows Server 2008 R2

Shipped with operating system

Installed with additional software

Windows 8

Shipped with operating system

Installed with additional software

Windows Server 2012

Shipped with operating system

Installed with additional software

Windows RT

Shipped with operating system

MSXML 4.0 installed with additional software. MSXML 5.0 not applicable.

Windows 8.1

Shipped with operating system

Installed with additional software

Windows Server 2012 R2

Shipped with operating system

Installed with additional software

Windows RT 8.1

Shipped with operating system

MSXML 4.0 installed with additional software. MSXML 5.0 not applicable.

Note For information on which versions are supported by Microsoft, see Microsoft Knowledge Base Article 269238.

What is Microsoft XML Core Services (MSXML)? 
Microsoft XML Core Services (MSXML) allows customers who use JScript, Visual Basic Scripting Edition (VBScript), and Microsoft Visual Studio 6.0 to develop XML-based applications that provide interoperability with other applications that adhere to the XML 1.0 standard. For more information, see the MSDN article, MSXML.

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 website.

It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. To determine the support lifecycle for your software release, see Select a Product for Lifecycle Information. For more information about service packs for these software releases, see Service Pack Lifecycle Support Policy.

Customers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, see the Microsoft Worldwide Information website, select the country in the Contact Information list, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Microsoft Support Lifecycle Policy FAQ.

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

Vulnerability Severity Rating and Maximum Security Impact by Affected Software

Affected Software

MSXML Information Disclosure Vulnerability - CVE-2014-0266

Aggregate Severity Rating

Windows XP

Windows XP Service Pack 3  

Important 
Information Disclosure

Important

Windows XP Professional x64 Edition Service Pack 2  

Important 
Information Disclosure

Important

Windows Server 2003

Windows Server 2003 Service Pack 2  

Low 
Information Disclosure

Low

Windows Server 2003 x64 Edition Service Pack 2  

Low 
Information Disclosure

Low

Windows Server 2003 with SP2 for Itanium-based Systems  

Low 
Information Disclosure

Low

Windows Vista

Windows Vista Service Pack 2  

Important 
Information Disclosure

Important

Windows Vista x64 Edition Service Pack 2  

Important 
Information Disclosure

Important

Windows Server 2008

Windows Server 2008 for 32-bit Systems Service Pack 2  

Low 
Information Disclosure

Low

Windows Server 2008 for x64-based Systems Service Pack 2  

Low 
Information Disclosure

Low

Windows Server 2008 for Itanium-based Systems Service Pack 2  

Low 
Information Disclosure

Low

Windows 7

Windows 7 for 32-bit Systems Service Pack 1  

Important 
Information Disclosure

Important

Windows 7 for x64-based Systems Service Pack 1  

Important 
Information Disclosure

Important

Windows Server 2008 R2

Windows Server 2008 R2 for x64-based Systems Service Pack 1  

Low 
Information Disclosure

Low

Windows Server 2008 R2 for Itanium-based Systems Service Pack 1  

Low 
Information Disclosure

Low

Windows 8 and Windows 8.1

Windows 8 for 32-bit Systems  

Important 
Information Disclosure

Important

Windows 8 for x64-based Systems  

Important 
Information Disclosure

Important

Windows 8.1 for 32-bit Systems  

Important 
Information Disclosure

Important

Windows 8.1 for x64-based Systems  

Important 
Information Disclosure

Important

Windows Server 2012 and Windows Server 2012 R2

Windows Server 2012  

Low 
Information Disclosure

Low

Windows Server 2012 R2  

Low 
Information Disclosure

Low

Windows RT and Windows RT 8.1

Windows RT 

Important 
Information Disclosure

Important

Windows RT 8.1 

Important 
Information Disclosure

Important

Server Core installation option

Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)  

Low 
Information Disclosure

Low

Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)  

Low 
Information Disclosure

Low

Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)  

Low 
Information Disclosure

Low

Windows Server 2012 (Server Core installation)  

Low 
Information Disclosure

Low

Windows Server 2012 R2 (Server Core installation)  

Low 
Information Disclosure

Low

An information disclosure vulnerability exists that could allow an attacker to read files on the local file system of a user, or read content of web domains where a user is currently authenticated. An attacker could exploit this vulnerability when a user views specially crafted web content that is designed to invoke MSXML through Internet Explorer.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2014-0266.

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 scripting to exploit this vulnerability. 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.
  • 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. This mode mitigates this vulnerability. See the FAQ section for this vulnerability 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 MSXML 3.0 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 {f5078f39-c551-11d3-89b9-0000f81fe221} and {f6d90f16-9c73-11d3-b32e-00c04f990bb4}, 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\{f5078f39-c551-11d3-89b9-0000f81fe221}]
    "Compatibility Flags"=dword:04000400
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f39-c551-11d3-89b9-0000f81fe221}]
    "Compatibility Flags"=dword:04000400
    
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f6d90f16-9c73-11d3-b32e-00c04f990bb4}]
    "Compatibility Flags"=dword:04000400
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\ActiveX Compatibility\{f6d90f16-9c73-11d3-b32e-00c04f990bb4}]
    "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.

    Dn613825.note(en-us,Security.10).gifNote:
    You must restart Internet Explorer for your changes to take effect.

    Impact of workaround. Websites that use the XMLHTTP 3.0 ActiveX controls may no longer display or function correctly in Internet Explorer.

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

     

  • Set Internet and Local intranet security zone settings to "High" to block ActiveX Controls and Active Scripting in these zones

    You can help protect against exploitation of this vulnerability by changing your settings for the Internet security zone to block ActiveX controls and Active Scripting. You can do this by setting your browser security to High.

    To raise the browsing security level in Internet Explorer, perform the following steps:

    1. On the Internet Explorer Tools menu, click Internet Options.
    2. In the Internet Options dialog box, click the Security tab, and then click Internet.
    3. Under Security level for this zone, move the slider to High. This sets the security level for all websites you visit to High.
    4. Click Local intranet.
    5. Under Security level for this zone, move the slider to High. This sets the security level for all websites you visit to High.
    6. Click OK to accept the changes and return to Internet Explorer.
    Dn613825.note(en-us,Security.10).gifNote:
    If no slider is visible, click Default Level, and then move the slider to High.

     

    Dn613825.note(en-us,Security.10).gifNote:
    Setting the level to High may cause some websites to work incorrectly. If you have difficulty using a website after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly even with the security setting set to High.

    Impact of workaround. There are side effects to blocking ActiveX Controls and Active Scripting. Many websites that are on the Internet or on an intranet use ActiveX or Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX Controls to provide menus, ordering forms, or even account statements. Blocking ActiveX Controls or Active Scripting is a global setting that affects all Internet and intranet sites. If you do not want to block ActiveX Controls or Active Scripting for such sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone".

    Add sites that you trust to the Internet Explorer Trusted sites zone

    After you set Internet Explorer to block ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted websites exactly as you do today, while helping to protect yourself from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.

    To do this, perform the following steps:

    1. In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
    2. In the Select a web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
    3. If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
    4. In the Add this website to the zone box, type the URL of a site that you trust, and then click Add.
    5. Repeat these steps for each site that you want to add to the zone.
    6. Click OK two times to accept the changes and return to Internet Explorer.

    Add any sites that you trust not to take malicious action on your system. Two in particular that you may want to add are *.windowsupdate.microsoft.com and *.update.microsoft.com. These are the sites that will host the update, and it requires an ActiveX Control to install the update.

     

  • Configure Internet Explorer to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone

    You can help protect against exploitation of this vulnerability by changing your settings to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone. To do this, perform the following steps:

    1. In Internet Explorer, click Internet Options on the Tools menu.
    2. Click the Security tab.
    3. Click Internet, and then click Custom Level.
    4. Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK.
    5. Click Local intranet, and then click Custom Level.
    6. Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK.
    7. Click OK two times to return to Internet Explorer.
    Dn613825.note(en-us,Security.10).gifNote:
    Disabling Active Scripting in the Internet and Local intranet security zones may cause some websites to work incorrectly. If you have difficulty using a website after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly.

    Impact of workaround. There are side effects to prompting before running Active Scripting. Many websites that are on the Internet or on an intranet use Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use Active Scripting to provide menus, ordering forms, or even account statements. Prompting before running Active Scripting is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run Active Scripting. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone".

    Add sites that you trust to the Internet Explorer Trusted sites zone

    After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted websites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.

    To do this, perform the following steps:

    1. In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
    2. In the Select a web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
    3. If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
    4. In the Add this website to the zone box, type the URL of a site that you trust, and then click Add.
    5. Repeat these steps for each site that you want to add to the zone.
    6. Click OK two times to accept the changes and return to Internet Explorer.
    Dn613825.note(en-us,Security.10).gifNote:
    Add any sites that you trust not to take malicious action on your system. Two in particular that you may want to add are *.windowsupdate.microsoft.com and *.update.microsoft.com. These are the sites that will host the update, and it requires an ActiveX Control to install the update.

     

FAQ

What is the scope of the vulnerability? 
This is an information disclosure vulnerability.

What causes the vulnerability? 
The vulnerability is caused when Internet Explorer does not properly enforce cross-domain policies, allowing an attacker to access content from different domains.

What are cross-domain and zone policy in Internet Explorer? 
Before an XMLHTTP request is sent, the URL of the hosting page is compared to the URL in the open method to determine if the URLs are in the same domain. If not, the request is handled according to the policy of the security zone in which the request originates. For more information, see About Native XMLHTTP.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could read files on the local file system of the user or read content of web domains where the user is currently authenticated.

How could an attacker exploit the vulnerability? 
An attacker could exploit the vulnerability by hosting a specially crafted website that is designed to invoke MSXML through Internet Explorer. This can also include compromised websites and websites that accept or host user-provided content. 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. For example, an attacker could trick users into clicking a link that takes them to the attacker's site.

What systems are primarily at risk from the vulnerability? 
Systems where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this 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 this vulnerability? 
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 addresses the vulnerability by correcting the way that MSXML verifies same-origin policy of URLs.

Dn613825.note(en-us,Security.10).gifNote:
After applying this update, customers may find that some webpages no longer render properly in Internet Explorer. This could be because access is being denied to the webpages due to cross-domain and zone policy. The MSXML-XMLHTTP component is used to determine the policy for cross-domain access across zones. For example, a trusted site can access data from a site in the Intranet zone, while the reverse is always denied. For more information, see About Native XMLHTTP.

If you trust and wish to view such webpages, you can configure Internet Explorer to allow you to view the webpages. For more information on configuring Internet Explorer after installing this update, see Microsoft Knowledge Base Article 2916036.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CVE-2014-0266.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 
Yes. Microsoft is aware of targeted attacks that attempt to exploit this vulnerability.

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

Windows XP (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 XP:
WindowsXP-KB2916036-x86-enu.exe


For all supported x64-based editions of Windows XP Professional:
WindowsServer2003.WindowsXP-KB2916036-x64-enu.exe

Installation switches

See Microsoft Knowledge Base Article 262841

Update log file

KB2916036.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%\$NTUninstallKB2916036$\Spuninst folder

File information

See Microsoft Knowledge Base Article 2916036

Registry key verification

For all supported 32-bit editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2916036\Filelist


For all supported x64-based editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB2916036\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-KB2916036-x86-enu.exe


For all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB2916036-x64-enu.exe


For all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB2916036-ia64-enu.exe

Installation switches

See Microsoft Knowledge Base Article 262841

Update log file

KB2916036.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%\$NTUninstallKB2916036$\Spuninst folder

File information

See Microsoft Knowledge Base Article 2916036

Registry key verification

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2916036\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-KB2916036-x86.msu


For all supported x64-based editions of Windows Vista:
Windows6.0-KB2916036-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

See Microsoft Knowledge Base Article 2916036

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-KB2916036-x86.msu


For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB2916036-x64.msu


For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB2916036-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

See Microsoft Knowledge Base Article 2916036

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-KB2916036-x86.msu


For all supported x64-based editions of Windows 7:
Windows6.1-KB2916036-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

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 2916036

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-KB2916036-x64.msu


For all supported Itanium-based editions of Windows Server 2008 R2:
Windows6.1-KB2916036-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

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 2916036

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-KB2916036-x86.msu


For all supported x64-based editions of Windows 8:
Windows8-RT-KB2916036-x64.msu


For all supported 32-bit editions of Windows 8.1:
Windows8.1-KB2916036-x86.msu


For all supported x64-based editions of Windows 8.1:
Windows8.1-KB2916036-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

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

See Microsoft Knowledge Base Article 2916036

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-KB2916036-x64.msu


For all supported editions of Windows Server 2012 R2:
Windows8.1-KB2916036-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

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

See Microsoft Knowledge Base Article 2916036

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)

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

Deployment

These updates are available via Windows Update only.

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

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

See Microsoft Knowledge Base Article 2916036

Microsoft thanks the following for working with us to help protect customers:

  • FireEye, Inc. for working with us on the MSXML Information Disclosure Vulnerability (CVE-2014-0266)

Microsoft Active Protections Program (MAPP)

To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please go to the active protections websites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.

Support

How to obtain help and support for this security update

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 (February 11, 2014): Bulletin published.
  • V1.1 (February 28, 2014): Bulletin revised to announce a detection change in the 2916036 update for Windows 8.1 for 32-bit Systems, Windows 8.1 for x64-based Systems, Windows Server 2012 R2, and Windows RT 8.1. 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.

Page generated 2014-04-04 9:52Z-07:00.
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.