Security Bulletin

Microsoft Security Bulletin MS12-011 - Important

Vulnerabilities in Microsoft SharePoint Could Allow Elevation of Privilege (2663841)

Published: February 14, 2012

Version: 1.0

General Information

Executive Summary

This security update resolves three privately reported vulnerabilities in Microsoft SharePoint and Microsoft SharePoint Foundation. These vulnerabilities could allow elevation of privilege or information disclosure if a user clicked a specially crafted URL.

This security update is rated Important for Microsoft Office SharePoint Server 2010 and Microsoft SharePoint Foundation 2010. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerabilities by correcting the way that Microsoft SharePoint validates and sanitizes user input. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

Recommendation. 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 in supported editions of Windows XP and Windows Server 2003, see Microsoft Knowledge Base Article 294871. For information about automatic updating in supported editions of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, see Understanding Windows automatic updating.

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

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

Known Issues. Microsoft Knowledge Base Article 2663841 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues. When currently known issues and recommended solutions pertain only to specific releases of this software, this article provides links to further articles.

Affected and Non-Affected Software

The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.

Affected Software

Microsoft Server Software 

Software Update Package Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by this Update
Microsoft SharePoint Server
Microsoft SharePoint Server 2010 and Microsoft SharePoint Server 2010 Service Pack 1 Microsoft SharePoint Server 2010 and Microsoft SharePoint Server 2010 Service Pack 1 (moss) (KB2597124) Elevation of Privilege Important No bulletin replaced by KB2597124
Microsoft SharePoint Foundation
Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Foundation 2010 Service Pack 1 Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Foundation 2010 Service Pack 1 (sts) (KB2553413) Elevation of Privilege Important No bulletin replaced by KB2553413

Non-Affected Software 

Office and Other Software
Microsoft Office Groove 2007 Service Pack 2
Microsoft SharePoint Workspace 2010 and Microsoft SharePoint Workspace 2010 Service Pack 1 (32-bit editions)
Microsoft SharePoint Workspace 2010 and Microsoft SharePoint Workspace 2010 Service Pack 1 (64-bit editions)
Microsoft Office SharePoint Portal Server 2003 Service Pack 3
Microsoft Office Forms Server 2007 Service Pack 2 and Microsoft Office Forms Server 2007 Service Pack 3 (32-bit editions)
Microsoft Office Forms Server 2007 Service Pack 2 and Microsoft Office Forms Server 2007 Service Pack 3 (64-bit editions)
Microsoft Office SharePoint Server 2007 Service Pack 2 and Microsoft Office SharePoint Server 2007 Service Pack 3 (32-bit editions)
Microsoft Office SharePoint Server 2007 Service Pack 2 and Microsoft Office SharePoint Server 2007 Service Pack 3 (64-bit editions)
Microsoft Office Groove Data Bridge Server 2007 Service Pack 2 and Microsoft Office Groove Data Bridge Server 2007 Service Pack 3
Microsoft Office Groove Management Server 2007 Service Pack 2 and Microsoft Office Groove Management Server 2007 Service Pack 3
Microsoft Groove Server 2010 and Microsoft Groove Server 2010 Service Pack 1
Microsoft Windows SharePoint Services 2.0
Microsoft Windows SharePoint Services 3.0 Service Pack 2 and Microsoft Windows SharePoint Services 3.0 Service Pack 3 (32-bit versions)
Microsoft Windows SharePoint Services 3.0 Service Pack 2 and Microsoft Windows SharePoint Services 3.0 Service Pack 3 (64-bit versions)

Where are the file information details?
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.

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.

Does this update contain any security-related changes to functionality?
Yes. In addition to the changes that are listed in the Vulnerability Information section of this bulletin, this update includes a defense-in-depth update to help improve Microsoft SharePoint's handling of web services access controls.

What is defense-in-depth?
In information security, defense-in-depth refers to an approach in which multiple layers of defense are in place to help prevent attackers from compromising the security of a network or system.

I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. For more information about the product lifecycle, visit the Microsoft Support Lifecycle website.

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

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

Vulnerability Information

