Security Bulletin
Microsoft Security Bulletin MS11-074 - Important
Vulnerabilities in Microsoft SharePoint Could Allow Elevation of Privilege (2451858)
Published: September 13, 2011 | Updated: October 11, 2011
Version: 1.3
General Information
Executive Summary
This security update resolves five privately reported vulnerabilities and one publicly disclosed vulnerability in Microsoft SharePoint and Windows SharePoint Services. The most severe vulnerabilities could allow elevation of privilege if a user clicked on a specially crafted URL or visited a specially crafted Web site. For the most severe vulnerabilities, Internet Explorer 8 and Internet Explorer 9 users browsing to a SharePoint site in the Internet Zone are at a reduced risk because, by default, the XSS Filter in Internet Explorer 8 and Internet Explorer 9 helps to block the attacks in the Internet Zone. The XSS Filter in Internet Explorer 8 and Internet Explorer 9, however, is not enabled by default in the Intranet Zone.
This security update is rated Important for Microsoft Office Groove 2007, Microsoft SharePoint Workspace 2010, Microsoft Office Forms Server 2007, Microsoft Office SharePoint Server 2007, Microsoft Office SharePoint Server 2010, Microsoft Office Groove Data Bridge Server 2007, Microsoft Office Groove Management Server 2007, Microsoft Groove Server 2010, Microsoft SharePoint Services 2.0, Microsoft SharePoint Services 3.0, Microsoft SharePoint Foundation 2010, Microsoft Office Web Apps 2010, and Microsoft Word Web App 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 Microsoft SharePoint validates and sanitizes user input, parses malicious XML and XSL files, and handles script contained inside of specific request parameters. 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 2451858 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
| Software | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by this Update |
|---|---|---|---|
| Microsoft Office Groove 2007 Service Pack 2\ (KB2552997) | Information Disclosure | Important | MS11-016 |
| Microsoft SharePoint Workspace 2010 and Microsoft SharePoint Workspace 2010 Service Pack 1 (32-bit editions)\ (KB2566445) | Information Disclosure | Important | None |
| Microsoft SharePoint Workspace 2010 and Microsoft SharePoint Workspace 2010 Service Pack 1 (64-bit editions)\ (KB2566445) | Information Disclosure | Important | None |
Microsoft Server Software
[1]For supported editions of Microsoft Office SharePoint Server 2007, in addition to security update packages for Microsoft Office SharePoint 2007 (KB2508964, KB2553001, KB2553002, and KB2553003), customers also need to install the security update for Microsoft Windows SharePoint Services 3.0 (KB2493987) to be protected from the vulnerabilities described in this bulletin.
Microsoft Office Web Apps
| Software | Component | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by this Update |
|---|---|---|---|---|
| Microsoft Office Web Apps 2010 and Microsoft Office Web Apps 2010 Service Pack 1\ (KB2566449) | Not applicable | Information Disclosure | Important | MS11-022 |
| Microsoft Office Web Apps 2010 and Microsoft Office Web Apps 2010 Service Pack 1 | Microsoft Word Web App 2010 and Microsoft Word Web App 2010 Service Pack 1\ (KB2566450) | Information Disclosure | Important | MS10-079 |
Non-Affected Software
| Office and Other Software |
|---|
| Microsoft Office SharePoint Portal Server 2003 Service Pack 3 |
Frequently Asked Questions (FAQ) Related to This Security Update
Why was this bulletin revised on October 11, 2011? Microsoft revised this bulletin to announce the following changes to detection logic:
- To address an installation issue, changed detection logic so that the update for Microsoft Office SharePoint Server 2010 and Microsoft Office SharePoint Server 2010 Service Pack 1 (pplwfe) (KB2560890) will no longer be offered to customers running Microsoft Office SharePoint Server 2010 on systems configured as part of a multiple-system SharePoint server farm. Instead, the update must be applied manually to servers in a Microsoft SharePoint Server 2010 farm. For more information about installing an update on a Microsoft SharePoint Server 2010 farm, see the TechNet article, Install a software update (SharePoint Server 2010). This is a change to detection logic only. There were no changes to the security update files. Customers of Microsoft Office SharePoint Server 2010 who have successfully applied the KB2560890 update do not need to take any further action.
- To address an offering issue, corrected detection logic so that the update for Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Foundation 2010 Service Pack 1 (KB2494001) properly replaces previous update packages. This is a change to detection logic only. There were no changes to the security update files. Customers of Microsoft SharePoint Foundation 2010 who have successfully applied the KB2494001 update do not need to take any further action.
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.
How is this security update related to MS11-050? The HTML Sanitization Vulnerability (CVE-2011-1252) is addressed by this update (MS11-074) and the Cumulative Security Update for Internet Explorer (MS11-050) update.
Two different updates are needed because the modifications that are required to address the issue are located in different Microsoft products. This update (MS11-074) addresses the vulnerability in affected Microsoft productivity software and MS11-050 addresses the vulnerability in Internet Explorer.
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 server-package updates available for Microsoft Office SharePoint Server 2007?
The updates required to address the vulnerabilities described in this bulletin are offered across different server-package updates as indicated in the Affected Software table due to the componentized servicing model for Microsoft SharePoint Server 2007. Coreserverx, oserver, sserverx, and dlc are the internal names of the SharePoint components in this servicing model.
Why are multiple server-package updates listed for Microsoft Office SharePoint Server 2010?
The updates required to address the vulnerabilities described in this bulletin are offered across different server-package updates as indicated in the Affected Software table due to the componentized servicing model for Microsoft SharePoint Server 2010. Mosrchwfe, osrv, pplwfe, ppsmawfe, dlc, ppsmamui, and wosrv are the internal names of the SharePoint components in this servicing model.
I use Microsoft Office SharePoint Server 2007 or Microsoft Office SharePoint Server 2010. Do I need to install all of the updates listed in the Affected Software table for the software? Yes. Customers should apply all server-package 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 2451858.
Do I need to install these security updates in a particular sequence? No. Multiple updates for one version of Microsoft Office SharePoint Server can be applied in any sequence.
Does this update contain any security-related changes to functionality? Yes. In addition to the changes that are listed in the Vulnerability Information section of this bulletin, this update includes a defense-in-depth update to help improve Microsoft SharePoint's handling of cross-application redirects.
What is defense-in-depth?
In information security, defense-in-depth refers to an approach in which multiple layers of defense are in place to help prevent attackers from compromising the security of a network or system.
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 Office Web Apps? Microsoft Office Web Apps is the online companion to Office Word, Excel, PowerPoint, and OneNote applications that enables users, regardless of their location, to access and edit documents. Users can view, share, and work on documents with others across personal computers, mobile phones, and the Web. Office Web Apps is available to business customers with Microsoft Office 2010 volume licensing and document management solutions based on Microsoft SharePoint 2010 products.
Where are updates for Microsoft Office Web Apps applied? Customers who have deployed Microsoft Office Web Apps in a SharePoint environment will need to apply the updates for Microsoft Office Web Apps on the servers on which those components are installed. For more information about deploying Microsoft Office Web Apps, see the Microsoft TechNet article, Understanding Office Web Apps.
Note The update for Microsoft Office Web Apps does not apply to the client workstations that use a Web browser to access Microsoft Office Web Apps.
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 KB2493987 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 Web site.
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 Lifecycle Supported Service Packs.
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 Web site, 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 September bulletin summary. For more information, see Microsoft Exploitability Index.
| Affected Software | XSS in SharePoint Calendar Vulnerability - CVE-2011-0653 | HTML Sanitization Vulnerability - CVE-2011-1252 | Editform Script Injection Vulnerability - CVE-2011-1890 | Contact Details Reflected XSS Vulnerability - CVE-2011-1891 | SharePoint Remote File Disclosure Vulnerability - CVE-2011-1892 | SharePoint XSS Vulnerability - CVE-2011-1893 | Aggregate Severity Rating |
|---|---|---|---|---|---|---|---|
| Microsoft Office Client Software | |||||||
| Microsoft Office Groove 2007 Service Pack 2 | Not applicable | Not applicable | Not applicable | Not applicable | Important Information Disclosure | Not applicable | Important |
| Microsoft SharePoint Workspace 2010 and Microsoft SharePoint Workspace 2010 Service Pack 1 (32-bit editions) | Not applicable | Not applicable | Not applicable | Not applicable | Important Information Disclosure | Not applicable | Important |
| Microsoft SharePoint Workspace 2010 and Microsoft SharePoint Workspace 2010 Service Pack 1 (64-bit editions) | Not applicable | Not applicable | Not applicable | Not applicable | Important Information Disclosure | Not applicable | Important |
| Microsoft Forms Server | |||||||
| Microsoft Office Forms Server 2007 Service Pack 2 (32-bit editions) | Not applicable | Not applicable | Not applicable | Not applicable | Important Information Disclosure | Not applicable | Important |
| Microsoft Office Forms Server 2007 Service Pack 2 (64-bit editions) | Not applicable | Not applicable | Not applicable | Not applicable | Important Information Disclosure | Not applicable | Important |
| Microsoft SharePoint Server | |||||||
| Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions) | Not applicable | Important Information Disclosure | Not applicable | Not applicable | Important Information Disclosure | Not applicable | Important |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions) | Not applicable | Important Information Disclosure | Not applicable | Not applicable | Important Information Disclosure | Not applicable | Important |
| Microsoft Office SharePoint Server 2010 | Important Elevation of Privilege | Important Information Disclosure | Important Elevation of Privilege | Not applicable | Important Information Disclosure | Important Elevation of Privilege | Important |
| Microsoft Office SharePoint Server 2010 Service Pack 1 | Important Elevation of Privilege | Important Information Disclosure | Not applicable | Not applicable | Important Information Disclosure | Not applicable | Important |
| Microsoft Groove Server | |||||||
| Microsoft Office Groove Data Bridge Server 2007 Service Pack 2 | Not applicable | Not applicable | Not applicable | Not applicable | Important Information Disclosure | Not applicable | Important |
| Microsoft Office Groove Management Server 2007 Service Pack 2 | Not applicable | Not applicable | Not applicable | Not applicable | Important Information Disclosure | Not applicable | Important |
| Microsoft Groove Server 2010 and Microsoft Groove Server 2010 Service Pack 1 | Not applicable | Important Information Disclosure | Not applicable | Not applicable | Important Information Disclosure | 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) | Not applicable | Important Information Disclosure | Not applicable | Important Elevation of Privilege | Important Information Disclosure | Important Elevation of Privilege | Important |
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (64-bit versions) | Not applicable | Important Information Disclosure | Not applicable | Important Elevation of Privilege | Important Information Disclosure | Important Elevation of Privilege | Important |
| SharePoint Foundation 2010 | Important Elevation of Privilege | Important Information Disclosure | Important Elevation of Privilege | Important Elevation of Privilege | Important Information Disclosure | Important Elevation of Privilege | Important |
| SharePoint Foundation 2010 Service Pack 1 | Not applicable | Important Information Disclosure | Not applicable | Important Elevation of Privilege | Not applicable | Not applicable | Important |
| Microsoft Office Web Apps | |||||||
| Microsoft Office Web Apps 2010 and Microsoft Office Web Apps 2010 Service Pack 1 | Not applicable | Not applicable | Not applicable | Not applicable | Important Information Disclosure | Not applicable | Important |
| Microsoft Office Web Apps 2010 and Microsoft Office Web Apps 2010 Service Pack 1 | Not applicable | Not applicable | Not applicable | Not applicable | Important Information Disclosure | Not applicable | Important |
XSS in SharePoint Calendar Vulnerability - CVE-2011-0653
A cross-site scripting vulnerability exists in Microsoft SharePoint 2010 that could result in information disclosure or elevation of privilege if a user clicks a specially crafted URL containing malicious JavaScript elements. Due to the vulnerability, when the malicious JavaScript is echoed back to the user's browser, the resulting page could allow an attacker to issue SharePoint commands in the context of the authenticated user on the targeted SharePoint site.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2011-0653.
Mitigating Factors for XSS in SharePoint Calendar Vulnerability - CVE-2011-0653
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 Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites 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 Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site and then convince them to click a specially crafted URL that is used to exploit the vulnerability.
- Internet Explorer 8 and Internet Explorer 9 users browsing to a SharePoint site in the Internet Zone are at a reduced risk because, by default, the XSS Filter in Internet Explorer 8 and Internet Explorer 9 prevents this attack in the Internet Zone. The XSS Filter in Internet Explorer 8 and Internet Explorer 9, however, is not enabled by default in the Intranet Zone.
- An attacker can cause arbitrary JavaScript to be run when the user clicks a specially crafted URL, but the attacker would not be able to steal the logged-on user's authentication credentials due to the way that SharePoint Server handles the HttpOnly authentication cookie.
- The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful, a user must click a specially crafted URL that is sent in an e-mail message.
Workarounds for XSS in SharePoint Calendar Vulnerability - CVE-2011-0653
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:
Enable Internet Explorer 8 and Internet Explorer 9 XSSfilter in the Local intranet security zone
You can help protect against exploitation of this vulnerability by changing your settings to enable the XSS filter in the Local intranet security zone. (XSS filter is enabled by default in the Internet security zone.) To do this, perform the following steps:
- In Internet Explorer 8 or Internet Explorer 9, click Internet Options on the Tools menu.
- Click the Security tab.
- Click Local intranet, and then click Custom Level.
- Under Settings, in the Scripting section, under Enable XSS filter, click Enable, and then click OK.
- Click OK two times to return to Internet Explorer.
Impact of workaround. Internal sites not previously flagged as being XSS risks could be flagged.
How to undo the workaround.
To undo this workaround, perform the following steps.
- In Internet Explorer 8 or Internet Explorer 9, click Internet Options on the Tools menu.
- Click the Security tab.
- Click Local intranet, and then click Custom Level.
- Under Settings, in the Scripting section, under Enable XSS filter, click Disable, and then click OK.
- Click OK two times to return to Internet Explorer.
FAQ for XSS in SharePoint Calendar Vulnerability - CVE-2011-0653
What is the scope of the vulnerability?
This is a cross-site scripting vulnerability that could result in elevation of privilege or information disclosure.
What causes the vulnerability?
The vulnerability is caused when Microsoft SharePoint does not properly handle malicious JavaScript elements contained within a specially crafted URL, allowing the script to be displayed back to the user's browser.
What is cross-site scripting?
Cross-site scripting (XSS) is a class of security vulnerability that can enable an attacker to inject script code into a user's session with a Web site. 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 Web sites that they frequent. An XSS attack does not modify Web site content. Instead, it inserts new, malicious script that can execute at the browser in the context that is associated with a trusted server.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could read content that the attacker is not authorized to read, use the victim's identity to take actions on the SharePoint site on behalf of the victim, such as change permissions and delete content, and inject malicious content in the browser of the victim.
How could an attacker exploit the vulnerability?
For this vulnerability to be exploited, a user must click a specially crafted URL that takes the user to a targeted SharePoint site that then displays the script back to the user's browser.
In an e-mail attack scenario, an attacker could exploit the vulnerability by sending an e-mail message containing the specially crafted URL to the user of the targeted SharePoint site and by convincing the user to click on the specially crafted URL.
In a Web-based attack scenario, an attacker would have to host a Web site that contains a specially crafted URL to the targeted SharePoint site that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the attacker's Web site, and then convince them to click on the specially crafted URL.
What systems are primarily at risk from the vulnerability?
Systems where users connect to a SharePoint server, such as workstations or terminal servers, are primarily at risk.
What is the Internet Explorer 8 and Internet Explorer 9 Cross-site Scripting (XSS) Filter?
Cross-site scripting attacks try to exploit vulnerabilities in the Web sites you use. In the case of this vulnerability, you might receive an e-mail message that contains a specially crafted Web site address that includes JavaScript elements. When you click on the URL, you are directed to a legitimate SharePoint site where the attacker-provided script is run. Cross-site scripting attacks have emerged as a leading online threat, so Internet Explorer 8 and Internet Explorer 9 include a cross-site scripting filter that can detect these types of attacks and disable the harmful scripts. By default, the cross-site scripting filter is turned on in Internet Explorer 8 for the Internet Zone.
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.
HTML Sanitization Vulnerability - CVE-2011-1252
An information disclosure vulnerability exists in the way that the SafeHTML function sanitizes HTML. 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-2011-1252.
Mitigating Factors for HTML Sanitization Vulnerability - CVE-2011-1252
Microsoft has not identified any mitigating factors for this vulnerability
Workarounds for HTML Sanitization Vulnerability - CVE-2011-1252
Microsoft has not identified any workarounds for this vulnerability.
FAQ for HTML Sanitization Vulnerability - CVE-2011-1252
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 the SafeHTML function sanitizes HTML.
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 Web site. 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 Web sites that they frequent. An XSS attack does not modify Web site 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 that uses SafeHTML to sanitize HTML. 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 using SafeHTML. 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 the targeted site using SafeHTML, any Web page on that site that contains the specially crafted script is a potential vector for persistent cross-site scripting attacks. When a user visits a Web page 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 server that uses SafeHTML to sanitize HTML content, 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 SafeHTML sanitizes HTML content.
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-2011-1252.
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 and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
Editform Script Injection Vulnerability - CVE-2011-1890
A cross-site scripting, information disclosure, and elevation of privilege vulnerability exists in Microsoft SharePoint 2010 and Microsoft Foundation 2010 if a user visits a specially crafted Web site. Due to the vulnerability, malicious JavaScript can be injected into a post made to a targeted SharePoint site. The injected script could allow an attacker to issue SharePoint commands in the context of the authenticated user on the targeted SharePoint site.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2011-1890.
Mitigating Factors for Editform Script Injection Vulnerability - CVE-2011-1890
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 Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites 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 Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.
- Internet Explorer 8 and Internet Explorer 9 users browsing to a SharePoint site in the Internet Zone are at a reduced risk because, by default, the XSS Filter in Internet Explorer 8 prevents this attack in the Internet Zone. The Internet Explorer 8 and Internet Explorer 9 XSS Filter, however, is not enabled by default in the Intranet Zone.
- An attacker can cause arbitrary JavaScript to be run by the user who is visiting a specially crafted Web site, but the attacker would not be able to steal the logged-on user's authentication credentials due to the way that SharePoint Server handles the HttpOnly authentication cookie.
- The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful, a user must click on a link to a specially crafted Web site that is sent in an e-mail message.
Workarounds for Editform Script Injection Vulnerability - CVE-2011-1890
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:
Enable Internet Explorer 8 and Internet Explorer 9 XSS filter in the Local intranet security zone
You can help protect against exploitation of this vulnerability by changing your settings to enable the XSS filter in the Local intranet security zone (XSS filter is enabled by default in the Internet security zone). To do this, perform the following steps:
- In Internet Explorer 8 or Internet Explorer 9, click Internet Options on the Tools menu.
- Click the Security tab.
- Click Local intranet, and then click Custom Level.
- Under Settings, in the Scripting section, under Enable XSS filter, click Enable, and then click OK.
- Click OK two times to return to Internet Explorer.
Impact of workaround. Internal sites not previously flagged as being XSS risks could be flagged.
How to undo the workaround.
To undo this workaround, perform the following steps.
- In Internet Explorer 8 or Internet Explorer 9, click Internet Options on the Tools menu.
- Click the Security tab.
- Click Local intranet, and then click Custom Level.
- Under Settings, in the Scripting section, under Enable XSS filter, click Disable, and then click OK.
- Click OK two times to return to Internet Explorer.
FAQ for Editform Script Injection Vulnerability - CVE-2011-1890
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?
This vulnerability is caused when Microsoft SharePoint does not properly validate user input posted to the EditForm.aspx Web page.
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 Web site. 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 Web sites that they frequent. An XSS attack does not modify Web site 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 use script to issue SharePoint commands in the context of the authenticated user on the targeted SharePoint site. .
How could an attacker exploit the vulnerability?
In an e-mail attack scenario, an attacker could exploit the vulnerability by sending an e-mail message containing a link to a specially crafted Web site to the user and by convincing the user to click on the link.
In a Web-based attack scenario, an attacker would have to host a Web site that contains a specially crafted Web page that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the attacker's Web site.
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 modifying the way that Microsoft SharePoint validates user input to prevent malicious JavaScript from being injected and rendered in the user's browser.
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.
Contact Details Reflected XSS Vulnerability - CVE-2011-1891
A cross-site scripting vulnerability in Microsoft SharePoint could allow an attacker to gain control over valid user accounts, perform operations on the user's behalf, redirect the user to malicious sites, or steal user credentials.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2011-1891.
Mitigating Factors for Contact Details Reflected XSS Vulnerability - CVE-2011-1891
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 Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites 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 Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site and then convince them to click a specially crafted URL that is used to exploit the vulnerability.
- Internet Explorer 8 and Internet Explorer 9 users browsing to a SharePoint site in the Internet Zone are at a reduced risk because, by default, the XSS Filter in Internet Explorer 8 prevents this attack in the Internet Zone. The Internet Explorer 8 and Internet Explorer 9 XSS Filter, however, is not enabled by default in the Intranet Zone.
- An attacker can cause arbitrary JavaScript to be run by the user clicking the specially crafted URL, but the attacker would not be able to steal the logged-on user's authentication credentials due to the way that SharePoint Server handles the HttpOnly authentication cookie.
- The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful, a user must click a specially crafted URL that is sent in an e-mail message.
Workarounds for Contact Details Reflected XSS Vulnerability - CVE-2011-1891
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:
Enable Internet Explorer 8 and Internet Explorer 9 XSS filter in the Local intranet security zone
You can help protect against exploitation of this vulnerability by changing your settings to enable the XSS filter in the Local intranet security zone (XSS filter is enabled by default in the Internet security zone). To do this, perform the following steps:
- In Internet Explorer 8 or Internet Explorer 9, click Internet Options on the Tools menu.
- Click the Security tab.
- Click Local intranet, and then click Custom Level.
- Under Settings, in the Scripting section, under Enable XSS filter, click Enable, and then click OK.
- Click OK two times to return to Internet Explorer.
Impact of workaround. Internal sites not previously flagged as being XSS risks could be flagged.
How to undo the workaround.
To undo this workaround, perform the following steps.
- In Internet Explorer 8 or Internet Explorer 9, click Internet Options on the Tools menu.
- Click the Security tab.
- Click Local intranet, and then click Custom Level.
- Under Settings, in the Scripting section, under Enable XSS filter, click Disable, and then click OK.
- Click OK two times to return to Internet Explorer.
FAQ for Contact Details Reflected XSS Vulnerability - CVE-2011-1891
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?
This vulnerability is caused by improper input sanitization on specific SharePoint parameters.
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 Web site. 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 Web sites that they frequent. An XSS attack does not modify Web site 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?
To trigger the vulnerability, the user is tricked into visiting a site that will submit a specially crafted form containing malicious script to the vulnerable SharePoint site.
An attacker who successfully exploited this vulnerability could inject script to phish for user credentials or take actions on behalf of the user, such as change permissions and modify or delete content, on a targeted SharePoint site.
How could an attacker exploit the vulnerability?
An attacker could exploit this vulnerability by convincing a user to submit a specially crafted form that sends malicious script to an affected SharePoint 2007 instance.
What systems are primarily at risk from the vulnerability?
Client systems that connect to SharePoint 2007 and SharePoint 2007 servers are at risk from the vulnerability.
What is the Internet Explorer 8 and Internet Explorer 9 Cross-site Scripting (XSS) Filter?
Cross-site scripting attacks try to exploit vulnerabilities in the Web sites you use. In the case of this vulnerability, you might receive an e-mail message that contains a specially crafted Web site address that includes JavaScript elements. When you click on the URL, you are directed to a legitimate SharePoint site where the attacker-provided script is run. Cross-site scripting attacks have emerged as a leading online threat, so Internet Explorer 8 and Internet Explorer 9 include a cross-site scripting filter that can detect these types of attacks and disable the harmful scripts. By default, the cross-site scripting filter is turned on in Internet Explorer 8 and Internet Explorer 9 for the Internet Zone.
What does the update do?
The update addresses the vulnerability by modifying the way that SharePoint Server handles script requests.
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 Remote File Disclosure Vulnerability - CVE-2011-1892
A file disclosure vulnerability exists in Microsoft Office SharePoint that could allow a malicious authenticated user to use a specially crafted XML file to gain read-only access to a local file on the SharePoint server under the security context of the account running SharePoint.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2011-1892.
Mitigating Factors for SharePoint Remote File Disclosure Vulnerability - CVE-2011-1892
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:
- The attacker cannot run arbitrary code on the target SharePoint server. This is an information disclosure vulnerability only.
- The attacker must be authenticated on the SharePoint site in order to exploit this vulnerability.
Workarounds for SharePoint Remote File Disclosure Vulnerability - CVE-2011-1892
Microsoft has not identified any workarounds for this vulnerability.
FAQ for SharePoint Remote File Disclosure Vulnerability - CVE-2011-1892
What is the scope of the vulnerability?
This is an information disclosure vulnerability.
What causes the vulnerability?
This vulnerability is caused when SharePoint does not properly restrict the use of specially crafted XML classes and external entities in Web Parts.
What might an attacker use the vulnerability to do?
An attacker could use this vulnerability to obtain read access to files on the file system of the local SharePoint server with the access permissions of the IIS AppPool account.
How could an attacker exploit the vulnerability?
An authenticated user on the SharePoint site could use a specially crafted XML and XSL file to create a malicious XML Web Part used to obtain file access on the targeted SharePoint server.
What systems are primarily at risk from the vulnerability?
Servers running the affected Microsoft SharePoint software are primarily at risk.
What does the update do?
The update addresses the vulnerability by modifying the way that Microsoft SharePoint parses malicious XML and XSL files, thus restricting the ability to disclose files on the file system of the local SharePoint server.
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 XSS Vulnerability - CVE-2011-1893
A cross-site scripting, information disclosure, and elevation of privilege vulnerability exists in Microsoft SharePoint Server and Windows SharePoint Services where JavaScript that is encoded in a specially crafted URL can be reflected back to the user in the resulting page, allowing an attacker to issue SharePoint commands in the context of the authenticated user on a targeted SharePoint site.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2011-1893.
Mitigating Factors for SharePoint XSS Vulnerability - CVE-2011-1893
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 Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites 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 Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.
- Internet Explorer 8 and Internet Explorer 9 users browsing to a SharePoint site in the Internet Zone are at a reduced risk because, by default, the XSS Filter in Internet Explorer 8 prevents this attack in the Internet Zone. The Internet Explorer 8 and Internet Explorer 9 XSS Filter, however, is not enabled by default in the Intranet Zone.
- An attacker can cause arbitrary JavaScript to be run by the user who visiting a specially crafted Web site, but the attacker would not be able to steal the logged-on user's authentication credentials due to the way that SharePoint Server handles the HttpOnly authentication cookie.
- The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful, a user must click on a link to a specially crafted Web site that is sent in an e-mail message.
Workarounds for SharePoint XSS Vulnerability - CVE-2011-1893
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:
Enable Internet Explorer 8 and Internet Explorer 9 XSS filter in the Local intranet security zone
You can help protect against exploitation of this vulnerability by changing your settings to enable the XSS filter in the Local intranet security zone (XSS filter is enabled by default in the Internet security zone). To do this, perform the following steps:
- In Internet Explorer 8 or Internet Explorer 9, click Internet Options on the Tools menu.
- Click the Security tab.
- Click Local intranet, and then click Custom Level.
- Under Settings, in the Scripting section, under Enable XSS filter, click Enable, and then click OK.
- Click OK two times to return to Internet Explorer.
Impact of workaround. Internal sites not previously flagged as being XSS risks could be flagged.
How to undo the workaround.
To undo this workaround, perform the following steps.
- In Internet Explorer 8 or Internet Explorer 9, click Internet Options on the Tools menu.
- Click the Security tab.
- Click Local intranet, and then click Custom Level.
- Under Settings, in the Scripting section, under Enable XSS filter, click Disable, and then click OK.
- Click OK two times to return to Internet Explorer.
FAQ for SharePoint XSS Vulnerability - CVE-2011-1893
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?
This vulnerability is caused by input sanitation which will allow for a malicious URL that contains JavaScript elements to be displayed back to the user.
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 Web site. 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 Web sites that they frequent. An XSS attack does not modify Web site 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 reflect malicious JavaScript back to the browser of the user, which could allow the attacker to modify the page content, conduct phishing, and perform actions on behalf of the user.
How could an attacker exploit the vulnerability?
For this vulnerability to be exploited, a user must click a specially crafted URL.
In an e-mail attack scenario, an attacker could exploit the vulnerability by sending an e-mail message containing the specially crafted URL to the user of the targeted SharePoint site and by convincing the user to click on the specially crafted URL.
In a Web-based attack scenario, an attacker would have to host a Web site that contains a specially crafted URL to the targeted SharePoint site that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the attacker's Web site, and then convince them to click on the specially crafted URL.
What systems are primarily at risk from the vulnerability?
Client systems that use Microsoft Windows SharePoint Services or connect to a Microsoft SharePoint Server, 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 Microsoft SharePoint validates and sanitizes user input to block the reflective XSS attack vector.
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 Web site provides additional information about security in Microsoft products.
Security updates are available from Microsoft Update and Windows Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."
For customers of Microsoft Office for Mac, Microsoft AutoUpdate for Mac can help keep your Microsoft software up to date. For more information about using Microsoft AutoUpdate for Mac, see Check for software updates automatically.
Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, "MS07-036"), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.
Detection and Deployment Guidance
Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see Microsoft Knowledge Base Article 961747.
Microsoft Baseline Security Analyzer
Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.
The following table provides the MBSA detection summary for this security update.
| Software | MBSA |
|---|---|
| Microsoft Office Groove 2007 Service Pack 2 | Yes |
| Microsoft SharePoint Workspace 2010 and Microsoft SharePoint Workspace 2010 Service Pack 1 | Yes |
| Microsoft Office Forms Server 2007 Service Pack 2 (32-bit editions) | Yes |
| Microsoft Office Forms Server 2007 Service Pack 2 (64-bit editions) | Yes |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions) | Yes |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions) | Yes |
| Microsoft Office SharePoint Server 2010 and Microsoft Office SharePoint Server 2010 Service Pack 1 | Yes |
| Microsoft Office Groove Data Bridge Server 2007 Service Pack 2 | Yes |
| Microsoft Office Groove Management Server 2007 Service Pack 2 | Yes |
| Microsoft Groove Server 2010 and Microsoft Groove Server 2010 Service Pack 1 | Yes |
| Microsoft Windows SharePoint Services 2.0 | Yes |
| 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 and SharePoint Foundation 2010 Service Pack 1 | Yes |
| Microsoft Office Web Apps 2010 and Microsoft Office Web Apps 2010 Service Pack 1 | Yes |
| Microsoft Word Web App 2010 and Microsoft Word Web App 2010 Service Pack 1 | Yes |
Note For customers using legacy software not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, please visit Microsoft Baseline Security Analyzer and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools.
Windows Server Update Services
Windows Server Update Services (WSUS) enables information technology administrators to deploy the latest Microsoft product updates to computers that are running the Windows operating system. For more information about how to deploy security updates using Windows Server Update Services, see the TechNet article, Windows Server Update Services.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
| Software | SMS 2003 with ITMU | Configuration Manager 2007 |
|---|---|---|
| Microsoft Office Groove 2007 Service Pack 2 | Yes | Yes |
| Microsoft SharePoint Workspace 2010 and Microsoft SharePoint Workspace 2010 Service Pack 1 | Yes | Yes |
| Microsoft Office Forms Server 2007 Service Pack 2 (32-bit editions) | Yes | Yes |
| Microsoft Office Forms Server 2007 Service Pack 2 (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 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 2010 and Microsoft Office 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 Office Groove Data Bridge Server 2007 Service Pack 2 | Yes | Yes |
| Microsoft Office Groove Management Server 2007 Service Pack 2 | Yes | Yes |
| Microsoft Groove Server 2010 and Microsoft Groove Server 2010 Service Pack 1 | Yes | Yes |
| Microsoft Windows SharePoint Services 2.0 | Yes | Yes |
| 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 and SharePoint Foundation 2010 Service Pack 1 | Yes | Yes |
| Microsoft Office Web Apps 2010 and Microsoft Office Web Apps 2010 Service Pack 1 | Yes | Yes |
| Microsoft Word Web App 2010 and Microsoft Word Web App 2010 Service Pack 1 | Yes | Yes |
Note Microsoft discontinued support for SMS 2.0 on April 12, 2011. For SMS 2003, Microsoft also discontinued support for the Security Update Inventory Tool (SUIT) on April 12, 2011. Customers are encouraged to upgrade to System Center Configuration Manager 2007. For customers remaining on SMS 2003 Service Pack 3, the Inventory Tool for Microsoft Updates (ITMU) is also an option.
For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.
System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007.
For more information about SMS, visit the SMS Web site.
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 Office SharePoint Server 2010 The detection table described above is based on single-server Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2010 deployments. The detection tools do not detect the applicability of the update on systems configured as part of a multiple-system SharePoint server farms.
Note If you have used an Administrative Installation Point (AIP) for deploying Office XP or Office 2003, you may not be able to deploy the update using SMS if you have updated the AIP from the original baseline. For more information, see the Office Administrative Installation Point heading in this section.
Office Administrative Installation Point
If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your system.
- 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 Web site.
Update Compatibility Evaluator and Application Compatibility Toolkit
Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit.
The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Microsoft Office Groove 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 Office Groove 2007 Service Pack 2:\ groove2007-kb2552997-fullfile-x86-glb.exe /passive |
| Installing without restarting | For Office Groove 2007 Service Pack 2:\ groove2007-kb2552997-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 tool in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 2552997 |
| 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 be installed on the system.
To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft Web sites:
- 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 tool 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 tool 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 of the 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.
Microsoft SharePoint Workspace 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 SharePoint Workspace 2010 and SharePoint Workspace 2010 Service Pack 1 (32-bit editions):\ workspaces2010-kb2566445-fullfile-x86-glb.exe /passive |
| For SharePoint Workspace 2010 and SharePoint Workspace 2010 Service Pack 1 (64-bit editions):\ workspaces2010-kb2566445-fullfile-x64-glb.exe /passive | |
| Installing without restarting | For SharePoint Workspace 2010 and SharePoint Workspace 2010 Service Pack 1 (32-bit editions):\ workspaces2010-kb2566445-fullfile-x86-glb.exe /norestart |
| For SharePoint Workspace 2010 and SharePoint Workspace 2010 Service Pack 1 (64-bit editions):\ workspaces2010-kb2566445-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 tool in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 2566445 |
| 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 be installed on the system.
To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft Web sites:
- 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 tool 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 tool 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 of the 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) and Forms 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 Service Pack 2 (32-bit editions):\ Office2007-kb2508964-fullfile-x86-glb.exe /passive\ Office2007-kb2553001-fullfile-x86-glb.exe /passive\ Office2007-kb2553002-fullfile-x86-glb.exe /passive\ Office2007-kb2553003-fullfile-x86-glb.exe /passive |
| For Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions):\ Office2007-kb2508964-fullfile-x64-glb.exe /passive\ Office2007-kb2553001-fullfile-x64-glb.exe /passive\ Office2007-kb2553002-fullfile-x64-glb.exe /passive\ Office2007-kb2553003-fullfile-x64-glb.exe /passive | |
| For Microsoft Office Forms Server 2007 Service Pack 2 (32-bit editions):\ formsserver2007-kb2553005-fullfile-x86-glb.exe /passive | |
| For Microsoft Office Forms Server 2007 Service Pack 2 (64-bit editions):\ formsserver2007-kb2553005-fullfile-x64-glb.exe /passive | |
| Installing without restarting | For Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions):\ Office2007-kb2508964-fullfile-x86-glb.exe /norestart\ Office2007-kb2553002-fullfile-x86-glb.exe /norestart\ Office2007-kb2553003-fullfile-x86-glb.exe /norestart |
| For Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions):\ Office2007-kb2508964-fullfile-x64-glb.exe /norestart\ Office2007-kb2553002-fullfile-x64-glb.exe /norestart\ Office2007-kb2553003-fullfile-x64-glb.exe /norestart | |
| For Microsoft Office Forms Server 2007 Service Pack 2 (32-bit editions):\ formsserver2007-kb2553005-fullfile-x86-glb.exe /norestart | |
| For Microsoft Office Forms Server 2007 Service Pack 2 (64-bit editions):\ formsserver2007-kb2553005-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 | For Microsoft Office SharePoint Server 2007, see Microsoft Knowledge Base Article 2508964, Microsoft Knowledge Base Article 2553002, and Microsoft Knowledge Base Article 2345212 |
| For Microsoft Office Forms Server 2007, see Microsoft Knowledge Base Article 2553005 | |
| 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 be installed on the system.
To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft Web sites:
- 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 and Microsoft Office SharePoint Server 2010 Service Pack 1:\ officeserver2010-kb2494022-fullfile-x64-glb.exe /passive\ officeserver2010-kb2560885-fullfile-x64-glb.exe /passive\ officeserver2010-kb2560890-fullfile-x64-glb.exe /passive\ officeserver2010-kb2566456-fullfile-x64-glb.exe /passive\ Officeserver2010-kb2566954-fullfile-x64-glb.exe /passive\ officeserver2010-kb2566958-fullfile-x64-glb.exe /passive\ officeserver2010-kb2566960-fullfile-x64-glb.exe /passive |
| Installing without restarting | For Microsoft Office SharePoint Server 2010 and Microsoft Office SharePoint Server 2010 Service Pack 1:\ officeserver2010-kb2494022-fullfile-x64-glb.exe /norestart\ officeserver2010-kb2560885-fullfile-x64-glb.exe /norestart\ officeserver2010-kb2560890-fullfile-x64-glb.exe /norestart\ officeserver2010-kb2566456-fullfile-x64-glb.exe /norestart\ Officeserver2010-kb2566954-fullfile-x64-glb.exe /norestart\ officeserver2010-kb2566958-fullfile-x64-glb.exe /norestart\ officeserver2010-kb2566960-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 2494022,\ Microsoft Knowledge Base Article 2560885,\ Microsoft Knowledge Base Article 2560890,\ Microsoft Knowledge Base Article 2566456,\ Microsoft Knowledge Base Article 2566954,\ Microsoft Knowledge Base Article 2566958, and\ Microsoft Knowledge Base Article 2566960 |
| 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 be installed on the system.
To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft Web sites:
- 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 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 Groove Data Bridge Server 2007 Service Pack 2:\ groovedatabridge2007-kb2552999-fullfile-x64-glb.exe /passive |
| For Microsoft Office Groove Management Server 2007 Service Pack 2:\ groovemanagementserver2007-kb2552998-fullfile-x64-glb.exe /passive | |
| Installing without restarting | For Microsoft Office Groove Data Bridge Server 2007 Service Pack 2:\ groovedatabridge2007-kb2552999-fullfile-x64-glb.exe /norestart |
| For Microsoft Office Groove Management Server 2007 Service Pack 2:\ groovemanagementserver2007-kb2552998-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 | For Microsoft Office Groove Data Bridge Server 2007, see Microsoft Knowledge Base Article 2552999 |
| For Microsoft Office Groove Management Server 2007, see Microsoft Knowledge Base Article 2552998 | |
| 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 be installed on the system.
To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft Web sites:
- 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.
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 and Microsoft Groove Server 2010 Service Pack 1:\ grooveserver2010-kb2508965-fullfile-x64-glb.exe /passive |
| Installing without restarting | For Microsoft Groove Server 2010 and Microsoft Groove Server 2010 Service Pack 1:\ grooveserver2010-kb2508965-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 2508965 |
| 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 be installed on the system.
To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft Web sites:
- 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 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-kb2494007-fullfile-ENU.exe /passive |
| Installing without restarting | For Microsoft Windows SharePoint Services 2.0:\ WSS2003-kb2494007-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 2494007 |
| 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 be installed on the system.
To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft Web sites:
- 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 versions):\ wss-kb2493987-fullfile-x86-glb.exe /passive |
| For Microsoft Windows SharePoint Services 3.0 Service Pack 2 (64-bit versions):\ wss-kb2493987-fullfile-x64-glb.exe /passive | |
| Installing without restarting | For Microsoft Windows SharePoint Services 3.0 Service Pack 2 (32-bit versions):\ wss-kb2493987-fullfile-x86-glb.exe /norestart |
| For Microsoft Windows SharePoint Services 3.0 Service Pack 2 (64-bit versions):\ wss-kb2493987-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 2493987 |
| 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 be installed on the system.
To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft Web sites:
- 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 and Microsoft SharePoint Foundation 2010 Service Pack 1:\ sharepointfoundation2010-kb2494001-fullfile-x64-glb.exe /passive |
| Installing without restarting | For Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Foundation 2010 Service Pack 1:\ sharepointfoundation2010-kb2494001-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 2494001 |
| 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 be installed on the system.
To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft Web sites:
- 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 and Word Web App (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 Office Web Apps 2010 and Office Web Apps 2010 Service Pack 1:\ webapps-kb2566449-fullfile-x64-glb.exe /passive |
| For Word Web App 2010 and Word Web App 2010 Service Pack 1:\ wordwebapp-kb2566450-fullfile-x64-glb.exe /passive | |
| Installing without restarting | For Office Web Apps 2010 and Office Web Apps 2010 Service Pack 1:\ webapps-kb2566449-fullfile-x64-glb.exe /norestart |
| For Word Web App 2010 and Word Web App 2010 Service Pack 1:\ wordwebapp-kb2566450-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 | For Office Web Apps 2010 and Office Web Apps 2010 Service Pack 1, see Microsoft Knowledge Base Article 2566449 |
| For Word Web App 2010 and Word Web App 2010 Service Pack 1, see Microsoft Knowledge Base Article 2566450 | |
| 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 be installed on the system.
To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft Web sites:
- 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.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Andrew Connell of Critical Path Training, LLC for reporting the XSS in SharePoint Calendar Vulnerability (CVE-2011-0653)
- David Feldman of Raytheon for reporting the XSS in SharePoint Calendar Vulnerability (CVE-2011-0653)
- Adi Cohen of IBM Rational Application Security for reporting HTML Sanitization Vulnerability (CVE-2011-1252)
- Trend Micro for working with us on HTML Sanitization Vulnerability (CVE-2011-1252)
- Pedro Jimenez of ITT for reporting the Editform Script Injection Vulnerability (CVE-2011-1890)
- Seeker automatic application security testing solution for reporting the Contact Details Reflected XSS Vulnerability (CVE-2011-1891)
- Nicolas Grégoire of Agarri for reporting the SharePoint Remote File Disclosure Vulnerability (CVE-2011-1892)
- Jim LaValley of LaValley Consulting, LLC for reporting the SharePoint XSS Vulnerability (CVE-2011-1893)
- Irene Abezgauz of Seeker for working with us on a defense-in-depth update to help improve the handling of cross-application redirects in Microsoft SharePoint
Microsoft Active Protections Program (MAPP)
To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.
Support
- Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support.
- International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.
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 (September 13, 2011): Bulletin published.
- V1.1 (September 13, 2011): Added update link and package information for the Microsoft Office SharePoint Server 2010 and Microsoft Office SharePoint Server 2010 Service Pack 1 (pplwfe) (KB2560890) update. This is an informational change only. There were no changes to the security update files or detection logic.
- V1.2 (September 21, 2011): Removed erroneous reference to Microsoft Knowledge Base Article 2553001 in the deployment reference table for Microsoft Groove Server 2007. This is an informational change only. There were no changes to the security update files or detection logic.
- V1.3 (October 11, 2011): Announced changes to detection logic for some affected configurations. There were no changes to the security update files. See the Update FAQ for details.
Built at 2014-04-18T13:49:36Z-07:00