Security Bulletin
Microsoft Security Bulletin MS10-104 - Important
Vulnerability in Microsoft SharePoint Could Allow Remote Code Execution (2455005)
Published: December 14, 2010
Version: 1.0
General Information
Executive Summary
This security update resolves a privately reported vulnerability in Microsoft SharePoint. The vulnerability could allow remote code execution in the security context of a guest user if an attacker sent a specially crafted SOAP request to the Document Conversions Launcher Service in a SharePoint server environment that is using the Document Conversions Load Balancer Service. By default, the Document Conversions Load Balancer Service and Document Conversions Launcher Service are not enabled in Microsoft Office SharePoint Server 2007.
This security update is rated Important for all supported editions of Microsoft Office SharePoint Server 2007. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The update addresses the vulnerability by modifying the way that the Document Conversion Launcher Service validates specially crafted SOAP requests. 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. None.
Affected and Non-Affected Software
The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.
Affected Software
| Microsoft SharePoint Server | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by this Update |
|---|---|---|---|
| Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions)\ (KB2433089) | Remote Code Execution | Important | None |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions)\ (KB2433089) | Remote Code Execution | Important | None |
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 Windows SharePoint Services 3.0 Service Pack 2 (32-bit versions) |
| Microsoft Windows SharePoint Services 3.0 Service Pack 2 (64-bit versions) |
| SharePoint Foundation 2010 |
| Microsoft SharePoint Server 2010 |
| Microsoft Groove 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.
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 December bulletin summary. For more information, see Microsoft Exploitability Index.
| Affected Software | Malformed Request Code Execution Vulnerability - CVE-2010-3964 | Aggregate Severity Rating |
|---|---|---|
| Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions) | Important \ Remote Code Execution | Important |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions) | Important \ Remote Code Execution | Important |
Malformed Request Code Execution Vulnerability - CVE-2010-3964
A remote code execution vulnerability exists in the way that the Document Conversions Launcher Service validates SOAP requests before processing on a SharePoint server. An attacker who successfully exploited this vulnerability could run arbitrary code on an affected SharePoint server under the security context of a guest account.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2010-3964.
Mitigating Factors for Malformed Request Code Execution Vulnerability - CVE-2010-3964
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:
- By default, the Document Conversions Load Balancer Service and Document Conversions Launcher Service are not enabled in Microsoft Office SharePoint Server 2007.
- An attacker who successfully exploited this vulnerability could execute code as a guest account that only has rights to a specific temporary directory. The content of this specific temporary directory is cleaned up regularly.
Workarounds for Malformed Request Code Execution Vulnerability - CVE-2010-3964
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:
Stop and Disable Office Document Conversions Launcher Service
Run the following command from a command prompt as an administrator on each system running the Document Conversions Launcher Service:
sc stop dclaunchersc config dclauncher start= disabledImpact of Workaround. Office document conversion is disabled.
How to undo the workaround.
Run the following command from a command prompt as an administrator:
sc config dclauncher start= autosc start dclauncherBlock ports used by the Office Document Conversions Launcher Service at the firewall
Block the following port at the firewall:
TCP Port 8082This port is used to initiate a connection with the affected component. Blocking this port at the enterprise firewall, both inbound and outbound, will help protect systems that are behind that firewall from attempts to exploit this vulnerability. Microsoft recommends that you block all unsolicited inbound communication from the Internet to help prevent attacks that may use other ports. For more information about ports, see the TechNet article, TCP and UDP Port Assignments.
Impact of Workaround. Applications and services may use the affected port. Blocking connectivity to the port may cause various applications or services to not function.
How to undo the workaround.
Unblock TCP port 8082 at the firewall. For more information about ports, see the TechNet article, TCP and UDP Port Assignments.
FAQ for Malformed Request Code Execution Vulnerability - CVE-2010-3964
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could run arbitrary code in the security context of a guest account on the affected SharePoint server.
What causes the vulnerability?
This vulnerability is caused when the Document Conversions Launcher Service does not properly validate specially crafted Simple Object Access Protocol (SOAP) requests.
What is Document Conversions Launcher Service?
Document Conversions Launcher Service schedules and initiates the document conversions on a server. When Microsoft Office SharePoint Server 2007 passes a document conversion request to the service, the Document Conversions Launcher Service calls the appropriate document converter. In most server farm configurations, the Document Conversions Launcher Service and the converter programs that it starts should be installed on an application server. Each application server can only have a single Document Conversions Launcher Service enabled.
Document Conversions Launcher Service runs under the HVU_ComputerName account. The HVU_ComputerName account is a local guest account created on the application server when the Document Conversions Launcher Service is enabled.
What is Document Conversions Load Balancer Service?
Document Conversions Load Balancer Service balances document conversion requests. The Document Conversions Load Balancer Service can be configured on a stand-alone server or on one server in a farm. When it receives a converter request from Microsoft Office SharePoint Server 2007, the Document Conversions Load Balancer Service returns a Uniform Resource Identifier (URI) pointing to the appropriate Document Conversions Launcher Service. SharePoint Server 2007 connects to the specified launcher via SOAP requests and requests that it convert the specified document.
Note that disabling the Document Conversions Load Balancer Service stops the document conversion process and also disables the Document Conversions Launcher Service.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code in the security context of a guest user on the target server.
How could an attacker exploit the vulnerability?
An attacker can send a specially crafted SOAP request to the Document Conversions Launcher Service in a SharePoint server environment that is using the Document Conversions Load Balancer Service. When the Document Conversions Launcher Service processes the specially crafted SOAP request, the vulnerability could allow remote code execution in the security context of a guest account on the affected system.
What systems are primarily at risk from the vulnerability?
SharePoint server environments that use the Document Conversions Load Balancer Service are primarily at risk from this vulnerability. The vulnerability could allow remote code execution on servers running the Document Conversions Launcher Service in the SharePoint server environment.
What does the update do?
This update addresses the vulnerability by modifying the way that the Document Conversion Launcher Service validates specially crafted SOAP requests.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through coordinated vulnerability disclosure.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.
Update Information
Detection and Deployment Tools and Guidance
Security Central
Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
Security updates are available from Microsoft Update and Windows Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."
Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, "MS07-036"), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.
Detection and Deployment Guidance
Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see Microsoft Knowledge Base Article 961747.
Microsoft Baseline Security Analyzer
Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.
The following table provides the MBSA detection summary for this security update.
| Software | MBSA |
|---|---|
| Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions) | Yes |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions) | 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 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 |
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 Updates. - For creating a network installation point for supported versions of Microsoft Office, see Create a network installation point for Microsoft Office.
Note If you plan to manage security updates centrally, use Windows Server Update Services. For more information about how to deploy security updates for Microsoft Office, visit the Windows Server Update Services Web site.
Update Compatibility Evaluator and Application Compatibility Toolkit
Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit.
The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
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-kb2433089-fullfile-x86-glb.exe /passive |
| For Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions):\ Office2007-kb2433089-fullfile-x64-glb.exe /passive | |
| Installing without restarting | For Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions):\ Office2007-kb2433089-fullfile-x86-glb.exe /norestart |
| For Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions):\ Office2007-kb2433089-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 2433089 |
| 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:
- Oleksandr Mirosh, working with TippingPoint's Zero Day Initiative, for reporting the Malformed Request Code Execution Vulnerability (CVE-2010-3964)
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 (December 14, 2010): Bulletin published.
Built at 2014-04-18T13:49:36Z-07:00