Security Bulletin
Microsoft Security Bulletin MS12-050 - Important
Vulnerabilities in SharePoint Could Allow Elevation of Privilege (2695502)
Published: July 10, 2012 | Updated: January 15, 2014
Version: 2.2
General Information
Executive Summary
This security update resolves one publicly disclosed and five privately reported vulnerabilities in Microsoft SharePoint and Windows SharePoint Services. The most severe vulnerabilities could allow elevation of privilege if a user clicks a specially crafted URL that takes the user to a targeted SharePoint site.
This security update is rated Important for supported editions of Microsoft InfoPath 2007, Microsoft InfoPath 2010, Microsoft SharePoint Server 2007, Microsoft SharePoint Server 2010, and Microsoft Groove Server 2010; and for supported versions of Microsoft Windows SharePoint Services 2.0, Microsoft Windows SharePoint Services 3.0, and SharePoint Foundation 2010. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerabilities by modifying the way that HTML strings are sanitized and 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 2695502 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 Office
Microsoft Server Software
| Software | Component | Maximum Security Impact | Aggregate Severity Rating | Updates Replaced |
|---|---|---|---|---|
| Microsoft SharePoint Server | ||||
| Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions) | Microsoft Office SharePoint Server 2007 Service Pack 2 (coreserver) (32-bit editions)[1](KB2596663) Microsoft Office SharePoint Server 2007 Service Pack 2 (xlsrvwfe) (32-bit editions) (KB2596942) | Elevation of Privilege | Important | KB2508964 in MS11-074 replaced by KB2596663 |
| Microsoft Office SharePoint Server 2007 Service Pack 3 (32-bit editions)[1] | Microsoft Office SharePoint Server 2007 Service Pack 3 (coreserver) (32-bit editions)[1](KB2596663) Microsoft Office SharePoint Server 2007 Service Pack 3 (xlsrvwfe) (32-bit editions) (KB2596942) | Elevation of Privilege | Important | KB2508964 in MS11-074 replaced by KB2596663 |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions)[1] | Microsoft Office SharePoint Server 2007 Service Pack 2 (coreserver) (64-bit editions)[1](KB2596663) Microsoft Office SharePoint Server 2007 Service Pack 2 (xlsrvwfe) (64-bit editions) (KB2596942) | Elevation of Privilege | Important | KB2508964 in MS11-074 replaced by KB2596663 |
| Microsoft Office SharePoint Server 2007 Service Pack 3 (64-bit editions)[1] | Microsoft Office SharePoint Server 2007 Service Pack 3 (coreserver) (64-bit editions)[1](KB2596663) Microsoft Office SharePoint Server 2007 Service Pack 2 (xlsrvwfe) (64-bit editions) (KB2596942) | Elevation of Privilege | Important | KB2508964 in MS11-074 replaced by KB2596663 |
| Microsoft SharePoint Server 2010 | Microsoft SharePoint Server 2010 (wosrv) (KB2553424) Microsoft SharePoint Server 2010 (coreserverloc) (KB2553194) | Elevation of Privilege | Important | KB2566960 in MS11-074 replaced by KB2553424 KB2566954 in MS11-074 replaced by KB2553194 |
| Microsoft SharePoint Server 2010 Service Pack 1 | Microsoft SharePoint Server 2010 Service Pack 1 (wosrv) (KB2553424) Microsoft SharePoint Server 2010 Service Pack 1 (coreserverloc) (KB2553194) | Elevation of Privilege | Important | KB2566960 in MS11-074 replaced by KB2553424 KB2566954 in MS11-074 replaced by KB2553194 |
| Microsoft Groove Server | ||||
| Microsoft Groove Server 2010 (KB2589325) | Not applicable | Elevation of Privilege | Important | KB2553005 in MS11-074 replaced by KB2589325 |
| Microsoft Groove Server 2010 Service Pack 1 (KB2589325) | Not applicable | Elevation of Privilege | Important | KB2553005 in MS11-074 replaced by KB2589325 |
| Windows SharePoint Services and Microsoft SharePoint Foundation | ||||
| Microsoft Windows SharePoint Services 2.0[2] (KB2760604) | Not applicable | Elevation of Privilege | Important | KB2494007 in MS11-074 replaced by KB2760604 |
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (32-bit version) (KB2596911) | Not applicable | Elevation of Privilege | Important | KB2493987 in MS11-074 replaced by KB2596911 |
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (64-bit version) (KB2596911) | Not applicable | Elevation of Privilege | Important | KB2493987 in MS11-074 replaced by KB2596911 |
| Microsoft SharePoint Foundation 2010 (KB2553365) | Not applicable | Elevation of Privilege | Important | KB2494001 in MS11-074 replaced by KB2553365 |
| Microsoft SharePoint Foundation 2010 Service Pack 1 (KB2553365) | Not applicable | Elevation of Privilege | Important | KB2494001 in MS11-074 replaced by KB2553365 |
[1]For supported editions of Microsoft Office SharePoint Server 2007, in addition to security update packages for Microsoft Office SharePoint 2007 (KB2596663 and KB2596942), customers also need to install the security update for Microsoft Windows SharePoint Services 3.0 (KB2596911) to be protected from the vulnerabilities described in this bulletin.
[2]This update is available from the Microsoft Download Center only.
Microsoft Office Web Apps
| Software | Maximum Security Impact | Aggregate Severity Rating | Updates Replaced |
|---|---|---|---|
| Microsoft Office Web Apps 2010\ (KB2598239) | Elevation of Privilege | Important | KB2566449 in MS11-074 replaced by KB2598239 |
| Microsoft Office Web Apps 2010 Service Pack 1\ (KB2598239) | Elevation of Privilege | Important | KB2566449 in MS11-074 replaced by KB2598239 |
Non-Affected Software
| Office and Other Software |
|---|
| Microsoft SharePoint Portal Server 2003 Service Pack 3 |
| Microsoft InfoPath 2003 Service Pack 3 |
| Microsoft Groove 2007 Service Pack 2 |
| Microsoft Groove 2007 Service Pack 3 |
| Microsoft Groove Server 2007 Service Pack 2 |
| Microsoft Groove Server 2007 Service Pack 3 |
| Microsoft SharePoint Workspace 2010 (32-bit editions) |
| Microsoft SharePoint Workspace 2010 Service Pack 1 (32-bit editions) |
| Microsoft SharePoint Workspace 2010 (64-bit editions) |
| Microsoft SharePoint Workspace 2010 Service Pack 1 (64-bit editions) |
Frequently Asked Questions (FAQ) Related to This Security Update
Where are the file information details?
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.
Where are the hashes of the security updates?
The SHA1 and SHA2 hashes of the security updates can be used to verify the authenticity of downloaded security update packages. For the hash information pertaining to this update, see Microsoft Knowledge Base Article 2695502.
How is this security update related to MS12-037 and MS12-039?
The HTML Sanitization Vulnerability (CVE-2012-1858) described in this bulletin also affects Internet Explorer and Microsoft Lync. However, you may install only the updates that correspond to the software you have installed on your systems. If you have installed Microsoft SharePoint, apply the required updates according to this bulletin. If you have installed Internet Explorer, apply the required updates according to MS12-037. If you have installed Microsoft Lync, apply the required updates according to MS12-039.
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 of 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.
For administrators and enterprise installations, or end users who want to install this security update manually, depending on their configuration of Microsoft Office SharePoint Server, not all the server-package updates listed in this bulletin may apply. For more information on the applicability of these server-package updates in a SharePoint environment, see Microsoft Knowledge Base Article 2695502.
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.
What is Microsoft Groove Server 2010?
Microsoft Groove Server 2010 provides comprehensive services for managing Microsoft SharePoint Workspace. Groove Server 2010 contains two components: Groove Server 2010 Manager and Groove Server 2010 Relay, each of which runs on a Windows server on an enterprise network.
What is Microsoft SharePoint Foundation 2010?
Microsoft SharePoint Foundation 2010 is the new version of Microsoft Windows SharePoint Services. It is the essential solution for organizations that need a secure, manageable, Web-based collaboration platform. SharePoint helps teams stay connected and productive by providing easy access to the people, documents, and information that they need to make well-informed decisions and get work done. Use SharePoint Foundation to coordinate schedules, organize documents, and participate in discussions through team workspaces, blogs, wikis, and document libraries on the platform that is the underlying infrastructure for SharePoint Server.
What is Microsoft Windows SharePoint Services 3.0?
Windows SharePoint Services 3.0 provides a platform for collaborative applications, offering a common framework for document management and a common repository for storing documents of all types. It exposes key Windows Server services like Windows Workflow Services and Windows Rights Management Services.
Windows SharePoint Services 3.0 is provided as a free download for supported editions of Windows Server 2003 and Windows Server 2008.
How is Microsoft Windows SharePoint Services 3.0 related to Microsoft Office SharePoint Server 2007?
Microsoft Office SharePoint Server 2007 is an integrated suite of server capabilities built on top of Windows SharePoint Services 3.0.
For systems with Microsoft Office SharePoint Server 2007 installed, you will need to apply the KB2596911 update for Windows SharePoint Services 3.0. There is no configuration where you can only have Microsoft Office SharePoint Server 2007 and not Microsoft Windows SharePoint Services 3.0.
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 July bulletin summary. For more information, see Microsoft Exploitability Index.
| Affected Software | HTML Sanitization Vulnerability - CVE-2012-1858 | XSS scriptresx.ashx Vulnerability - CVE-2012-1859 | SharePoint Search Scope Vulnerability - CVE-2012-1860 | SharePoint Script in Username Vulnerability - CVE-2012-1861 | SharePoint URL Redirection Vulnerability - CVE-2012-1862 | SharePoint Reflected List Parameter Vulnerability - CVE-2012-1863 | Aggregate Severity Rating |
|---|---|---|---|---|---|---|---|
| Microsoft Office Client Software | |||||||
| Microsoft InfoPath 2007 Service Pack 2 | Important Information Disclosure | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Important |
| Microsoft InfoPath 2007 Service Pack 3 | Important Information Disclosure | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Important |
| Microsoft InfoPath 2010 (32-bit editions) | Important Information Disclosure | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Important |
| Microsoft InfoPath 2010 Service Pack 1 (32-bit editions) | Important Information Disclosure | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Important |
| Microsoft InfoPath 2010 (64-bit editions) | Important Information Disclosure | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Important |
| Microsoft InfoPath 2010 Service Pack 1 (64-bit editions) | Important Information Disclosure | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Important |
| Microsoft SharePoint Server | |||||||
| Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions) | Important Information Disclosure | Not applicable | Moderate Information Disclosure | Not applicable | Moderate Information Disclosure | Important Elevation of Privilege | Important |
| Microsoft Office SharePoint Server 2007 Service Pack 3 (32-bit editions) | Important Information Disclosure | Not applicable | Moderate Information Disclosure | Not applicable | Moderate Information Disclosure | Important Elevation of Privilege | Important |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions) | Important Information Disclosure | Not applicable | Moderate Information Disclosure | Not applicable | Moderate Information Disclosure | Important Elevation of Privilege | Important |
| Microsoft Office SharePoint Server 2007 Service Pack 3 (64-bit editions) | Important Information Disclosure | Not applicable | Moderate Information Disclosure | Not applicable | Moderate Information Disclosure | Important Elevation of Privilege | Important |
| Microsoft SharePoint Server 2010 | Important Information Disclosure | Important Elevation of Privilege | Moderate Information Disclosure | Important Elevation of Privilege | Not applicable | Not applicable | Important |
| Microsoft SharePoint Server 2010 Service Pack 1 | Important Information Disclosure | Important Elevation of Privilege | Moderate Information Disclosure | Important Elevation of Privilege | Not applicable | Not applicable | Important |
| Microsoft Groove Server | |||||||
| Microsoft Groove Server 2010 | Important Information Disclosure | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Important |
| Microsoft Groove Server 2010 Service Pack 1 | Important Information Disclosure | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Important |
| Windows SharePoint Services and Microsoft SharePoint Foundation | |||||||
| Microsoft Windows SharePoint Services 2.0 | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Important Elevation of Privilege | Important |
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (32-bit versions) | Important Information Disclosure | Not applicable | Not applicable | Not applicable | Not applicable | Important Elevation of Privilege | Important |
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (64-bit versions) | Important Information Disclosure | Not applicable | Not applicable | Not applicable | Not applicable | Important Elevation of Privilege | Important |
| SharePoint Foundation 2010 | Important Information Disclosure | Important Elevation of Privilege | Not applicable | Important Elevation of Privilege | Not applicable | Important Elevation of Privilege | Important |
| SharePoint Foundation 2010 Service Pack 1 | Important Information Disclosure | Important Elevation of Privilege | Not applicable | Important Elevation of Privilege | Not applicable | Important Elevation of Privilege | Important |
| Microsoft Office Web Apps | |||||||
| Microsoft Office Web Apps 2010 | Important Information Disclosure | Important Elevation of Privilege | Moderate Information Disclosure | Important Elevation of Privilege | Not applicable | Not applicable | Important |
| Microsoft Office Web Apps 2010 Service Pack 1 | Important Information Disclosure | Important Elevation of Privilege | Moderate Information Disclosure | Important Elevation of Privilege | Not applicable | Not applicable | Important |
HTML Sanitization Vulnerability - CVE-2012-1858
An information disclosure vulnerability exists in the way that HTML strings are sanitized. An attacker who successfully exploited this vulnerability could perform cross-site scripting attacks 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-2012-1858.
Mitigating Factors for HTML Sanitization Vulnerability - CVE-2012-1858
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:
- Only sites that sanitize HTML strings are affected.
Workarounds for HTML Sanitization Vulnerability - CVE-2012-1858
Microsoft has not identified any workarounds for this vulnerability.
FAQ for HTML Sanitization Vulnerability - CVE-2012-1858
What is the scope of the vulnerability?
This is an information disclosure vulnerability. An attacker who successfully exploited the vulnerability could perform persistent cross-site scripting attacks against users of a site that is filtering HTML content via SafeHTML.
What causes the vulnerability?
The vulnerability is caused by the way that HTML strings are sanitized.
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 the vulnerability could perform cross-site scripting attacks against users of a targeted site where HTML strings are sanitized. An attacker could then potentially run script on behalf of a victim user on the site.
How could an attacker exploit the vulnerability?
To exploit this vulnerability, an attacker must have the ability to submit a specially crafted script to a target site that use HTML sanitization. Due to the vulnerability, in specific situations the specially crafted script is not properly sanitized, which subsequently could lead to an attacker-supplied script being run in the security context of a user who views the malicious content.
For cross-site scripting attacks, this vulnerability requires that a user be visiting a compromised site for any malicious action to occur. For instance, after an attacker has successfully submitted specially crafted script to a target site that use HTML sanitization, any webpage on that site that contains the specially crafted script is a potential vector for persistent cross-site scripting attacks. When a user visits a webpage that contains the specially crafted script, the script could be run in the security context of the user.
What systems are primarily at risk from the vulnerability?
Systems where users connect to a site that sanitizes HTML strings, such as workstations or terminal servers, are primarily at risk.
What does the update do?
The update addresses the vulnerability by modifying the way that HTML strings are sanitized.
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-2012-1858.
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 scriptresx.ashx Vulnerability - CVE-2012-1859
A cross-site scripting and elevation of privilege vulnerability exists in SharePoint allows attacker-controlled JavaScript to run in the context of the user clicking a link. This is an elevation of privilege vulnerability as it allows an anonymous attacker to potentially issue SharePoint commands in the context of an authenticated user on the site.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2012-1859.
Mitigating Factors for XSS scriptresx.ashx Vulnerability - CVE-2012-1859
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 host a website that contains a webpage that is used to exploit this vulnerability. In addition, compromised websites and websites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these websites. Instead, an attacker would have to convince users to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes users to the attacker's website.
Workarounds for XSS scriptresx.ashx Vulnerability - CVE-2012-1859
Microsoft has not identified any workarounds for this vulnerability.
FAQ for XSS scriptresx.ashx Vulnerability - CVE-2012-1859
What is the scope of the vulnerability?
This is an elevation of privilege vulnerability.
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 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 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 email message or Instant Messenger message that takes them to the attacker's website, and then convince them to click 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.
SharePoint Search Scope Vulnerability - CVE-2012-1860
An information disclosure vulnerability exists in the way that SharePoint stores search scopes. An attacker could view or tamper with other users' search scopes.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2012-1860.
Mitigating Factors for SharePoint Search Scope Vulnerability - CVE-2012-1860
Microsoft has not identified any mitigating factors for this vulnerability.
Workarounds for SharePoint Search Scope Vulnerability - CVE-2012-1860
Microsoft has not identified any workarounds for this vulnerability.
FAQ for SharePoint Search Scope Vulnerability - CVE-2012-1860
What is the scope of the vulnerability?
This is an information disclosure vulnerability.
What causes the vulnerability?
The vulnerability is caused when Microsoft SharePoint does not properly validate search scope permissions, allowing users to view and modify other users' search scopes.
What might an attacker use the vulnerability to do?
An attacker could use this vulnerability to tamper with and access information about other users' search scopes.
How could an attacker exploit the vulnerability?
To exploit this vulnerability, an attacker would have to tamper with a parameter in the search scope URL of a SharePoint server while logged in.
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.
SharePoint Script in Username Vulnerability - CVE-2012-1861
A cross-site scripting vulnerability exists in SharePoint allows attacker-controlled JavaScript to run in the context of the user clicking a link. This is an elevation of privilege vulnerability as it allows an anonymous attacker to potentially issue SharePoint commands in the context of an authenticated user.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2012-1861.
Mitigating Factors for SharePoint Script in Username Vulnerability - CVE-2012-1861
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 host a website that contains a webpage that is used to exploit this vulnerability. In addition, compromised websites and websites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these websites. Instead, an attacker would have to convince users to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes users to the attacker's website.
Workarounds for SharePoint Script in Username Vulnerability - CVE-2012-1861
Microsoft has not identified any workarounds for this vulnerability.
FAQ for SharePoint Script in Username Vulnerability - CVE-2012-1861
What is the scope of the vulnerability?
This is a cross-site scripting vulnerability which 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 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 email message or Instant Messenger message that takes them to the attacker's website, and then convince them to click 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.
SharePoint URL Redirection Vulnerability - CVE-2012-1862
A URL redirection vulnerability, which could lead to spoofing and information disclosure,exists in SharePoint which could allow an attacker to redirect a user to an external URL.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2012-1862.
Mitigating Factors for SharePoint URL Redirection Vulnerability - CVE-2012-1862
Microsoft has not identified any mitigating factors for this vulnerability.
Workarounds for SharePoint URL Redirection Vulnerability - CVE-2012-1862
Microsoft has not identified any workarounds for this vulnerability.
FAQ for SharePoint URL Redirection Vulnerability - CVE-2012-1862
What is the scope of the vulnerability?
This is a spoofing vulnerability that could lead to information disclosure.
What causes the vulnerability?
The vulnerability is caused when Microsoft SharePoint does not properly validate specially crafted URLs to ensure that users are not redirected to external sites.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could trick a user into being redirected from a targeted SharePoint site to a malicious external website. The malicious website could be designed to impersonate the targeted SharePoint site. This could lead to a user disclosing information under the pretense that the user is visiting the targeted SharePoint site because the user is unaware they have been redirected to the malicious website.
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. There they can be redirected to an external 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.
SharePoint Reflected List Parameter Vulnerability - CVE-2012-1863
A cross-site scripting vulnerability exists in SharePoint allows attacker-controlled JavaScript to run in the context of the user clicking a link. This is an elevation of privilege vulnerability as it allows an anonymous attacker to potentially issue SharePoint commands in the context of an authenticated user.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2012-1863.
Mitigating Factors for SharePoint Reflected List Parameter Vulnerability - CVE-2012-1863
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 host a website that contains a webpage that is used to exploit this vulnerability. In addition, compromised websites and websites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these websites. Instead, an attacker would have to convince users to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes users to the attacker's website.
Workarounds for SharePoint Reflected List Parameter Vulnerability - CVE-2012-1863
Microsoft has not identified any workarounds for this vulnerability.
FAQ for SharePoint Reflected List Parameter Vulnerability - CVE-2012-1863
What is the scope of the vulnerability?
This is a cross-site scripting vulnerability which 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 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 email message or Instant Messenger message that takes them to the attacker's website, and then convince them to click 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 InfoPath 2007 Service Pack 2 | Yes |
| Microsoft InfoPath 2007 Service Pack 3 | Yes |
| Microsoft InfoPath 2010 (32-bit editions) | Yes |
| Microsoft InfoPath 2010 Service Pack 1 (32-bit editions) | Yes |
| Microsoft InfoPath 2010 (64-bit editions) | Yes |
| Microsoft InfoPath 2010 Service Pack 1 (64-bit editions) | Yes |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions) | Yes |
| Microsoft Office SharePoint Server 2007 Service Pack 3 (32-bit editions) | Yes |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions) | Yes |
| Microsoft Office SharePoint Server 2007 Service Pack 3 (64-bit editions) | Yes |
| Microsoft SharePoint Server 2010 | Yes |
| Microsoft SharePoint Server 2010 Service Pack 1 | Yes |
| Microsoft Groove Server 2010 | Yes |
| Microsoft Groove Server 2010 Service Pack 1 | Yes |
| Microsoft Windows SharePoint Services 2.0 | No |
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (32-bit versions) | Yes |
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (64-bit versions) | Yes |
| SharePoint Foundation 2010 | Yes |
| 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 | System Center Configuration Manager |
|---|---|---|
| Microsoft InfoPath 2007 Service Pack 2 | Yes | Yes |
| Microsoft InfoPath 2007 Service Pack 3 | Yes | Yes |
| Microsoft InfoPath 2010 (32-bit editions) | Yes | Yes |
| Microsoft InfoPath 2010 Service Pack 1 (32-bit editions) | Yes | Yes |
| Microsoft InfoPath 2010 (64-bit editions) | Yes | Yes |
| Microsoft InfoPath 2010 Service Pack 1 (64-bit editions) | Yes | Yes |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions) | Yes. See Note for Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2010 below | Yes. See Note for Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2010 below |
| Microsoft Office SharePoint Server 2007 Service Pack 3 (32-bit editions) | Yes. See Note for Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2010 below | Yes. See Note for Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2010 below |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions) | Yes. See Note for Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2010 below | Yes. See Note for Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2010 below |
| Microsoft Office SharePoint Server 2007 Service Pack 3 (64-bit editions) | Yes. See Note for Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2010 below | Yes. See Note for Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2010 below |
| Microsoft SharePoint Server 2010 | Yes. See Note for Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2010 below | Yes. See Note for Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2010 below |
| Microsoft SharePoint Server 2010 Service Pack 1 | Yes. See Note for Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2010 below | Yes. See Note for Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2010 below |
| Microsoft Groove Server 2010 | Yes | Yes |
| Microsoft Groove Server 2010 Service Pack 1 | Yes | Yes |
| Microsoft Windows SharePoint Services 2.0 | No | No |
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (32-bit versions) | Yes | Yes |
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (64-bit versions) | Yes | Yes |
| SharePoint Foundation 2010 | Yes | Yes |
| 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. 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 uses WSUS 3.0 for detection of updates. For more information about System Center Configuration Manager Software Update Management, visit System Center.
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 2007 and Microsoft SharePoint Server 2010 The detection table described above is based on single-server Microsoft Office SharePoint Server 2007 and Microsoft 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.
- For supported versions of Microsoft Office XP, see Creating an Administrative Installation Point. For more information on how to change the source for a client system from an updated administrative installation point to an Office XP original baseline source, see Microsoft Knowledge Base Article 922665.
Note If you plan to manage software updates centrally from an updated administrative image, you can find more information in the article Updating Office XP Clients from a Patched Administrative Image. - For supported versions of Microsoft Office 2003, see Creating an Administrative Installation Point. For more information on how to change the source for a client computer from an updated administrative installation point to an Office 2003 original baseline source or Service Pack 3 (SP3), see Microsoft Knowledge Base Article 902349.
Note If you plan to manage software updates centrally from an updated administrative image, you can find more information in the article, Distributing Office 2003 Product Updates. - For creating a network installation point for supported versions of Microsoft Office, see Create a network installation point for Microsoft Office.
Note If you plan to manage security updates centrally, use Windows Server Update Services. For more information about how to deploy security updates for Microsoft Office, visit the Windows Server Update Services website.
Update Compatibility Evaluator and Application Compatibility Toolkit
Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit.
The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
InfoPath 2007 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
|---|---|
| Deployment | |
| Installing without user intervention | For InfoPath 2007:\ infopath2007-kb2596666-fullfile-x86-glb.exe /passive\ ipeditor2007-kb2596786-fullfile-x86-glb.exe /passive |
| Installing without restarting | For InfoPath 2007:\ infopath2007-kb2596666-fullfile-x86-glb.exe /norestart\ ipeditor2007-kb2596786-fullfile-x86-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 | Use Add or Remove Programs item in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 2596666 and Microsoft Knowledge Base Article 2596786 |
| 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:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Microsoft Windows 2000
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.
Supported Security Update Installation 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
To remove this security update, use the Add or Remove Programs item in Control Panel.
Note When you remove this update, you may be prompted to insert the 2007 Microsoft Office CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs item in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
Verifying that the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. - Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
InfoPath 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 | The update for this issue will be included in a future service pack or update rollup |
|---|---|
| Deployment | |
| Installing without user intervention | For InfoPath 2010 (32-bit editions):\ infopath2010-kb2553431-fullfile-x86-glb.exe /passive\ ipeditor2010-kb2553322-fullfile-x86-glb.exe /passive |
| For InfoPath 2010 (64-bit editions):\ infopath2010-kb2553431-fullfile-x64-glb.exe /passive\ ipeditor2010-kb2553322-fullfile-x64-glb.exe /passive | |
| Installing without restarting | For InfoPath 2010 (32-bit editions):\ infopath2010-kb2553431-fullfile-x86-glb.exe /norestart\ ipeditor2010-kb2553322-fullfile-x86-glb.exe /norestart |
| For InfoPath 2010 (64-bit editions):\ infopath2010-kb2553431-fullfile-x64-glb.exe /norestart\ ipeditor2010-kb2553322-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 | Use Add or Remove Programs item in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 2553431 and Microsoft Knowledge Base Article 2553322 |
| 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:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Microsoft Windows 2000
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.
Supported Security Update Installation 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
To remove this security update, use the Add or Remove Programs item in Control Panel.
Note When you remove this update, you may be prompted to insert the 2007 Microsoft Office CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs item in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
Verifying that the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. - Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
SharePoint Server 2007 (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 2007 (32-bit editions):\ coreserver2007-kb2596663-fullfile-x86-glb.exe /passive\ xlsrvwfe2007-kb2596942-fullfile-x86-glb.exe /passive |
| For Microsoft Office SharePoint Server 2007 (64-bit editions):\ coreserver2007-kb2596663-fullfile-x64-glb.exe /passive\ xlsrvwfe2007-kb2596942-fullfile-x64-glb.exe /passive | |
| Installing without restarting | For Microsoft Office SharePoint Server 2007 (32-bit editions):\ coreserver2007-kb2596663-fullfile-x86-glb.exe /norestart\ xlsrvwfe2007-kb2596942-fullfile-x86-glb.exe /norestart |
| For Microsoft Office SharePoint Server 2007 (64-bit editions):\ coreserver2007-kb2596663-fullfile-x64-glb.exe /norestart\ xlsrvwfe2007-kb2596942-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 2596663and Microsoft Knowledge Base Article 2596942 |
| 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:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Windows 2000
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.
Supported Security Update Installation 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.- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
- Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
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:\ wosrv2010-kb2553424-fullfile-x64-glb.exe /passive\ coreserverloc2010-kb2553194-fullfile-x64-glb.exe /passive |
| Installing without restarting | For Microsoft Office SharePoint Server 2010:\ wosrv2010-kb2553424-fullfile-x64-glb.exe /norestart\ coreserverloc2010-kb2553194-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 2553424 and Microsoft Knowledge Base Article 2553194 |
| 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:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Windows 2000
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.
Supported Security Update Installation 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.- Click Start and then enter an update file name in Start Search.
- When the file appears under Programs, right-click on the file name and click Properties.
- Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- 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.
- 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.
Groove 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 Groove Server 2010:\ emsgrs2010-kb2589325-fullfile-x64-glb.exe /passive |
| Installing without restarting | For Microsoft Groove Server 2010:\ emsgrs2010-kb2589325-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 2589325 |
| 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:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Windows 2000
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.
Supported Security Update Installation 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.- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
- Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Windows SharePoint Services 2.0
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 Windows SharePoint Services 2.0:\ WSS2003-KB2760604-fullfile-ENU.exe /passive |
| Installing without restarting | For Microsoft Windows SharePoint Services 2.0:\ WSS2003-KB2760604-fullfile-ENU.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 | For Microsoft Windows SharePoint Services 2.0, see Microsoft Knowledge Base Article 2760604 |
| 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:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Windows 2000
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.
Supported Security Update Installation 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.- Click Start and then enter an update file name in Start Search.
- When the file appears under Programs, right-click on the file name and click Properties.
- Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- 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.
- 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.
Windows SharePoint Services 3.0 (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 Windows SharePoint Services 3.0 Service Pack 2 (32-bit version):\ sts2007-kb2596911-fullfile-x86-glb.exe /passive |
| For Microsoft Windows SharePoint Services 3.0 Service Pack 2 (64-bit version):\ sts2007-kb2596911-fullfile-x64-glb.exe /passive | |
| Installing without restarting | For Microsoft Windows SharePoint Services 3.0 Service Pack 2 (32-bit version):\ sts2007-kb2596911-fullfile-x86-glb.exe /norestart |
| For Microsoft Windows SharePoint Services 3.0 Service Pack 2 (64-bit version):\ sts2007-kb2596911-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 2596911 |
| 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:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Windows 2000
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.
Supported Security Update Installation 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.- Click Start and then enter an update file name in Start Search.
- When the file appears under Programs, right-click on the file name and click Properties.
- Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- 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.
- 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:\ wss2010-kb2553365-fullfile-x64-glb.exe /passive |
| Installing without restarting | For Microsoft SharePoint Foundation 2010:\ wss2010-kb2553365-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 2553365 |
| 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:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Windows 2000
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.
Supported Security Update Installation 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.- Click Start and then enter an update file name in Start Search.
- When the file appears under Programs, right-click on the file name and click Properties.
- Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- 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.
- 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.
Office Web Apps 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 Office Web Apps 2010:\ wac2010-kb2598239-fullfile-x64-glb.exe /passive |
| Installing without restarting | For Microsoft Office Web Apps 2010:\ wac2010-kb2598239-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 2598239 |
| 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:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Windows 2000
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.
Supported Security Update Installation 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.- Click Start and then enter an update file name in Start Search.
- When the file appears under Programs, right-click on the file name and click Properties.
- Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- 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.
- 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:
- Adi Cohen of IBM Security Systems - Application Security for reporting the HTML Sanitization Vulnerability (CVE-2012-1858)
- Yang Yang of Salesforce.com Product Security Team for reporting the SharePoint Script in Username Vulnerability (CVE-2012-1861)
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
How to obtain help and support for this security update
- Help installing updates: Support for Microsoft Update
- Security solutions for IT professionals: TechNet Security Troubleshooting and Support
- Help protect your computer that is running Windows from viruses and malware: Virus Solution and Security Center
- Local support according to your country: International Support
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 (July 10, 2012): Bulletin published.
- V1.1 (July 10, 2012): Downgraded the severity rating for the SharePoint Search Scope Vulnerability, CVE-2012-1860, from Important to Moderate for all affected software. This is an informational change only.
- V2.0 (December 11, 2012): Rereleased this bulletin to announce availability of an update for Microsoft Windows SharePoint Services 2.0. No other update packages are affected by this rerelease.
- V2.1 (December 12, 2012): Clarified that the update for Microsoft SharePoint Services 2.0 is available from the Microsoft Download Center only.
- V2.2 (January 15, 2014): Bulletin revised to announce a detection change in update 2596911. This is a detection change only. Customers who have already successfully updated their systems do not need to take any action.
Built at 2014-04-18T13:49:36Z-07:00