Severity Ratings and Vulnerability Identifiers

The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the February bulletin summary. For more information, see Microsoft Exploitability Index.

Affected Software XSS in inplview.aspx Vulnerability - CVE-2012-0017 XSS in themeweb.aspx Vulnerability - CVE-2012-0144 XSS in wizardlist.aspx Vulnerability - CVE-2012-0145 Aggregate Severity Rating
Microsoft SharePoint Server
Microsoft Office SharePoint Server 2010 and Microsoft Office SharePoint Server 2010 Service Pack 1 Not applicable Important  Elevation of Privilege Important  Elevation of Privilege Important
Microsoft SharePoint Foundation
Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Foundation 2010 Service Pack 1 Important  Elevation of Privilege Important  Elevation of Privilege Important  Elevation of Privilege Important

XSS in inplview.aspx Vulnerability - CVE-2012-0017

A cross-site scripting vulnerability exists in Microsoft SharePoint 2010 that could result in information disclosure or elevation of privilege if a user clicks a specially crafted URL containing malicious JavaScript elements. Due to the vulnerability, when the malicious JavaScript is echoed back to the user's browser, the resulting page could allow an attacker to issue SharePoint commands in the context of the authenticated user on the targeted SharePoint site.

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

Mitigating Factors for XSS in inplview.aspx Vulnerability - CVE-2012-0017

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:

  • Internet Explorer 8 and Internet Explorer 9 users browsing to a SharePoint site in the Internet Zone are at a reduced risk because, by default, the XSS Filter in Internet Explorer 8 and Internet Explorer 9 prevents this attack in the Internet Zone. The XSS Filter in Internet Explorer 8 and Internet Explorer 9, however, is not enabled by default in the Intranet Zone.
  • An attacker can cause arbitrary JavaScript to be run when the user clicks a specially crafted URL, but the attacker would not be able to steal the logged-on user's authentication credentials due to the way that SharePoint Server handles the HttpOnly authentication cookie.

Workarounds for XSS in inplview.aspx Vulnerability - CVE-2012-0017

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:

  • Enable Internet Explorer 8 and Internet Explorer 9 XSSfilter in the Local intranet security zone

    You can help protect against exploitation of this vulnerability by changing your settings to enable the XSS filter in the Local intranet security zone. (XSS filter is enabled by default in the Internet security zone.) To do this, perform the following steps:

    1. In Internet Explorer 8 or Internet Explorer 9, click Internet Options on the Tools menu.
    2. Click the Security tab.
    3. Click Local intranet, and then click Custom Level.
    4. Under Settings, in the Scripting section, under Enable XSS filter, click Enable, and then click OK.
    5. Click OK two times to return to Internet Explorer.

    Impact of workaround. Internal sites not previously flagged as being XSS risks could be flagged.

    How to undo the workaround. 

    To undo this workaround, perform the following steps:

    1. In Internet Explorer 8 or Internet Explorer 9, click Internet Options on the Tools menu.
    2. Click the Security tab.
    3. Click Local intranet, and then click Custom Level.
    4. Under Settings, in the Scripting section, under Enable XSS filter, click Disable, and then click OK.
    5. Click OK two times to return to Internet Explorer.

FAQ for XSS in inplview.aspx Vulnerability - CVE-2012-0017

What is the scope of the vulnerability?
This is a cross-site scripting vulnerability that could result in elevation of privilege or information disclosure.

What causes the vulnerability?
The vulnerability is caused when Microsoft SharePoint does not properly handle malicious JavaScript elements contained within a specially crafted URL, allowing the script to be displayed back to the user's browser.

What is cross-site scripting?
Cross-site scripting (XSS) is a class of security vulnerability that can enable an attacker to inject script code into a user's session with a website. The vulnerability can affect web servers that dynamically generate HTML pages. If these servers embed browser input in the dynamic pages that they send back to the browser, these servers can be manipulated to include maliciously supplied content in the dynamic pages. This can allow malicious script to be executed. Web browsers may perpetuate this problem through their assumptions of trusted sites and their use of cookies to maintain persistent state with the websites that they frequent. An XSS attack does not modify website content. Instead, it inserts new, malicious script that can execute at the browser in the context that is associated with a trusted 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?
For this vulnerability to be exploited, a user must click a specially crafted URL that takes the user to a targeted SharePoint site that then displays the script back to the user's browser.

