Security Bulletin
Microsoft Security Bulletin MS12-066 - Important
Vulnerability in HTML Sanitization Component Could Allow Elevation of Privilege (2741517)
Published: October 09, 2012 | Updated: January 15, 2014
Version: 1.4
General Information
Executive Summary
This security update resolves a publicly disclosed vulnerability in Microsoft Office, Microsoft Communications Platforms, Microsoft Server software, and Microsoft Office Web Apps. The vulnerability could allow elevation of privilege if an attacker sends specially crafted content to a user.
This security update is rated Important for supported editions of Microsoft InfoPath 2007, Microsoft InfoPath 2010, Microsoft Communicator 2007 R2, Microsoft Lync 2010, Microsoft Lync 2010 Attendee, Microsoft SharePoint Server 2007, Microsoft SharePoint Server 2010, Microsoft Groove Server 2010, Microsoft SharePoint Windows Services 3.0, Microsoft SharePoint Foundation 2010, and Microsoft Office Web Apps 2010. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerability by modifying the way that HTML strings are sanitized. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection 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 2741517 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, see Microsoft Support Lifecycle.
Affected Software
Microsoft Office
| Software | Maximum Security Impact | Aggregate Severity Rating | Updates Replaced |
|---|---|---|---|
| Microsoft InfoPath 2007 Service Pack 2\ (KB2687439)\ \ Microsoft InfoPath 2007 Service Pack 2\ (KB2687440) | Elevation of Privilege | Important | KB2596666 in MS12-050 replaced by KB2687439\ \ KB2596786 in MS12-050 replaced by KB2687440 |
| Microsoft InfoPath 2007 Service Pack 3\ (KB2687439)\ \ Microsoft InfoPath 2007 Service Pack 3\ (KB2687440) | Elevation of Privilege | Important | KB2596666 in MS12-050 replaced by KB2687439\ \ KB2596786 in MS12-050 replaced by KB2687440 |
| Microsoft InfoPath 2010 Service Pack 1 (32-bit editions)\ (KB2687436)\ \ Microsoft InfoPath 2010 Service Pack 1 (32-bit editions)\ (KB2687417) | Elevation of Privilege | Important | KB2553431 in MS12-050 replaced by KB2687436\ \ KB2553322 in MS12-050 replaced by KB2687417 |
| Microsoft InfoPath 2010 Service Pack 1 (64-bit editions)\ (KB2687436)\ \ Microsoft InfoPath 2010 Service Pack 1 (64-bit editions)\ (KB2687417) | Elevation of Privilege | Important | KB2553431 in MS12-050 replaced by KB2687436\ \ KB2553322 in MS12-050 replaced by KB2687417 |
Microsoft Communications Platforms and Software
| Software | Maximum Security Impact | Aggregate Severity Rating | Updates Replaced |
|---|---|---|---|
| Microsoft Communicator 2007 R2\ (KB2726391) | Information Disclosure | Important | KB2708980 in MS12-039 replaced by KB2726391 |
| Microsoft Lync 2010 (32-bit)\ (KB2726382) | Information Disclosure | Important | KB2693282 in MS12-039 replaced by KB2726382 |
| Microsoft Lync 2010 (64-bit)\ (KB2726382) | Information Disclosure | Important | KB2693282 in MS12-039 replaced by KB2726382 |
| Microsoft Lync 2010 Attendee\ (admin level install)\ (KB2726388)\ \ Microsoft Lync 2010 Attendee[1]\ (user level install)\ (KB2726384) | Information Disclosure | Important | KB2696031 in MS12-039 replaced by KB2726388\ \ KB2693283 in MS12-039 replaced by KB2726384 |
[1]This update is available from the Microsoft Download Center only.
Microsoft Server Software
| Software | Update Package | Maximum Security Impact | Aggregate Severity Rating | Updates Replaced |
|---|---|---|---|---|
| Microsoft SharePoint Server | ||||
| Microsoft SharePoint Server 2007 Service Pack 2 (32-bit editions) | Microsoft SharePoint Server 2007 Service Pack 2 (coreserver) (32-bit editions)[1](KB2687405) | Elevation of Privilege | Important | KB2596663 in MS12-050 replaced by KB2687405 |
| Microsoft SharePoint Server 2007 Service Pack 3 (32-bit editions) | Microsoft SharePoint Server 2007 Service Pack 3 (coreserver) (32-bit editions)[1](KB2687405) | Elevation of Privilege | Important | KB2596663 in MS12-050 replaced by KB2687405 |
| Microsoft SharePoint Server 2007 Service Pack 2 (64-bit editions) | Microsoft SharePoint Server 2007 Service Pack 2 (coreserver) (64-bit editions)[1](KB2687405) | Elevation of Privilege | Important | KB2596663 in MS12-050 replaced by KB2687405 |
| Microsoft SharePoint Server 2007 Service Pack 3 (64-bit editions) | Microsoft SharePoint Server 2007 Service Pack 3 (coreserver) (64-bit editions)[1](KB2687405) | Elevation of Privilege | Important | KB2596663 in MS12-050 replaced by KB2687405 |
| Microsoft SharePoint Server 2010 Service Pack 1 | Microsoft SharePoint Server 2010 Service Pack 1 (wosrv) (KB2687435) Microsoft SharePoint Server 2010 Service Pack 1 (coreserver) (KB2589280) | Elevation of Privilege | Important | KB2553424 in MS12-050 replaced by KB2687435 KB2553194 in MS12-050 replaced by KB2589280 |
| Microsoft Groove Server | ||||
| Microsoft Groove Server 2010 Service Pack 1 (KB2687402) | Not applicable | Elevation of Privilege | Important | KB2589325 in MS12-050 replaced by KB2687402 |
| Windows SharePoint Services and Microsoft SharePoint Foundation | ||||
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (32-bit version) (KB2687356) | Not applicable | Elevation of Privilege | Important | KB2596911 in MS12-050 replaced by KB2687356 |
| Microsoft Windows SharePoint Services 3.0 Service Pack 3 (32-bit version) (KB2687356) | Not applicable | Elevation of Privilege | Important | None |
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (64-bit version) (KB2687356) | Not applicable | Elevation of Privilege | Important | KB2596911 in MS12-050 replaced by KB2687356 |
| Microsoft Windows SharePoint Services 3.0 Service Pack 3 (64-bit version) (KB2687356) | Not applicable | Elevation of Privilege | Important | None |
| Microsoft SharePoint Foundation 2010 Service Pack 1 (KB2687434) | Not applicable | Elevation of Privilege | Important | KB2553365 in MS12-050 replaced by KB2687434 |
[1]For supported editions of Microsoft SharePoint Server 2007, in addition to the security update package for Microsoft SharePoint 2007 (KB2687405), customers also need to install the security update for Microsoft Windows SharePoint Services 3.0 (KB2687356) to be protected from the vulnerability described in this bulletin.
Microsoft Office Web Apps
| Software | Component | Maximum Security Impact | Aggregate Severity Rating | Updates Replaced |
|---|---|---|---|---|
| Microsoft Office Web Apps 2010 Service Pack 1\ (KB2687401) | Not applicable | Elevation of Privilege | Important | KB2598239 in MS12-050 replaced by KB2687401 |
Non-Affected Software
| Office and Other Software |
|---|
| Microsoft Communicator 2005 |
| Microsoft Communicator 2005 Web Access |
| Microsoft Communicator 2007 |
| Microsoft Communicator 2007 Web Access |
| Microsoft Communications Server 2007 |
| Microsoft Communications Server 2007 Speech Server |
| Microsoft Communications Server 2007 R2 |
| Microsoft Communicator 2007 R2 Attendant |
| Microsoft Communicator 2007 R2 Group Chat Admin |
| Microsoft Communicator 2007 R2 Group Chat Client |
| Microsoft Live Meeting 2007 Console |
| Microsoft Communicator for Mac 2011 |
| Microsoft Communicator Mobile |
| Microsoft Communicator Phone Edition |
| Microsoft Lync Server 2010 |
| Microsoft Lync 2010 Attendant (32-bit) |
| Microsoft Lync 2010 Attendant (64-bit) |
| Microsoft Lync 2010 Group Chat |
| Microsoft Lync Server 2010 Group Chat Software Development Kit |
| Microsoft Lync for Mac 2011 |
| Microsoft Groove 2007 Service Pack 2 |
| Microsoft Groove 2007 Service Pack 3 |
| Microsoft Groove Server 2007 Service Pack 2 |
| Microsoft Groove Server 2007 Service Pack 3 |
| Microsoft InfoPath 2003 Service Pack 3 |
| Microsoft Live Communications Server 2003 |
| Microsoft Live Communications Server 2005 Service Pack 1 |
| Microsoft SharePoint Portal Server 2003 Service Pack 3 (32-bit editions) |
| Microsoft SharePoint Portal Server 2003 Service Pack 3 (64-bit editions) |
| Microsoft Speech Server 2004 |
| Microsoft Speech Server 2004 R2 |
| Microsoft Windows SharePoint Services 2.0 (32-bit editions) |
| Microsoft Windows SharePoint Services 2.0 (64-bit editions) |
| Microsoft SharePoint Workspace 2010 Service Pack 1 (32-bit editions) |
| Microsoft SharePoint Workspace 2010 Service Pack 1 (64-bit editions) |
Frequently Asked Questions (FAQ) Related to This Security Update
How does MS12-064 relate to this bulletin (MS12-066)?
The security update packages for Microsoft Office Web Apps 2010 Service Pack 1 (KB2687401) in this bulletin, MS12-066, also address the vulnerabilities described in MS12-064.
A Microsoft Office component discussed in this bulletin is part of the Microsoft Office Suite that I have installed on my system; however, I did not choose to install this specific component. Will I be offered this update?
Yes, if the component discussed in this bulletin was delivered with the version of the Microsoft Office Suite installed on your system, the system will be offered updates for it whether the component is installed or not. The detection logic used to scan for affected systems is designed to check for updates for all components that were delivered with the particular Microsoft Office Suite and to offer the updates to a system. Users who choose not to apply an update for a component that is not installed, but is delivered with their version of the Microsoft Office Suite, will not increase the security risk of that system. On the other hand, users who do choose to install the update will not have a negative impact on the security or performance of a system.
For example, Microsoft InfoPath 2010 is included in Microsoft Office Professional Plus 2010. Systems with Microsoft Office Professional Plus 2010 will be offered updates for InfoPath 2010 whether InfoPath 2010 is installed or not. This would not be the case for Microsoft Office Standard 2010, because InfoPath 2010 is not included in Office Standard 2010.
Does the offer to update a non-vulnerable version of Microsoft Office constitute an issue in the Microsoft update mechanism?
No, the update mechanism is functioning correctly in that it detects a lower version of the files on the system than in the update package and thus, offers the update.
Why are multiple update packages available for some affected software?
The updates required to address the vulnerabilities described in this bulletin are offered across different updates packages as indicated in the Affected Software table due to the componentized servicing model for Microsoft Office and Microsoft SharePoint Server software.
There are multiple update packages available for some affected software. Do I need to install all of the updates listed in the Affected Software table for the software?
Yes. Customers should apply all updates offered for the software installed on their systems.
For administrators and enterprise installations, or end users who want to install this security update manually, depending on their configuration of Microsoft Office SharePoint Server, not all the server-package updates listed in this bulletin may apply. For more information on the applicability of these server-package updates in a SharePoint environment, see Microsoft Knowledge Base Article 2741517.
Do I need to install these security updates in a particular sequence?
No. Multiple updates for one version of Microsoft Office or Microsoft SharePoint Server software can be applied in any sequence.
What is Microsoft Groove Server 2010?
Microsoft Groove Server 2010 provides comprehensive services for managing Microsoft SharePoint Workspace. Groove Server 2010 contains two components: Groove Server 2010 Manager and Groove Server 2010 Relay, each of which runs on a Windows server on an enterprise network.
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 KB2687356 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.
What is Microsoft 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.
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.
Where are the file information details?
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.
Why is the Lync 2010 Attendee (user level install) update only available from the Microsoft Download Center?
Microsoft is releasing the update for Lync 2010 Attendee (user level install) to the Microsoft Download Center only. Because the user level installation of Lync 2010 Attendee is handled through a Lync session, distribution methods such as automatic updating are not appropriate for this type of installation scenario.
Where are the hashes of the security updates?
The SHA1 and SHA2 hashes of the security updates can be used to verify the authenticity of downloaded security update packages. For the hash information pertaining to this update, see Microsoft Knowledge Base Article 2741517.
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, see the Microsoft Support Lifecycle website.
It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. To determine the support lifecycle for your software release, see Select a Product for Lifecycle Information. For more information about service packs for these software releases, see Service Pack Lifecycle Support Policy.
Customers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, see the Microsoft Worldwide Information website, select the country in the Contact Information list, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Microsoft Support Lifecycle Policy FAQ.
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 October bulletin summary. For more information, see Microsoft Exploitability Index.
| Affected Software | HTML Sanitization Vulnerability - CVE-2012-2520 | Aggregate Severity Rating |
|---|---|---|
| Microsoft Office Client Software | ||
| Microsoft InfoPath 2007 Service Pack 2 | Important Elevation of Privilege | Important |
| Microsoft InfoPath 2007 Service Pack 3 | Important Elevation of Privilege | Important |
| Microsoft InfoPath 2010 Service Pack 1 (32-bit editions) | Important Elevation of Privilege | Important |
| Microsoft InfoPath 2010 Service Pack 1 (64-bit editions) | Important Elevation of Privilege | Important |
| **Microsoft Communications Platforms and Software ** | ||
| Microsoft Communicator 2007 R2 | Important **Information Disclosure | Important |
| Microsoft Lync 2010 (32-bit) | Important **Information Disclosure | Important |
| Microsoft Lync 2010 (64-bit) | Important **Information Disclosure | Important |
| Microsoft Lync 2010 Attendee (admin level install) | Important **Information Disclosure | Important |
| Microsoft Lync 2010 Attendee (user level install) | Important **Information Disclosure | Important |
| Microsoft SharePoint Server | ||
| Microsoft SharePoint Server 2007 Service Pack 2 (32-bit editions) | Important Elevation of Privilege | Important |
| Microsoft SharePoint Server 2007 Service Pack 2 (64-bit editions) | Important Elevation of Privilege | Important |
| Microsoft SharePoint Server 2007 Service Pack 3 (32-bit editions) | Important Elevation of Privilege | Important |
| Microsoft SharePoint Server 2007 Service Pack 3 (64-bit editions) | Important Elevation of Privilege | Important |
| Microsoft SharePoint Server 2010 Service Pack 1 | Important Elevation of Privilege | Important |
| Microsoft Groove Server | ||
| Microsoft Groove Server 2010 Service Pack 1 | Important Elevation of Privilege | Important |
| Windows SharePoint Services and Microsoft SharePoint Foundation | ||
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (32-bit version) | Important Elevation of Privilege | Important |
| Microsoft Windows SharePoint Services 3.0 Service Pack 3 (32-bit version) | Important Elevation of Privilege | Important |
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (64-bit version) | Important Elevation of Privilege | Important |
| Microsoft Windows SharePoint Services 3.0 Service Pack 3 (64-bit version) | Important Elevation of Privilege | Important |
| Microsoft SharePoint Foundation 2010 Service Pack 1 | Important Elevation of Privilege | Important |
| Microsoft Offices Web Apps | ||
| Microsoft Office Web Apps 2010 Service Pack 1 | Important Elevation of Privilege | Important |
HTML Sanitization Vulnerability - CVE-2012-2520
An elevation of privilege vulnerability exists in the way that HTML strings are sanitized. An attacker who successfully exploited this vulnerability could perform cross-site scripting attacks and run script in the security context of the logged-on user.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2012-2520.
Mitigating Factors for HTML Sanitization Vulnerability - CVE-2012-2520
Microsoft has not identified any mitigating factors for this vulnerability.
Workarounds for HTML Sanitization Vulnerability - CVE-2012-2520
Microsoft has not identified any workarounds for this vulnerability.
FAQ for HTML Sanitization Vulnerability - CVE-2012-2520
What is the scope of the vulnerability?
This is an elevation of privilege vulnerability.
What causes the vulnerability?
The vulnerability is caused by the way that HTML strings are sanitized.
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 or use the victim's identity to take actions on the targeted site or application.
How could an attacker exploit the vulnerability?
To exploit this vulnerability, an attacker would have to convince a user to click a link that goes to a specially crafted URL, or send the user a specially crafted chat message.
In a web-based attack scenario, an attacker would have to host a website that contains a specially crafted URL that directs the user to the targeted SharePoint site that is used to attempt to exploit this vulnerability. In addition, compromised websites and websites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted website. Instead, an attacker would have to convince them to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes them to the attacker's website.
In a chat-based attack scenario, an attacker must have the ability to submit a specially crafted script to a Lync or Microsoft Communicator chat window. Because of 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 receives a specially crafted chat message for any malicious action to occur.
What systems are primarily at risk from the vulnerability?
Systems where Microsoft Lync or Microsoft Communicator are used frequently and environments where users connect to a SharePoint server are primarily at risk for this vulnerability.
What is HTML sanitization?
HTML sanitization is a process that restricts HTML to elements that can be safely displayed in a browser.
What does the update do?
The update addresses the vulnerability by modifying the way that HTML strings are sanitized.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CVE-2012-2520.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
Yes. Microsoft is aware of limited, targeted attacks attempting to exploit the vulnerability.
Update Information
Detection and Deployment Tools and Guidance
Security Central
Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security website provides additional information about security in Microsoft products.
Security updates are available from Microsoft Update and Windows Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."
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, "MS12-001"), you can add all 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) lets administrators scan local and remote systems for missing security updates as well as common security misconfigurations. For more information, see Microsoft Baseline Security Analyzer.
The following table provides the MBSA detection summary for this security update.
| Software | MBSA |
|---|---|
| Microsoft InfoPath 2007 Service Pack 2 | Yes |
| Microsoft InfoPath 2007 Service Pack 3 | Yes |
| Microsoft InfoPath 2010 Service Pack 1 (32-bit editions) | Yes |
| Microsoft InfoPath 2010 Service Pack 1 (64-bit editions) | Yes |
| Microsoft Communicator 2007 R2 | Yes |
| Microsoft Lync 2010 (32-bit) | Yes |
| Microsoft Lync 2010 (64-bit) | Yes |
| Microsoft Lync 2010 Attendee (admin level install) | Yes |
| Microsoft Lync 2010 Attendee (user level install) | No |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions) | Yes |
| Microsoft Office SharePoint Server 2007 Service Pack 3 (32-bit editions) | Yes |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions) | Yes |
| Microsoft Office SharePoint Server 2007 Service Pack 3 (64-bit editions) | Yes |
| Microsoft SharePoint Server 2010 Service Pack 1 | Yes |
| Microsoft Groove Server 2010 Service Pack 1 | Yes |
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (32-bit version) | Yes |
| Microsoft Windows SharePoint Services 3.0 Service Pack 3 (32-bit version) | Yes |
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (64-bit version) | Yes |
| Microsoft Windows SharePoint Services 3.0 Service Pack 3 (64-bit version) | Yes |
| SharePoint Foundation 2010 Service Pack 1 | Yes |
| Microsoft Office Web Apps 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 see Microsoft Baseline Security Analyzer and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools.
Windows Server Update Services
Windows Server Update Services (WSUS) enables information technology administrators to deploy the latest Microsoft product updates to computers that are running the Windows operating system. For more information about how to deploy security updates using Windows Server Update Services, see the TechNet article, Windows Server Update Services.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
| Software | SMS 2003 with ITMU | System Center Configuration Manager |
|---|---|---|
| Microsoft InfoPath 2007 Service Pack 2 | Yes | Yes |
| Microsoft InfoPath 2007 Service Pack 3 | Yes | Yes |
| Microsoft InfoPath 2010 Service Pack 1 (32-bit editions) | Yes | Yes |
| Microsoft InfoPath 2010 Service Pack 1 (64-bit editions) | Yes | Yes |
| Microsoft Communicator 2007 R2 | Yes | Yes |
| Microsoft Lync 2010 (32-bit) | Yes | Yes |
| Microsoft Lync 2010 (64-bit) | Yes | Yes |
| Microsoft Lync 2010 Attendee (admin level install) | Yes | Yes |
| Microsoft Lync 2010 Attendee (user level install) | No | No |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions) | Yes[1] | Yes[1] |
| Microsoft Office SharePoint Server 2007 Service Pack 3 (32-bit editions) | Yes[1] | Yes[1] |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions) | Yes[1] | Yes[1] |
| Microsoft Office SharePoint Server 2007 Service Pack 3 (64-bit editions) | Yes[1] | Yes[1] |
| Microsoft SharePoint Server 2010 Service Pack 1 | Yes[1] | Yes[1] |
| Microsoft Groove Server 2010 Service Pack 1 | Yes | Yes |
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (32-bit version) | Yes | Yes |
| Microsoft Windows SharePoint Services 3.0 Service Pack 3 (32-bit version) | Yes | Yes |
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (64-bit version) | Yes | Yes |
| Microsoft Windows SharePoint Services 3.0 Service Pack 3 (64-bit version) | Yes | Yes |
| SharePoint Foundation 2010 Service Pack 1 | Yes | Yes |
| Microsoft SharePoint Server 2010 Service Pack 1 | Yes | Yes |
[1]The detection table described above is based on single-server Microsoft Office SharePoint Server 2007 and Microsoft SharePoint Server 2010 deployments. The detection tools do not detect the applicability of the update on systems configured as part of a multiple-system SharePoint server farms.
Note Microsoft discontinued support for SMS 2.0 on April 12, 2011. For SMS 2003, Microsoft also discontinued support for the Security Update Inventory Tool (SUIT) on April 12, 2011. Customers are encouraged to upgrade to System Center Configuration Manager. For customers remaining on SMS 2003 Service Pack 3, the Inventory Tool for Microsoft Updates (ITMU) is also an option.
For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.
System Center Configuration Manager uses WSUS 3.0 for detection of updates. For more information, see System Center.
For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.
Note If you have used an Administrative Installation Point (AIP) for deploying 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 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, see the Windows Server Update Services website.
Update Compatibility Evaluator and Application Compatibility Toolkit
Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit.
The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
InfoPath 2007 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
|---|---|
| Deployment | |
| Installing without user intervention | For all supported editions of InfoPath 2007:\ infopath2007-kb2687439-fullfile-x86-glb.exe /passive\ ipeditor2007-kb2687440-fullfile-x86-glb.exe /passive |
| Installing without restarting | For all supported editions of InfoPath 2007:\ infopath2007-kb2687439-fullfile-x86-glb.exe /norestart\ ipeditor2007-kb2687440-fullfile-x86-glb.exe /norestart |
| Update log file | Not applicable |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.\ \ To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
| HotPatching | Not applicable |
| Removal Information | Use Add or Remove Programs item in Control Panel. |
| File Information | For all supported editions of Microsoft InfoPath 2007:\ See Microsoft Knowledge Base Article 2687439 and Microsoft Knowledge Base Article 2687440 |
| Registry Key Verification | Not applicable |
Deployment Information
Installing the Update
You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.
This security update requires that Windows Installer 3.1 or later version be installed on the system.
To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft websites:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Microsoft Windows 2000
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
| Switch | Description |
|---|---|
| /? or /help | Displays usage dialog. |
| /passive | Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel. |
| /quiet | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /norestart | Suppresses restarting the system if the update requires a restart. |
| /forcerestart | Automatically restarts the system after applying the update, regardless of whether the update requires the restart. |
| /extract | Extracts the files without installing them. You are prompted for a target folder. |
| /extract:<path> | Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. |
| /lang:<LCID> | Forces the use of a specific language, when the update package supports that language. |
| /log:<log file> | Enables logging, by both Vnox and Installer, during the update installation. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
To remove this security update, use the Add or Remove Programs item in Control Panel.
Note When you remove this update, you may be prompted to insert the 2007 Microsoft Office CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs item in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.Click Start and then enter an update file name in the Start Search box.
When the file appears under Programs, right-click the file name and click Properties.
On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed.
You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
InfoPath 2010 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
|---|---|
| Deployment | |
| Installing without user intervention | For all supported 32-bit editions of InfoPath 2010: infopath2010-kb2687436-fullfile-x86-glb.exe /passive ipeditor2010-kb2687417-fullfile-x86-glb.exe /passive |
| For all supported x64-based editions of InfoPath 2010: infopath2010-kb2687436-fullfile-x64-glb.exe /passive ipeditor2010-kb2687417-fullfile-x64-glb.exe /passive | |
| Installing without restarting | For all supported 32-bit editions of InfoPath 2010: infopath2010-kb2687436-fullfile-x86-glb.exe /norestart ipeditor2010-kb2687417-fullfile-x86-glb.exe /norestart |
| For all supported x64-based editions of InfoPath 2010: infopath2010-kb2687436-fullfile-x64-glb.exe /norestart ipeditor2010-kb2687417-fullfile-x64-glb.exe /norestart | |
| Update log file | Not applicable |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
| HotPatching | Not applicable. |
| Removal Information | Use Add or Remove Programs item in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 2687436 and Microsoft Knowledge Base Article 2687417 |
| Registry Key Verification | Not applicable |
Deployment Information
Installing the Update
You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.
This security update requires that Windows Installer 3.1 or later version be installed on the system.
To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft websites:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Microsoft Windows 2000
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
| Switch | Description |
|---|---|
| /? or /help | Displays usage dialog. |
| /passive | Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel. |
| /quiet | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /norestart | Suppresses restarting the system if the update requires a restart. |
| /forcerestart | Automatically restarts the system after applying the update, regardless of whether the update requires the restart. |
| /extract | Extracts the files without installing them. You are prompted for a target folder. |
| /extract:<path> | Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. |
| /lang:<LCID> | Forces the use of a specific language, when the update package supports that language. |
| /log:<log file> | Enables logging, by both Vnox and Installer, during the update installation. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
To remove this security update, use the Add or Remove Programs item in Control Panel.
Note When you remove this update, you may be prompted to insert the 2007 Microsoft Office CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs item in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
Verifying that the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.Click Start and then enter an update file name in the Start Search box.
When the file appears under Programs, right-click the file name and click Properties.
On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed.
You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Microsoft Communicator 2007 R2, Microsoft Lync 2010, Microsoft Lync 2010 Attendee
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 Microsoft Communicator 2007 R2 (KB2726391): communicator.msp /passive |
| For Microsoft Lync 2010 (32-bit) (KB2726382): lync.msp /passive | |
| For Microsoft Lync 2010 (64-bit) (KB2726382): lync.msp /passive | |
| For Microsoft Lync 2010 Attendee (admin level install) (KB2726388): AttendeeAdmin.msp /passive | |
| For Microsoft Lync 2010 Attendee (user level install) (KB2726384): AttendeeUser.msp /passive | |
| Installing without restarting | For Microsoft Communicator 2007 R2 (KB2726391): communicator.msp /norestart |
| For Microsoft Lync 2010 (32-bit) (KB2726382): lync.msp /norestart | |
| For Microsoft Lync 2010 (64-bit) (KB2726382): lync.msp /norestart | |
| For Microsoft Lync 2010 Attendee (admin level install) (KB2726388): AttendeeAdmin.msp /norestart | |
| For Microsoft Lync 2010 Attendee (user level install) (KB2726384): AttendeeUser.msp /norestart | |
| Update log file | Not applicable |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
| HotPatching | Not applicable. |
| Removal Information | Use Add or Remove Programs item in Control Panel. |
| File Information | For Microsoft Communicator 2007 R2: See Microsoft Knowledge Base Article 2726391 |
| For all supported editions of Microsoft Lync 2010: See Microsoft Knowledge Base Article 2726382 | |
| For Microsoft Lync 2010 Attendee (admin level install): See Microsoft Knowledge Base Article 2726388 | |
| For Microsoft Lync 2010 Attendee (user level install): See Microsoft Knowledge Base Article 2726384 | |
| Registry Key Verification | For Microsoft Communicator 2007 R2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{0EEB34F6-991D-4a1b-8EEB-772DA0EADB22} Version = 3.5.6907.261 |
| For Microsoft Lync 2010 (32-bit): HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{0EEB34F6-991D-4a1b-8EEB-772DA0EADB22} Version = 4.0.7577.4109 | |
| For Microsoft Lync 2010 (64-bit): HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Active Setup\Installed Components\{0EEB34F6-991D-4a1b-8EEB-772DA0EADB22} Version = 4.0.7577.4109 | |
| For Microsoft Lync 2010 Attendee (admin level install): HKEY_CURRENT_USER\SOFTWARE\Microsoft\Active Setup\Installed Components\{0EEB34F6-991D-4a1b-8EEB-772DA0EADB22} Version = 4.0.7577.4109 | |
| For Microsoft Lync 2010 Attendee (user level install): HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{0EEB34F6-991D-4a1b-8EEB-772DA0EADB22} Version = 4.0.7577.4109 |
Deployment Information
Installing the Update
You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.
This security update requires that Windows Installer 3.1 or later version be installed on the system.
To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft websites:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Microsoft Windows 2000
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
| Switch | Description | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| /help | Displays the command-line options. | ||||||||||||||
| /quiet or **/q[n | b | r | f]** | Quiet mode, no user interaction or\ /q[n | b | r | f] sets user interface level:\ n - No user interface\ b - Basic user interface\ r - Reduced user interface\ f - Full user interface (default) | ||||||||
| /passive | Unattended mode - progress bar only. | ||||||||||||||
| /norestart | Do not restart after the installation is complete. | ||||||||||||||
| **/l[i | w | e | a | r | u | c | m | o | p | v | x | + | ! | *] <LogFile>** | Enables logging. Options:\ i - Status messages\ w - Nonfatal warnings\ e - All error messages\ a - Start up of actions\ r - Action-specific records\ u - User requests\ c - Initial UI parameters\ m - Out-of-memory or fatal exit information\ o - Out-of-disk-space messages\ p - Terminal properties\ v - Verbose output\ x - Extra debugging information\ + - Append to existing log file\ ! - Flush each line to the log\ * - Log all information, except for v and x options |
| /log<LogFile> | Equivalent of /l* <LogFile>. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
To remove this security update, use the Add or Remove Programs item in Control Panel.
Note When you remove this update, you may be prompted to insert the 2007 Microsoft Office CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs item in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
Verifying that the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.Click Start and then enter an update file name in the Start Search box.
When the file appears under Programs, right-click the file name and click Properties.
On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed.
You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Registry Key Verification
You may also be able to verify that the security update has installed by reviewing the registry keys listed in the Reference Table in this section.
SharePoint Server 2007 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | There are no more service packs planned for this software. The update for this issue may be included in a future update rollup. |
|---|---|
| Deployment | |
| Installing without user intervention | For all supported 32-bit editions of Microsoft Office SharePoint Server 2007:\ coreserver2007-kb2687405-fullfile-x86-glb.exe /passive |
| For all supported x64-based editions of Microsoft Office SharePoint Server 2007:\ coreserver2007-kb2687405-fullfile-x64-glb.exe /passive | |
| Installing without restarting | For all supported 32-bit editions of Microsoft Office SharePoint Server 2007:\ coreserver2007-kb2687405-fullfile-x86-glb.exe /norestart |
| For all supported x64-based editions of Microsoft Office SharePoint Server 2007:\ coreserver2007-kb2687405-fullfile-x64-glb.exe /norestart | |
| Update log file | Not applicable |
| Further information | See the subsection, 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 2687405 |
| Registry Key Verification | Not applicable |
Deployment Information
Installing the Update
You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.
This security update requires that Windows Installer 3.1 or later version be installed on the system.
To install the 3.1 or later version of Windows Installer, see one of the following Microsoft websites:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Windows 2000
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
| Switch | Description |
|---|---|
| /? or /help | Displays usage dialog. |
| /passive | Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel. |
| /quiet | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /norestart | Suppresses restarting the system if the update requires a restart. |
| /forcerestart | Automatically restarts the system after applying the update, regardless of whether the update requires the restart. |
| /extract | Extracts the files without installing them. You are prompted for a target folder. |
| /extract:<path> | Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. |
| /lang:<LCID> | Forces the use of a specific language, when the update package supports that language. |
| /log:<log file> | Enables logging, by both Vnox and Installer, during the update installation. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
This security update cannot be removed.
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
- Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
SharePoint Server 2010 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | There are no more service packs planned for this software. The update for this issue may be included in a future update rollup. |
|---|---|
| Deployment | |
| Installing without user intervention | For all supported editions of Microsoft Office SharePoint Server 2010:\ wosrv2010-kb2687435-fullfile-x64-glb.exe /passive\ coreserver2010-kb2589280-fullfile-x64-glb.exe /passive |
| Installing without restarting | For all supported editions of Microsoft Office SharePoint Server 2010:\ wosrv2010-kb2687435-fullfile-x64-glb.exe /norestart\ coreserver2010-kb2589280-fullfile-x64-glb.exe /norestart |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Update log file | Not applicable |
| 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 2687435 and Microsoft Knowledge Base Article 2589280 |
| Registry Key Verification | Not applicable |
Deployment Information
Installing the Update
You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.
This security update requires that Windows Installer 3.1 or later version be installed on the system.
To install the 3.1 or later version of Windows Installer, see one of the following Microsoft websites:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Windows 2000
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
| Switch | Description |
|---|---|
| /? or /help | Displays usage dialog. |
| /passive | Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel. |
| /quiet | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /norestart | Suppresses restarting the system if the update requires a restart. |
| /forcerestart | Automatically restarts the system after applying the update, regardless of whether the update requires the restart. |
| /extract | Extracts the files without installing them. You are prompted for a target folder. |
| /extract:<path> | Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. |
| /lang:<LCID> | Forces the use of a specific language, when the update package supports that language. |
| /log:<log file> | Enables logging, by both Vnox and Installer, during the update installation. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
This security update cannot be removed.
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.- Click Start and then enter an update file name in Start Search.
- When the file appears under Programs, right-click on the file name and click Properties.
- Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
- Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Groove Server 2010 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | There are no more service packs planned for this software. The update for this issue may be included in a future update rollup. |
|---|---|
| Deployment | |
| Installing without user intervention | For all supported editions of Microsoft Groove Server 2010:\ emsgrs2010-kb2687402-fullfile-x64-glb.exe /passive |
| Installing without restarting | For all supported editions of Microsoft Groove Server 2010:\ emsgrs2010-kb2687402-fullfile-x64-glb.exe /norestart |
| Further information | See the subsection, 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 2687402 |
| Registry Key Verification | Not applicable |
Deployment Information
Installing the Update
You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.
This security update requires that Windows Installer 3.1 or later version be installed on the system.
To install the 3.1 or later version of Windows Installer, see one of the following Microsoft websites:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Windows 2000
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
| Switch | Description |
|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|
| /?, /h, /help | Displays help on supported switches. |
| /quiet | Suppresses the display of status or error messages. |
| /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
| /warnrestart:<seconds> | When combined with /quiet, the installer will warn the user before initiating restart. |
| /promptrestart | When combined with /quiet, the installer will prompt before initiating restart. |
| /forcerestart | When combined with /quiet, the installer will forcefully close applications and initiate restart. |
| /log:<file name> | Enables logging to specified file. |
| /extract:<destination> | Extracts the package contents to the destination folder. |
| /uninstall /kb:<KB Number> | Uninstalls the security update. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
This security update cannot be removed.
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
- Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Windows SharePoint Services 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 all supported 32-bit editions of Microsoft Windows SharePoint Services 3.0:\ sts2007-kb2687356-fullfile-x86-glb.exe /passive |
| For all supported 64-bit editions of Microsoft Windows SharePoint Services 3.0:\ sts2007-kb2687356-fullfile-x64-glb.exe /passive | |
| Installing without restarting | For all supported 32-bit editions of Microsoft Windows SharePoint Services 3.0:\ sts2007-kb2687356-fullfile-x86-glb.exe /norestart |
| For all supported 64-bit editions of Microsoft Windows SharePoint Services 3.0:\ sts2007-kb2687356-fullfile-x64-glb.exe /norestart | |
| Further information | See the subsection, 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 2687356 |
| Registry Key Verification | Not applicable |
Deployment Information
Installing the Update
You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.
This security update requires that Windows Installer 3.1 or later version be installed on the system.
To install the 3.1 or later version of Windows Installer, see one of the following Microsoft websites:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Windows 2000
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
| Switch | Description |
|---------------------------|---------------------------------------------------------------------------------------------------------------------|
| /? or /help | Displays usage dialog. |
| /passive | Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel. |
| /quiet | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /norestart | Suppresses restarting the system if the update requires a restart. |
| /forcerestart | Automatically restarts the system after applying the update, regardless of whether the update requires the restart. |
| /extract | Extracts the files without installing them. You are prompted for a target folder. |
| /extract:<path> | Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. |
| /lang:<LCID> | Forces the use of a specific language, when the update package supports that language. |
| /log:<log file> | Enables logging, by both Vnox and Installer, during the update installation. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
This security update cannot be removed.
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.- Click Start and then enter an update file name in Start Search.
- When the file appears under Programs, right-click on the file name and click Properties.
- Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
- Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Microsoft SharePoint Foundation 2010 (all versions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | There are no more service packs planned for this software. The update for this issue may be included in a future update rollup. |
|---|---|
| Deployment | |
| Installing without user intervention | For Microsoft SharePoint Foundation 2010 Service Pack 1:\ wss2010-kb2687434-fullfile-x64-glb.exe /passive |
| Installing without restarting | For Microsoft SharePoint Foundation 2010 Service Pack 1:\ wss2010-kb2687434-fullfile-x64-glb.exe /norestart |
| Update log file | Not applicable |
| Further information | See the subsection, 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 2687434 |
| Registry Key Verification | Not applicable |
Deployment Information
Installing the Update
You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.
This security update requires that Windows Installer 3.1 or later version be installed on the system.
To install the 3.1 or later version of Windows Installer, see one of the following Microsoft websites:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Windows 2000
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
| Switch | Description |
|---------------------------|---------------------------------------------------------------------------------------------------------------------|
| /? or /help | Displays usage dialog. |
| /passive | Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel. |
| /quiet | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /norestart | Suppresses restarting the system if the update requires a restart. |
| /forcerestart | Automatically restarts the system after applying the update, regardless of whether the update requires the restart. |
| /extract | Extracts the files without installing them. You are prompted for a target folder. |
| /extract:<path> | Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. |
| /lang:<LCID> | Forces the use of a specific language, when the update package supports that language. |
| /log:<log file> | Enables logging, by both Vnox and Installer, during the update installation. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
This security update cannot be removed.
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.- Click Start and then enter an update file name in Start Search.
- When the file appears under Programs, right-click on the file name and click Properties.
- Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
- Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Office Web Apps 2010 (all versions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | There are no more service packs planned for this software. The update for this issue may be included in a future update rollup. |
|---|---|
| Deployment | |
| Installing without user intervention | For Office Web Apps 2010 Service Pack 1:\ wac2010-kb2687401-fullfile-x64-glb.exe /passive |
| Installing without restarting | For Office Web Apps 2010 Service Pack 1:\ wac2010-kb2687401-fullfile-x64-glb.exe /norestart |
| Update log file | Not applicable |
| Further information | See the subsection, 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 2687401 |
| Registry Key Verification | Not applicable |
Deployment Information
Installing the Update
You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.
This security update requires that Windows Installer 3.1 or later version be installed on the system.
To install the 3.1 or later version of Windows Installer, see one of the following Microsoft websites:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Windows 2000
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
| Switch | Description |
|---------------------------|---------------------------------------------------------------------------------------------------------------------|
| /? or /help | Displays usage dialog. |
| /passive | Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel. |
| /quiet | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /norestart | Suppresses restarting the system if the update requires a restart. |
| /forcerestart | Automatically restarts the system after applying the update, regardless of whether the update requires the restart. |
| /extract | Extracts the files without installing them. You are prompted for a target folder. |
| /extract:<path> | Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. |
| /lang:<LCID> | Forces the use of a specific language, when the update package supports that language. |
| /log:<log file> | Enables logging, by both Vnox and Installer, during the update installation. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
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:
- Drew Hintz and Andrew Lyons of Google Security Team for reporting the HTML Sanitization Vulnerability (CVE-2012-2520)
Microsoft Active Protections Program (MAPP)
To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please go to the active protections websites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.
Support
How to obtain help and support for this security update
- Help installing updates: Support for Microsoft Update
- Security solutions for IT professionals: TechNet Security Troubleshooting and Support
- Help protect your computer that is running Windows from viruses and malware: Virus Solution and Security Center
- Local support according to your country: International Support
Disclaimer
The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Revisions
- V1.0 (October 9, 2012): Bulletin published.
- V1.1 (October 10, 2012): Corrected KB numbers for Microsoft Lync 2010 Attendee (admin level install) and Microsoft Lync 2010 Attendee (user level install). This is an informational change only. Customers who have already successfully updated their systems do not need to take any action.
- V1.2 (October 17, 2012): Corrected update replacement information. Corrected KB numbers for Microsoft Lync 2010 Attendee (admin level install) and Microsoft Lync 2010 Attendee (user level install). These are informational changes only. Customers who have already successfully updated their systems do not need to take any action.
- V1.3 (October 23, 2012): Added Microsoft Windows SharePoint Services 3.0 Service Pack 3 (32-bit version) and Microsoft Windows SharePoint Services 3.0 Service Pack 3 (64-bit version) to the Affected Software section. This is a bulletin change only. There were no changes to the detection logic or security update files.
- V1.4 (January 15, 2014): Bulletin revised to announce a detection change in update 2687356 (a.k.a. 2687442). This is a detection change only. Customers who have already successfully updated their systems do not need to take any action. Note that update 2687356 is offered through Microsoft Update as update 2687442.
Built at 2014-04-18T13:49:36Z-07:00