The security update addresses the vulnerabilities by correcting how SharePoint Server and Web Applications sanitize specially crafted page content. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability later in this bulletin.

Recommendation. Customers can configure automatic updating to check online for updates from Microsoft Update by using the Microsoft Update service. Customers who have automatic updating enabled and configured to check online for updates from Microsoft Update typically 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 from Microsoft Update 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.

Note for SharePoint Server The detection tools (such as Microsoft Update, WSUS, MBSA, SMS, and System Center Configuration Manager) are applicable for single-server Microsoft SharePoint Server deployments. The detection tools do not detect the applicability of the updates on systems configured as part of a multiple-system SharePoint server farm. For recommended instructions on how to apply updates to SharePoint Server, see Deploy software updates for SharePoint 2013.

Knowledge Base Article

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.

Non-Affected Software

Why does this update address several reported security vulnerabilities?This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files.

Why are multiple update packages available for some affected software?The updates required to address the vulnerabilities described in this bulletin are offered across different updates packages as indicated in the Affected Software table due to the componentized servicing model for Microsoft Office and Microsoft SharePoint Server software.

There are multiple update packages available for some affected software. Do I need to install all the updates listed in the Affected Software table for the software?Yes. Customers should apply all updates offered for the software installed on their systems.

Do I need to install these security updates in a particular sequence?No. Multiple updates for one version of Microsoft Office or Microsoft SharePoint Server software 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 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.

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

Related remote code execution vulnerabilities exist in Microsoft SharePoint Server. An authenticated attacker who successfully exploited any of these related vulnerabilities could run arbitrary code in the security context of the W3WP service account.

To view these related vulnerabilities as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2014-0251.

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:

To exploit any of these related vulnerabilities, an attacker must be able to authenticate on the target SharePoint site. Note that this is not a mitigating factor if the SharePoint site is configured to allow anonymous users to access the site. By default, anonymous access is not enabled.

Workarounds

Microsoft has not identified any workarounds for these vulnerabilities.

FAQ

What is the scope of the vulnerabilities?These are related remote code execution vulnerabilities.

What causes the vulnerabilities?When page content is not properly sanitized, conditions exist where an attacker could run arbitrary code in the security context of the W3WP service account.

Why is a single CVE Identifier assigned to multiple vulnerabilities?Although the vulnerabilities are in different components of Microsoft SharePoint Server, they all share the same underlying issue and related code. The vulnerabilities are grouped into a single CVE Identifier that represents the underlying issue.

What might an attacker use the vulnerabilities to do?An attacker who successfully exploited any of these related vulnerabilities could run arbitrary code in the security context of the W3WP service account on the target SharePoint site.

How could an attacker exploit the vulnerabilities?An authenticated attacker could attempt to exploit any of these related vulnerabilities by sending specially crafted page content to a SharePoint server.

What systems are primarily at risk from the vulnerabilities?Systems that are running an affected version of SharePoint server are primarily at risk.

What does the update do?The update addresses these related vulnerabilities by correcting how SharePoint Server sanitizes specially crafted page content.

When this security bulletin was issued, had these vulnerabilities been publicly disclosed?No. Microsoft received information about these related vulnerabilities through coordinated vulnerability disclosure.

When this security bulletin was issued, had Microsoft received any reports that these vulnerabilities were being exploited?No. Microsoft had not received any information to indicate that these related vulnerabilities had been publicly used to attack customers when this security bulletin was originally issued.

An elevation of privilege vulnerability exists in Microsoft SharePoint Server. An attacker who successfully exploited this vulnerability could perform cross-site scripting attacks on affected systems and run script in the security context of the logged-on user.

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

Mitigating Factors

Microsoft has not identified any mitigating factors for this vulnerability.

Workarounds

Microsoft has not identified any workarounds for this vulnerability.

FAQ

What is the scope of the vulnerability?This is an elevation of privilege vulnerability.

What causes the vulnerability?The vulnerability is caused when SharePoint Server does not properly sanitize a specially crafted request to an affected SharePoint server.

What might an attacker use the vulnerability to do?An attacker who successfully exploited this vulnerability could read content that the attacker is not authorized to read, use the victim's identity to take actions on the SharePoint site on behalf of the victim, such as change permissions and delete content, and inject malicious content in the browser of the victim.

How could an attacker exploit the vulnerability?An authenticated attacker could exploit this vulnerability by sending a specially crafted request to an affected SharePoint server.

What systems are primarily at risk from the vulnerability?Any system running an affected version of SharePoint Server is primarily at risk from the vulnerability.

What does the update do?The update addresses the vulnerability by helping to ensure that SharePoint Server properly sanitizes user input.

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.

A remote code execution vulnerability exists in Microsoft Web Applications. An authenticated attacker who successfully exploited this vulnerability could run arbitrary code in the security context of the W3WP service account.

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

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:

To exploit this vulnerability, an attacker must be able to authenticate on the target SharePoint site. Note that this is not a mitigating factor if the SharePoint site is configured to allow anonymous users to access the site. By default, anonymous access is not enabled.

Workarounds

Microsoft has not identified any workarounds for this vulnerability.

FAQ

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

What causes the vulnerability?When page content is not properly sanitized, conditions exist where an attacker could run arbitrary code in the security context of the W3WP service account.

What might an attacker use the vulnerability to do?An attacker who successfully exploited the vulnerability could run arbitrary code in the security context of the W3WP service account on the target SharePoint site.

How could an attacker exploit the vulnerability?An authenticated attacker could attempt to exploit the vulnerability by sending specially crafted page content to a SharePoint server.

What systems are primarily at risk from the vulnerability?Systems that are running an affected version of SharePoint server are primarily at risk.

What does the update do?The update addresses the vulnerability by correcting how affected Web Applications sanitize specially crafted page content.

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.

Note for SharePoint Server The detection tools (such as Microsoft Update, WSUS, MBSA, SMS, and System Center Configuration Manager) are applicable for single-server Microsoft SharePoint Server deployments. The detection tools do not detect the applicability of the updates on systems configured as part of a multiple-system SharePoint server farm. For recommended instructions on how to apply updates to SharePoint Server, see Deploy software updates for SharePoint 2013.

In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.

In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.

In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.

In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.

In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.

In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.

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.

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.