Microsoft Security Bulletin MS10-072 - Important
Vulnerabilities in SafeHTML Could Allow Information Disclosure (2412048)
Published: | Updated:
Version: 1.1
General Information
Executive Summary
This security update resolves one publicly disclosed vulnerability and one privately reported vulnerability in Microsoft SharePoint and Windows SharePoint Services. The vulnerabilities could allow information disclosure if an attacker submits specially crafted script to a target site using SafeHTML.
This security update is rated Important for Microsoft SharePoint Services 3.0, Microsoft SharePoint Foundation 2010, and Microsoft Office Web Apps; and all supported editions of Microsoft Office SharePoint Server 2007, and Microsoft Groove Server 2010. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The update addresses the vulnerabilities by modifying the way that SafeHTML sanitizes HTML content. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. Microsoft recommends that customers apply the update at the earliest opportunity.
Known Issues. Microsoft Knowledge Base Article 2412048 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
| Software | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by this Update |
|---|---|---|---|
| Windows SharePoint Services and Microsoft SharePoint Foundation | |||
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (32-bit versions) (KB2345304) | Information Disclosure | Important | MS10-039 |
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (64-bit versions) (KB2345304) | Information Disclosure | Important | MS10-039 |
| Microsoft SharePoint Foundation 2010 (KB2345322) | Information Disclosure | Important | None |
| Microsoft SharePoint Server and Microsoft Groove Server | |||
| Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions)[1] (KB2345212) | Information Disclosure | Important | MS10-039 |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions)[1] (KB2345212) | Information Disclosure | Important | MS10-039 |
| Microsoft Groove Server 2010 (KB2346298) | Information Disclosure | Important | None |
| Microsoft Office Web Apps | |||
| Microsoft Office Web Apps (KB2346411) | Information Disclosure | Important | None |
[1]For supported editions of Microsoft Office SharePoint Server 2007, in addition to security update package KB2345212, customers also need to install the security update for Microsoft Windows SharePoint Services 3.0 (KB2345304) to be protected from the vulnerabilities described in this bulletin.
Non-Affected Software
| Office and Other Software |
|---|
| Microsoft Windows SharePoint Services 2.0 |
| Microsoft SharePoint Portal Server 2001 Service Pack 3 |
| Microsoft SharePoint Portal Server 2003 Service Pack 3 |
| Microsoft SharePoint Server 2010 |
| Microsoft Groove 2007 |
| Microsoft SharePoint Workspace |
Frequently Asked Questions (FAQ) Related to This Security Update
Where are the file information details?
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.
How is this security update related to MS10-071?
The HTML Sanitization Vulnerability (CVE-2010-3243) and HTML Sanitization Vulnerability (CVE-2010-3324) are addressed by this update (MS10-072) and the Cumulative Security Update for Internet Explorer (MS10-071) update.
Two different updates are needed because the modifications that are required to address the issue are located in different Microsoft products. This update (MS10-072) addresses the vulnerabilities in affected Microsoft productivity software and MS10-071 addresses the vulnerabilities in Internet Explorer.
MS10-079 also describes vulnerabilities in Microsoft Office Web Apps. How does MS10-079 relate to this bulletin (MS10-072)?
The security update package in this bulletin, MS10-072, for Microsoft Office Web Apps (KB2346411) also addresses a vulnerability described in MS10-079. Users with Microsoft Office Web Apps installed will only need to install the KB2346411 security update package once.
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. Instead of having to install several updates that are almost the same, customers need to install this update only.
What is Microsoft Groove Server 2010?
Microsoft Groove Server 2010 is a Windows-based software package that 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 documents and edit documents. Users can view, share, and work on documents with others online 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 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?
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.
In what configurations will I need to apply the different updates?
You will need to apply one or both updates, depending on which SharePoint product is installed on your system. For systems with only Microsoft Windows SharePoint Services 3.0 installed, you will need to apply the KB2345304 update. For systems with Microsoft Office SharePoint Server 2007 installed, you will need to apply both the KB2345212 and KB2345304 updates. 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 October bulletin summary. For more information, see Microsoft Exploitability Index.
| Affected Software | HTML Sanitization Vulnerability - CVE-2010-3243 | HTML Sanitization Vulnerability - CVE-2010-3324 | Aggregate Severity Rating |
|---|---|---|---|
| Windows SharePoint Services and Microsoft SharePoint Foundation | |||
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (32-bit versions) | Important Information Disclosure | Important Information Disclosure | Important |
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (64-bit versions) | Important Information Disclosure | Important Information Disclosure | Important |
| Microsoft SharePoint Foundation 2010 | Not applicable | Important Information Disclosure | Important |
| Microsoft SharePoint Server and Microsoft Groove Server | |||
| Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions) | Important Information Disclosure | Important Information Disclosure | Important |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions) | Important Information Disclosure | Important Information Disclosure | Important |
| Microsoft Groove Server 2010 | Not applicable | Important Information Disclosure | Important |
| Microsoft Office Web Apps | |||
| Microsoft Office Web Apps | Not applicable | Important Information Disclosure | Important |
HTML Sanitization Vulnerability - CVE-2010-3243
An information disclosure vulnerability exists in the way that HTML is filtered that could allow an attacker to 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-2010-3243.
Mitigating Factors for HTML Sanitization Vulnerability - CVE-2010-3243
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:
- Only sites that use SafeHTML to sanitize HTML are affected.
Workarounds for HTML Sanitization Vulnerability - CVE-2010-3243
Microsoft has not identified any workarounds for this vulnerability.
FAQ for HTML Sanitization Vulnerability - CVE-2010-3243
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 scripts on behalf of the targeted site's users.
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?
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-2010-3324
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-2010-3324.
Mitigating Factors for HTML Sanitization Vulnerability - CVE-2010-3324
Microsoft has not identified any mitigating factors for this vulnerability.
Workarounds for HTML Sanitization Vulnerability - CVE-2010-3324
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:
- Read e-mails in plain text
To help protect yourself from the e-mail attack vector, read e-mail messages in plain text format.
Microsoft Office Outlook 2002 users who have applied Office XP Service Pack 1 or a later version and Microsoft Office Outlook Express 6 users who have applied Internet Explorer 6 Service Pack 1 or a later version can enable this setting and view e-mail messages that are not digitally signed or e-mail messages that are not encrypted in plain text only.
Digitally signed e-mail messages or encrypted e-mail messages are not affected by the setting and may be read in their original formats. For more information about how to enable this setting in Outlook 2002, see Microsoft Knowledge Base Article 307594.
For information about this setting in Outlook Express 6, see Microsoft Knowledge Base Article 291387.
Impact of workaround. E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. Additionally:
- The changes are applied to the preview pane and to open messages.
- Pictures become attachments so that they are not lost.
- Because the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.
- Set Internet and Local intranet security zone settings to "High" to block ActiveX Controls and Active Scripting in these zones
You can help protect against exploitation of this vulnerability by changing your settings for the Internet security zone to block ActiveX controls and Active Scripting. You can do this by setting your browser security to High.
To raise the browsing security level in Internet Explorer, follow these steps:
- On the Internet Explorer Tools menu, click Internet Options.
- In the Internet Options dialog box, click the Security tab, and then click the Internet icon.
- Under Security level for this zone, move the slider to High. This sets the security level for all Web sites you visit to High.
Note If no slider is visible, click Default Level, and then move the slider to High.
Note Setting the level to High may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly even with the security setting set to High.
Impact of workaround. There are side effects to blocking ActiveX Controls and Active Scripting. Many Web sites that are on the Internet or on an intranet use ActiveX or Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX Controls to provide menus, ordering forms, or even account statements. Blocking ActiveX Controls or Active Scripting is a global setting that affects all Internet and intranet sites. If you do not want to block ActiveX Controls or Active Scripting for such sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone".
Add sites that you trust to the Internet Explorer Trusted sites zone
After you set Internet Explorer to block ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect yourself from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.
To do this, follow these steps:
- In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
- In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
- If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
- In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
- Repeat these steps for each site that you want to add to the zone.
- Click OK two times to accept the changes and return to Internet Explorer.
Note Add any sites that you trust not to take malicious action on your system. Two in particular that you may want to add are *.windowsupdate.microsoft.com and *.update.microsoft.com. These are the sites that will host the update, and it requires an ActiveX Control to install the update.
- Configure Internet Explorer to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone
You can help protect against exploitation of this vulnerability by changing your settings to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone. To do this, follow these steps:
- In Internet Explorer, click Internet Options on the Tools menu.
- Click the Security tab.
- Click Internet, and then click Custom Level.
- Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK.
- Click Local intranet, and then click Custom Level.
- Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK.
- Click OK two times to return to Internet Explorer.
Note Disabling Active Scripting in the Internet and Local intranet security zones may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly.
Impact of workaround. There are side effects to prompting before running Active Scripting. Many Web sites that are on the Internet or on an intranet use Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use Active Scripting to provide menus, ordering forms, or even account statements. Prompting before running Active Scripting is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run Active Scripting. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone".
Add sites that you trust to the Internet Explorer Trusted sites zone
After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.
To do this, follow these steps:
- In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
- In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
- If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
- In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
- Repeat these steps for each site that you want to add to the zone.
- Click OK two times to accept the changes and return to Internet Explorer.
Note Add any sites that you trust not to take malicious action on your system. Two in particular that you may want to add are *.windowsupdate.microsoft.com and *.update.microsoft.com. These are the sites that will host the update, and it requires an ActiveX Control to install the update.
FAQ for HTML Sanitization Vulnerability - CVE-2010-3324
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-2010-3324.
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.
Update Information
Detection and Deployment Tools and Guidance
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."
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 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 |
| Microsoft SharePoint Foundation 2010 | 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 Groove Server 2010 | Yes |
| Microsoft Office Web Apps | 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 2.0 | SMS 2003 with SUIT | SMS 2003 with ITMU | Configuration Manager 2007 |
|---|---|---|---|---|
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (32-bit versions) | No | No | Yes | Yes |
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (64-bit versions) | No | No | Yes | Yes |
| Microsoft SharePoint Foundation 2010 | No | No | Yes | Yes |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions) | No | No | Yes. See Note for Microsoft Office SharePoint Server 2007 below | Yes. See Note for Microsoft Office SharePoint Server 2007 below |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions) | No | No | Yes. See Note for Microsoft Office SharePoint Server 2007 below | Yes. See Note for Microsoft Office SharePoint Server 2007 below |
| Microsoft Groove Server 2010 | No | No | Yes | Yes |
| Microsoft Office Web Apps | No | No | Yes | Yes |
For SMS 2.0 and SMS 2003, the Security Update Inventory Tool (SUIT) can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0.
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 The detection table described above is based on single-server Microsoft Office SharePoint Server 2007 deployments. The detection tools do not detect the applicability of the update on systems configured as part of a multiple-system SharePoint server farms. For more information about deploying updates on both stand-alone and multi server configurations, see the TechNet article, Deploy software updates for Office SharePoint Server 2007.
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 Upgrades. - 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:
Windows SharePoint Services 3.0 and Microsoft Foundation 2010
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 | Microsoft Windows SharePoint Services 3.0 Service Pack 2 (32-bit versions): wss-kb2345304-fullfile-x86-glb.exe /passive |
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (64-bit versions): wss-kb2345304-fullfile-x64-glb.exe /passive | |
| Microsoft SharePoint Foundation 2010: spf2010-kb2345322-fullfile-x64-glb.exe /passive | |
| Installing without restarting | Microsoft Windows SharePoint Services 3.0 Service Pack 1 and Microsoft Windows SharePoint Services 3.0 Service Pack 2 (32-bit versions): wss-kb2345304-fullfile-x86-glb.exe /norestart |
| Microsoft Windows SharePoint Services 3.0 Service Pack 1 and Microsoft Windows SharePoint Services 3.0 Service Pack 2 (64-bit versions): wss-kb2345304-fullfile-x64-glb.exe /norestart | |
| Microsoft SharePoint Foundation 2010: spf2010-kb2345322-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 Windows SharePoint Services 3.0, see Microsoft Knowledge Base Article 2345304 |
| For Microsoft SharePoint Foundation 2010, see Microsoft Knowledge Base Article 2345322 | |
| 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.
| 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.
SharePoint Server 2007 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | There are no more service packs planned for this software. The update for this issue may be included in a future update rollup. |
| Deployment | |
| Installing without user intervention | For Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions): office2007-kb2345212-fullfile-x86-glb.exe /passive For Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions): office2007-kb2345212-fullfile-x64-glb.exe /passive |
| Installing without restarting | For Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions): office2007-kb2345212-fullfile-x86-glb.exe /norestart For Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions): office2007-kb2345212-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 2345212 |
| 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.
| 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 Searchbox.
- 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
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 | grooveserver2010-kb2346298-fullfile-x64-glb.exe /passive |
| Installing without restarting | grooveserver2010-kb2346298-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 2346298 |
| 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.
| 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.
Office Web Apps
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 | webapplications2010-kb2346411-fullfile-x64-glb.exe /passive |
| Installing without restarting | webapplications2010-kb2346411-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 2346411 |
| 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.
| 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:
- Sirdarckcat of Google Inc. for reporting the HTML Sanitization Vulnerability (CVE-2010-3243)
- Mario Heiderich for reporting the HTML Sanitization Vulnerability (CVE-2010-3324)
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 (October 12, 2010): Bulletin published.
- V1.1 (October 13, 2010): Added a link to Microsoft Knowledge Base Article 2412048 under Known Issues in the Executive Summary.