In an email attack scenario, an attacker could exploit the vulnerability by sending an email message containing the specially crafted URL to the user of the targeted SharePoint site and by convincing the user to click on the specially crafted URL.

In a web-based attack scenario, an attacker would have to host a website that contains a specially crafted URL to the targeted SharePoint site that is used to attempt to exploit this vulnerability. In addition, compromised websites and websites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted website. Instead, an attacker would have to convince them to visit the website, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the attacker's website, and then convince them to click on the specially crafted URL.

What systems are primarily at risk from the vulnerability?
Systems where users connect to a SharePoint server, such as workstations or terminal servers, are primarily at risk.

What does the update do?
The update addresses the vulnerability by correcting the way that Microsoft SharePoint validates and 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.

XSS in themeweb.aspx Vulnerability - CVE-2012-0144

A cross-site scripting vulnerability exists in Microsoft SharePoint 2010 that could result in information disclosure or elevation of privilege if a user clicks a specially crafted URL containing malicious JavaScript elements. Due to the vulnerability, when the malicious JavaScript is echoed back to the user's browser, the resulting page could allow an attacker to issue SharePoint commands in the context of the authenticated user on the targeted SharePoint site.

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

Mitigating Factors for XSS in themeweb.aspx Vulnerability - CVE-2012-0144

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:

  • Internet Explorer 8 and Internet Explorer 9 users browsing to a SharePoint site in the Internet Zone are at a reduced risk because, by default, the XSS Filter in Internet Explorer 8 and Internet Explorer 9 prevents this attack in the Internet Zone. The XSS Filter in Internet Explorer 8 and Internet Explorer 9, however, is not enabled by default in the Intranet Zone.
  • An attacker can cause arbitrary JavaScript to be run when the user clicks a specially crafted URL, but the attacker would not be able to steal the logged-on user's authentication credentials due to the way that SharePoint Server handles the HttpOnly authentication cookie.

Workarounds for XSS in themeweb.aspx Vulnerability - CVE-2012-0144

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:

  • Enable Internet Explorer 8 and Internet Explorer 9 XSSfilter in the Local intranet security zone

    You can help protect against exploitation of this vulnerability by changing your settings to enable the XSS filter in the Local intranet security zone. (XSS filter is enabled by default in the Internet security zone.) To do this, perform the following steps:

    1. In Internet Explorer 8 or Internet Explorer 9, click Internet Options on the Tools menu.
    2. Click the Security tab.
    3. Click Local intranet, and then click Custom Level.
    4. Under Settings, in the Scripting section, under Enable XSS filter, click Enable, and then click OK.
    5. Click OK two times to return to Internet Explorer.

    Impact of workaround. Internal sites not previously flagged as being XSS risks could be flagged.

    How to undo the workaround. 

    To undo this workaround, perform the following steps:

    1. In Internet Explorer 8 or Internet Explorer 9, click Internet Options on the Tools menu.
    2. Click the Security tab.
    3. Click Local intranet, and then click Custom Level.
    4. Under Settings, in the Scripting section, under Enable XSS filter, click Disable, and then click OK.
    5. Click OK two times to return to Internet Explorer.

FAQ for XSS in themeweb.aspx Vulnerability - CVE-2012-0144

What is the scope of the vulnerability?
This is a cross-site scripting vulnerability that could result in elevation of privilege or information disclosure.

What causes the vulnerability?
The vulnerability is caused when Microsoft SharePoint does not properly handle malicious JavaScript elements contained within a specially crafted URL, allowing the script to be displayed back to the user's browser.

What is cross-site scripting?
Cross-site scripting (XSS) is a class of security vulnerability that can enable an attacker to inject script code into a user's session with a website. The vulnerability can affect web servers that dynamically generate HTML pages. If these servers embed browser input in the dynamic pages that they send back to the browser, these servers can be manipulated to include maliciously supplied content in the dynamic pages. This can allow malicious script to be executed. Web browsers may perpetuate this problem through their assumptions of trusted sites and their use of cookies to maintain persistent state with the websites that they frequent. An XSS attack does not modify website content. Instead, it inserts new, malicious script that can execute at the browser in the context that is associated with a trusted 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?
For this vulnerability to be exploited, a user must click a specially crafted URL that takes the user to a targeted SharePoint site that then displays the script back to the user's browser.

In an email attack scenario, an attacker could exploit the vulnerability by sending an email message containing the specially crafted URL to the user of the targeted SharePoint site and by convincing the user to click on the specially crafted URL.

In a web-based attack scenario, an attacker would have to host a web site that contains a specially crafted URL to the targeted SharePoint site that is used to attempt to exploit this vulnerability. In addition, compromised websites and websites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted website. Instead, an attacker would have to convince them to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes them to the attacker's website, and then convince them to click on the specially crafted URL.

What systems are primarily at risk from the vulnerability?
Systems where users connect to a SharePoint server, such as workstations or terminal servers, are primarily at risk.

What does the update do?
The update addresses the vulnerability by correcting the way that Microsoft SharePoint validates and 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.

XSS in wizardlist.aspx Vulnerability - CVE-2012-0145

A cross-site scripting vulnerability exists in Microsoft SharePoint 2010 that could result in information disclosure or elevation of privilege if a user clicks a specially crafted URL containing malicious JavaScript elements. Due to the vulnerability, when the malicious JavaScript is echoed back to the user's browser, the resulting page could allow an attacker to issue SharePoint commands in the context of the authenticated user on the targeted SharePoint site.

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

Mitigating Factors for XSS in wizardlist.aspx Vulnerability - CVE-2012-0145

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:

  • Internet Explorer 8 and Internet Explorer 9 users browsing to a SharePoint site in the Internet Zone are at a reduced risk because, by default, the XSS Filter in Internet Explorer 8 and Internet Explorer 9 prevents this attack in the Internet Zone. The XSS Filter in Internet Explorer 8 and Internet Explorer 9, however, is not enabled by default in the Intranet Zone.
  • An attacker can cause arbitrary JavaScript to be run when the user clicks a specially crafted URL, but the attacker would not be able to steal the logged-on user's authentication credentials due to the way that SharePoint Server handles the HttpOnly authentication cookie.

Workarounds for XSS in wizardlist.aspx Vulnerability - CVE-2012-0145

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:

  • Enable Internet Explorer 8 and Internet Explorer 9 XSSfilter in the Local intranet security zone

    You can help protect against exploitation of this vulnerability by changing your settings to enable the XSS filter in the Local intranet security zone. (XSS filter is enabled by default in the Internet security zone.) To do this, perform the following steps:

    1. In Internet Explorer 8 or Internet Explorer 9, click Internet Options on the Tools menu.
    2. Click the Security tab.
    3. Click Local intranet, and then click Custom Level.
    4. Under Settings, in the Scripting section, under Enable XSS filter, click Enable, and then click OK.
    5. Click OK two times to return to Internet Explorer.

    Impact of workaround. Internal sites not previously flagged as being XSS risks could be flagged.

    How to undo the workaround. 

    To undo this workaround, perform the following steps:

    1. In Internet Explorer 8 or Internet Explorer 9, click Internet Options on the Tools menu.
    2. Click the Security tab.
    3. Click Local intranet, and then click Custom Level.
    4. Under Settings, in the Scripting section, under Enable XSS filter, click Disable, and then click OK.
    5. Click OK two times to return to Internet Explorer.

FAQ for XSS in wizardlist.aspx Vulnerability - CVE-2012-0145

What is the scope of the vulnerability?
This is a cross-site scripting vulnerability that could result in elevation of privilege or information disclosure.

What causes the vulnerability?
The vulnerability is caused when Microsoft SharePoint does not properly handle malicious JavaScript elements contained within a specially crafted URL, allowing the script to be displayed back to the user's browser.

What is cross-site scripting?
Cross-site scripting (XSS) is a class of security vulnerability that can enable an attacker to inject script code into a user's session with a website. The vulnerability can affect web servers that dynamically generate HTML pages. If these servers embed browser input in the dynamic pages that they send back to the browser, these servers can be manipulated to include maliciously supplied content in the dynamic pages. This can allow malicious script to be executed. Web browsers may perpetuate this problem through their assumptions of trusted sites and their use of cookies to maintain persistent state with the websites that they frequent. An XSS attack does not modify website content. Instead, it inserts new, malicious script that can execute at the browser in the context that is associated with a trusted 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?
For this vulnerability to be exploited, a user must click a specially crafted URL that takes the user to a targeted SharePoint site that then displays the script back to the user's browser.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending an e-mail message containing the specially crafted URL to the user of the targeted SharePoint site and by convincing the user to click on the specially crafted URL.

In a web-based attack scenario, an attacker would have to host a Web site that contains a specially crafted URL to the targeted SharePoint site that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the attacker's Web site, and then convince them to click on the specially crafted URL.

What systems are primarily at risk from the vulnerability?
Systems where users connect to a SharePoint server, such as workstations or terminal servers, are primarily at risk.

What does the update do?
The update addresses the vulnerability by correcting the way that Microsoft SharePoint validates and 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.

Update Information

Detection and Deployment Tools and Guidance

Security Central

Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security website provides additional information about security in Microsoft products.

Security updates are available from Microsoft Update and Windows Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."

For customers of Microsoft Office for Mac, Microsoft AutoUpdate for Mac can help keep your Microsoft software up to date. For more information about using Microsoft AutoUpdate for Mac, see Check for software updates automatically.

Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, "MS07-036"), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.

Detection and Deployment Guidance

Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see Microsoft Knowledge Base Article 961747.

Microsoft Baseline Security Analyzer

Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.

The following table provides the MBSA detection summary for this security update.

Software MBSA
Microsoft Office SharePoint Server 2010 and Microsoft Office SharePoint Server 2010 Service Pack 1 Yes
SharePoint Foundation 2010 and SharePoint Foundation 2010 Service Pack 1 Yes

Note For customers using legacy software not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, please visit Microsoft Baseline Security Analyzer and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools.

Windows Server Update Services

Windows Server Update Services (WSUS) enables information technology administrators to deploy the latest Microsoft product updates to computers that are running the Windows operating system. For more information about how to deploy security updates using Windows Server Update Services, see the TechNet article, Windows Server Update Services.

Systems Management Server

The following table provides the SMS detection and deployment summary for this security update.

Software SMS 2003 with ITMU Configuration Manager 2007
Microsoft Office SharePoint Server 2010 and Microsoft Office SharePoint Server 2010 Service Pack 1 Yes. See Note for Microsoft Office SharePoint Server 2010 below Yes. See Note for Microsoft Office SharePoint Server 2010 below
SharePoint Foundation 2010 and SharePoint Foundation 2010 Service Pack 1 Yes Yes

Note Microsoft discontinued support for SMS 2.0 on April 12, 2011. For SMS 2003, Microsoft also discontinued support for the Security Update Inventory Tool (SUIT) on April 12, 2011. Customers are encouraged to upgrade to System Center Configuration Manager 2007. For customers remaining on SMS 2003 Service Pack 3, the Inventory Tool for Microsoft Updates (ITMU) is also an option.

For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.

System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007.

For more information about SMS, visit the SMS website.

For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.

Note for Microsoft Office SharePoint Server 2010 The detection table described above is based on single-server Microsoft Office SharePoint Server 2010 deployments. The detection tools do not detect the applicability of the update on systems configured as part of a multiple-system SharePoint server farms.

Note If you have used an Administrative Installation Point (AIP) for deploying Office XP or Office 2003, you may not be able to deploy the update using SMS if you have updated the AIP from the original baseline. For more information, see the Office Administrative Installation Point heading in this section.

Office Administrative Installation Point

If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your system.

Update Compatibility Evaluator and Application Compatibility Toolkit

Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit.

The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.

Security Update Deployment

Affected Software

For information about the specific security update for your affected software, click the appropriate link:

SharePoint Server 2010 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs There are no more service packs planned for this software. The update for this issue may be included in a future update rollup.
Deployment  
Installing without user intervention For Microsoft Office SharePoint Server 2010 and Microsoft Office SharePoint Server 2010 Service Pack 1:\ moss2010-kb2597124-fullfile-x64-glb.exe /passive
Installing without restarting For Microsoft Office SharePoint Server 2010 and Microsoft Office SharePoint Server 2010 Service Pack 1:\ moss2010-kb2597124-fullfile-x64-glb.exe /norestart
Update log file Not applicable
Further information For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance.
Restart Requirement  
Restart required? In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.\ \ To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
Hotpatching Not applicable
Removal Information This security update cannot be removed.
File Information See Microsoft Knowledge Base Article 2597124
Registry Key Verification Not applicable

Deployment Information

Installing the Update

You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.

This security update requires that Windows Installer 3.1 or later version be installed on the system.

To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft websites:

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Switch Description
/? or /help Displays usage dialog.
/passive Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel.
/quiet Specifies quiet mode, or suppresses prompts, when files are being extracted.
/norestart Suppresses restarting the system if the update requires a restart.
/forcerestart Automatically restarts the system after applying the update, regardless of whether the update requires the restart.
/extract Extracts the files without installing them. You are prompted for a target folder.
/extract:<path> Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/lang:<LCID> Forces the use of a specific language, when the update package supports that language.
/log:<log file> Enables logging, by both Vnox and Installer, during the update installation.

Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.

Removing the Update

This security update cannot be removed.

Verifying that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

    To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification

    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start and then enter an update file name in Start Search.
    2. When the file appears under Programs, right-click on the file name and click Properties.
    3. Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
    4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
    5. Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Microsoft SharePoint Foundation 2010 (all versions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs There are no more service packs planned for this software. The update for this issue may be included in a future update rollup.
Deployment  
Installing without user intervention For Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Foundation 2010 Service Pack 1:\ sts2010-kb2553413-fullfile-x64-glb.exe /passive
Installing without restarting For Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Foundation 2010 Service Pack 1:\ sts2010-kb2553413-fullfile-x64-glb.exe /norestart
Update log file Not applicable
Further information For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance.
Restart Requirement  
Restart required? In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.\ \ To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
Hotpatching Not applicable
Removal Information This security update cannot be removed.
File Information See Microsoft Knowledge Base Article 2553413
Registry Key Verification Not applicable

Deployment Information

Installing the Update

You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.

This security update requires that Windows Installer 3.1 or later version be installed on the system.

To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft websites:

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Switch Description
/? or /help Displays usage dialog.
/passive Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel.
/quiet Specifies quiet mode, or suppresses prompts, when files are being extracted.
/norestart Suppresses restarting the system if the update requires a restart.
/forcerestart Automatically restarts the system after applying the update, regardless of whether the update requires the restart.
/extract Extracts the files without installing them. You are prompted for a target folder.
/extract:<path> Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/lang:<LCID> Forces the use of a specific language, when the update package supports that language.
/log:<log file> Enables logging, by both Vnox and Installer, during the update installation.

Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.

Removing the Update

This security update cannot be removed.

Verifying that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

    To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification

    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start and then enter an update file name in Start Search.
    2. When the file appears under Programs, right-click on the file name and click Properties.
    3. Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
    4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
    5. Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Other Information

Acknowledgments

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

  • John Hollenberger for reporting the XSS in themeweb.aspx (CVE-2012-0144)
  • Rocco Calvi of stratsec for reporting the XSS in wizardlist.aspx (CVE-2012-0145)
  • Giorgio Fedon of Minded Security for working with us on a defense-in-depth update to help improve the handling of web services access controls in Microsoft SharePoint

Microsoft Active Protections Program (MAPP)

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

Support

  • Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY (1-866-727-2338). There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support.
  • International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support website.

Disclaimer

The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

Revisions

  • V1.0 (February 14, 2012): Bulletin published.

Built at 2014-04-18T13:49:36Z-07:00