Security Bulletin

Microsoft Security Bulletin MS07-059 - Important

Vulnerability in Windows SharePoint Services 3.0 and Office SharePoint Server 2007 Could Result in Elevation of Privilege Within the SharePoint Site (942017)

Published: October 09, 2007

Version: 1.0

General Information

Executive Summary

This security update resolves a publicly reported vulnerability in Microsoft Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007. The vulnerability could allow an attacker to run arbitrary script that could result in elevation of privilege within the SharePoint site, as opposed to elevation of privilege within the workstation or server environment. The vulnerability could also allow an attacker to run arbitrary script to modify a user’s cache, resulting in information disclosure at the workstation.

The security update is rated important for Microsoft SharePoint Services 3.0 in supported editions of Microsoft Windows Server 2003 and for supported editions of Microsoft Office SharePoint Server 2007.

The security update addresses the vulnerability by modifying the way that Microsoft Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007 validate URL-encoded requests.

Recommendation. Microsoft recommends that customers apply the update at the earliest opportunity.

Known Issues. Microsoft Knowledge Base Article 942017 documents currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues.

Affected and Non-Affected Software

The software listed here 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 Component Maximum Security Impact Aggregate Severity Rating Bulletins Replaced By This Update
Windows Server 2003
Windows Server 2003 Service Pack 1 Microsoft Windows SharePoint Services 3.0
(KB934525)
Elevation of Privilege Important None
Windows Server 2003 Service Pack 2 Microsoft Windows SharePoint Services 3.0
(KB934525)
Elevation of Privilege Important None
Windows Server 2003 x64 Edition Microsoft Windows SharePoint Services 3.0
(KB934525)
Elevation of Privilege Important None
Windows Server 2003 x64 Edition Service Pack 2 Microsoft Windows SharePoint Services 3.0
(KB934525)
Elevation of Privilege Important None
Microsoft Office SharePoint Server 2007
Microsoft Office SharePoint Server 2007
(KB937832)
Elevation of Privilege Important None
Microsoft Office SharePoint Server 2007 x64 Edition
(KB937832)
Elevation of Privilege Important None

What are the known issues that customers may experience when they install this security update?
Microsoft Knowledge Base Article 942017 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues.

What is the difference between Microsoft Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007?
Windows SharePoint Services, a technology in Windows Server 2003, 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. Office SharePoint Server 2007 is an integrated suite of server capabilities built on top of Windows SharePoint Services. Office SharePoint Server 2007 provides additional content management and enterprise search.

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 KB934525 update. For systems with Microsoft Office SharePoint Server 2007 installed, you will need to apply both the KB934525 and KB937832 updates. There is no configuration where you can only have Microsoft Office SharePoint Server 2007 and not Microsoft Windows SharePoint Services 3.0. For more information, see the “Detection and Deployment Tools and Guidance” subsection under the section, Update Information.

Does this update contain any changes to functionality?
Yes. Besides the changes that are listed in the Vulnerability Details section of this bulletin, there are also changes not related to security. This update includes the following changes to functionality:

Why does this update contain functionality changes that are non-security related?
All SharePoint updates are cumulative, meaning security updates released may include functionality changes that have yet to be released in the next scheduled servicing method, such as a service pack.

I am using an older version of the software discussed in this security bulletin. What should I do?
Theaffected software listed in this bulletin has been tested to determine which versions are affected. Other versions are past their support life cycle. To determine the support life cycle for your product and version, visit Microsoft Support Lifecycle.

It should be a priority for customers who have older versions of the software to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.

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, 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 Windows Operating System Product Support Lifecycle FAQ.

Vulnerability Information

Severity Ratings and Vulnerability Identifiers

Affected Software SharePoint Scripting Vulnerability – CVE-2007-2581 Aggregate Severity Rating
Microsoft Windows SharePoint Services 3.0 Elevation of Privilege Important
Microsoft Office SharePoint Server 2007 Elevation of Privilege Important

SharePoint Scripting Vulnerability - CVE-2007-2581

This is a scripting vulnerability in Microsoft Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007. The vulnerability could allow an attacker to run arbitrary script that can result in elevation of privilege within the SharePoint site, as opposed to elevation of privilege within the workstation or server environment. The vulnerability could also allow an attacker to run arbitrary script to modify a user’s cache, resulting in information disclosure at the workstation. However, user interaction is required to exploit this vulnerability.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2007-2581.

Mitigating Factors for SharePoint Scripting Vulnerability - CVE-2007-2581

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:

  • In a Web-based attack scenario, Web sites that accept or host user-provided content, or compromised Web sites and advertisement servers could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that contains a specially-crafted URL with embedded Javascript.
  • In the information disclosure scenario, clients that have the advanced Internet option, Do not save encrypted pages to disk, turned on in Internet Explorer would not be at risk from any attempts to put spoofed content into the client cache if the clients accessed SharePoint site through the Secure Sockets Layer (SSL) protocol.

Workarounds for SharePoint Scripting Vulnerability - CVE-2007-2581

Microsoft has not identified any workarounds for this vulnerability.

FAQ for SharePoint Scripting Vulnerability - CVE-2007-2581

What is the scope of the vulnerability?
This is a scripting vulnerability in Microsoft Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007. The vulnerability could allow an attacker to run arbitrary script that can result in elevation of privilege within the SharePoint site, as opposed to elevation of privilege within the workstation or server environment. The vulnerability could also allow an attacker to run arbitrary script to modify a user’s cache, resulting in information disclosure at the workstation. However, user interaction is required to exploit this vulnerability.

What causes the vulnerability?
Both Microsoft Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007 do not sufficiently validate URL-encoded requests to ensure that the requests do not contain script code.

What are SharePoint Services?
Windows SharePoint Services, a technology in Windows Server 2003, provides a platform for collaboration 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. Office SharePoint Server 2007 is an integrated suite of server capabilities built on top of Windows SharePoint Services.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could gain the same user rights on the SharePoint site as the logged-on user. Users whose accounts are configured to have fewer user rights on the SharePoint site could be less impacted than users who operate with administrative user rights on the SharePoint site.

An attacker could also run arbitrary script to modify a user’s cache by displaying spoofed responses to users, or by redirecting server responses to the attacker. This results in information disclosure at the workstation.

How could an attacker exploit the vulnerability?
In the elevation of privilege scenario, an attacker could convince a user to click a specially crafted link, in an e-mail message or in a Web site, that contained script. Once the user clicks the link, the browser would run the script to elevate the attacker to the same privilege or higher as the logged-on user on the SharePoint site.

In the spoofing scenario, an attacker could also create a specially crafted link to redirect the user to another specially crafted Web site, or to capture confidential information within the browser cache.

What systems are primarily at risk from the vulnerability?
Systems that are running Microsoft Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007 are primarily at risk of attacks resulting in elevation of privilege. Workstations where users are accessing a vulnerable SharePoint site are at risk of attacks resulting in information disclosure.

What does the update do?
The security update addresses the vulnerability by modifying the way that Microsoft Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007 validate URL-encoded requests.

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 numberCVE-2007-2581.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had seen examples of proof of concept code published publicly but 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

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 at the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch."

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 has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, the Microsoft Baseline Security Analyzer (MBSA), Microsoft Systems Management Server (SMS), and the Extended Security Update Inventory Tool. For more information, see Microsoft Knowledge Base Article 910723.

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 Web site.

The following table provides the MBSA detection summary for this security update.

Software MBSA 1.2.1 MBSA 2.0.1
Microsoft SharePoint Services 3.0 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 No Yes
Microsoft Windows SharePoint Services 3.0 on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 No Yes
Microsoft Office SharePoint Server 2007 No Yes

Note for Windows Vista Microsoft does not support installing MBSA 2.0.1 on systems that run Windows Vista, but you may install MBSA 2.0.1 on a supported operating system and then scan the Windows Vista-based system remotely. For additional information about MBSA support for Windows Vista, visit the MBSA Web site. See also Microsoft Knowledge Base Article 931943: Microsoft Baseline Security Analyzer (MBSA) support for Windows Vista.

For more information about MBSA, visit the MBSA Web site. For more information about the software that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.

Windows Server Update Services

By using Windows Server Update Services (WSUS), administrators can deploy the latest Important updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 to Windows 2000 and later operating systems. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.

Systems Management Server

The following table provides the SMS detection and deployment summary for this security update.

Software SMS 2.0 SMS 2003
Microsoft Windows SharePoint Services 3.0 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 No Yes
Microsoft Windows SharePoint Services 3.0 on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 No Yes
Microsoft Office SharePoint Server 2007 No Yes

For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about SUIT, visit the following Microsoft Web site. For more information about the limitations of SUIT, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

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, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

For more information about SMS, visit the SMS Web site.

Note If you have used an Administrative Installation Point (AIP) for deploying Office 2000, 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.

Security Update Deployment

Affected Software

For information about the specific security update for your affected software, click the appropriate link:

Windows Server 2003 (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 Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2: wssv3-kb934525-fullfile-x86-glb /quiet
For Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: wssv3-kb934525-fullfile-x64-glb /quiet
Update log file KB934525.log
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required In most cases, this update does not require a restart. If the required files are being used, this update will require a 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 Not applicable
File Information See the next subsection, File Information, for the full file manifest
Registry Key Verification Not applicable

File Information

The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

For all supported 32-bit editions of Windows Server 2003:

File Name Version Date Time Size
Configupddl.sql 27-Jun-2007 05:30 138
Configdb.sql 27-Jun-2007 06:16 63,050
Configup.sql 27-Jun-2007 05:30 46,283
Dbghelp1.dll 6.6.7.5 21-Feb-2007 11:14 1,030,144
schema.xml 15-Mar-2007 12:47 357,595
Dwdcw20.dll 12.0.4518.1014 27-Oct-2006 09:48 439,568
Imnidle.png 02-May-2007 02:07 635
Imnidlebusy.png 02-May-2007 02:07 631
Imnidlebusyoof.png 02-May-2007 02:07 646
Imnidleoof.png 02-May-2007 02:07 654
Imnon.png 02-May-2007 02:07 647
Imnonoof.png 02-May-2007 02:07 652
Mssdmn.exe 12.0.6031.5000 20-Jul-2007 02:00 282,496
Mssph.dll 12.0.6037.5000 29-Aug-2007 14:21 693592
Mssrch.dll 12.0.6028.5000 27-Jun-2007 10:55 2,052,960
Offfilt.dll 2006.523.6035.5000 18-Aug-2007 23:40 203,128
Onetnative.dll 12.0.4518.1014 27-Oct-2006 09:21 353,608
Onetutil.dll 12.0.6039.5000 13-Sep-2007 00:13 1,983,528
Owssvr.dll_0001 12.0.6039.5000 13-Sep-2007 00:59 3,011112
Owstimer.exe 12.0.6036.5000 22-Aug-2007 13:19 58,232
Psconfig.exe 12.0.6023.5000 24-May-2007 12:16 579,008
Psconfigui.exe 12.0.6023.5000 24-May-2007 12:16 824,768
Query9.dll 12.0.6021.5000 11-May-2007 13:11 84,824
Schema.xml 15-Mar-2007 12:47 354,280
Schema.xml 15-Mar-2007 12:47 151,688
Schema.xml 15-Mar-2007 12:47 84,704
Microsoft.SharePoint.Search.dll 12.0.6025.5000 07-Jun-2007 01:35 1,325,960
Microsoft.SharePoint.Search.dll 12.0.6025.5000 07-Jun-2007 01:35 1,325,960
SIGCONFIGDB.CER 27-Jun-2007 06:16 689
SIGCONFIGDB.DLL 27-Jun-2007 06:16 11,624
SIGCONFIGDB.SQL 27-Jun-2007 06:16 41,290
SIGSEARCHDB.CER 27-Jun-2007 10:55 689
SIGSEARCHDB.DLL 27-Jun-2007 10:55 11,624
SIGSEARCHDB.SQL 27-Jun-2007 10:55 150,788
Sigstore.cer 29-Aug-2007 13:52 689
Sigstore.dll 01-Sep-2007 09:48 11,616
Sigstore.sql 29-Aug-2007 13:52 394,870
Spwriter.exe 12.0.6036.5000 22-Aug-2007 13:19 38,272
Store.sql 29-Aug-2007 13:52 2,660362
Storeup.sql 29-Aug-2007 13:34 2,586286
Storeupddl.sql 27-Jun-2007 05:30 138
Stsadm.exe 12.0.6036.5000 22-aug-2007 13:19 521640
Microsoft.SharePoint.ApplicationPages.dll 12.0.6039.5000 13-Sep-2007 01:00 627784
Microsoft.SharePoint.Library.dll 12.0.6036.5000 12-Sep-2007 04:24 132,136
Microsoft.SharePoint.dll 12.0.6039.5000 13-Sep-2007 01:00 9,294888
Microsoft.SharePoint.dll 12.0.6039.5000 13-Sep-2007 01:00 9,294888
Microsoft.SharePoint.intl.dll 12.0.6028.5000 27-Jun-2007 06:16 464,256
Stssoap.dll 12.0.6028.5000 27-Jun-2007 06:16 312,704
Stswel.dll 12.0.6039.5000 13-Sep-2007 1:00 1,928,232
setup.exe 12.0.6022.5000 17-May-2007 19:02 442,240
Timezone.xml 22-Aug-2007 12:42 38437
Tquery.dll 12.0.6021.5000 11-May-2007 13:11 2,302,304
Wrapinst.exe 12.0.6022.5000 17-May-2007 18:31 50,560
SEARCHDB.SQL 27-Jun-2007 10:55 400,396
SEARCHDBUPGRADE.SQL 27-Jun-2007 10:31 310,744
Wss.xsd 20-Mar-2007 11:34 72,277
Microsoft.SharePoint.AdministrationOperation.dll 12.0.6017.5000 11-Jul-2007 18:18 472,448
Wsssetup.dll 12.0.6022.5000 17-May-2007 19:03 6,783,344

For all supported x64-based editions of Windows Server 2003:

File Name Version Date Time Size
Cfgupddl.sql 27-Jun-2007 05:30 138
Configdb.sql 27-Jun-2007 06:16 63,050
Configup.sql 27-Jun-2007 05:30 46,283
Dbghelp1.dll 6.6.7.5 21-Feb-2007 11:14 1,319,936
DMSLSTSCHEMA_XML 15-Mar-2007 12:47 357,595
Dwdcw20.dll 12.0.4518.1014 27-Oct-2006 09:47 1,079,568
Imnidle.png 02-May-2007 02:07 635
Imnidlebusy.png 02-May-2007 02:07 631
Imnidlebusyoof.png 02-May-2007 02:07 646
Imnidleoof.png 02-May-2007 02:07 654
Imnon.png 02-May-2007 02:07 647
Imnonoof.png 02-May-2007 02:07 652
Mssdmn.exe 12.0.6028.5000 27-Jun-2007 10:55 810,368
Mssph.dll_0001.x64 12.0.6028.5000 27-Jun-2007 10:55 1,932,632
Mssrch.dll_0001.x64 12.0.6028.5000 27-Jun-2007 10:55 4,721,504
Offfilt.dll_0002.x64 2006.523.6023.5000 23-May-2007 16:45 392,568
Onetnative.dll 12.0.4518.1014 27-Oct-2006 09:20 951,112
Onetutil.dll 12.0.6039.5000 11-Jul-2007 07:31 3,388,808
Owssvr.dll_0001 12.0.6039.5000 11-Jul-2007 08:45 5,129,600
Owstimer.exe_0001 12.0.6023.5000 24-May-2007 12:33 93,048
Psconfig.exe 12.0.6023.5000 24-May-2007 12:33 579,008
Psconfigui.exe 12.0.6023.5000 24-May-2007 12:33 824,768
Query9x.dll_0002.x64 12.0.6021.5000 11-May-2007 13:09 223,576
Schema.xml_doclib 15-Mar-2007 12:47 354,280
Schema.xml_webtemp 15-Mar-2007 12:47 151,688
Schema.xml_wplib 15-Mar-2007 12:47 84,704
Searchom.dll_0003.x64 12.0.6025.5000 07-Jun-2007 01:25 1,426,824
Searchom.dll_0005.x64 12.0.6025.5000 07-Jun-2007 01:25 1,426,824
Sigcfg.cer 27-Jun-2007 06:16 689
Sigcfg.dll 27-Jun-2007 06:16 11,624
Sigcfg.sql 27-Jun-2007 06:16 41,290
Sigsdb.cer.x64 27-Jun-2007 10:55 689
Sigsdb.dll.x64 27-Jun-2007 10:55 11,624
Sigsdb.sql.x64 27-Jun-2007 10:55 150,788
Sigstore.cer 27-Jun-2007 06:16 689
Sigstore.dll 27-Jun-2007 06:16 11,616
Sigstore.sql 27-Jun-2007 06:16 394,870
Spwriter.exe_0001 12.0.6023.5000 24-May-2007 12:33 59,776
Store.sql 27-Jun-2007 06:16 2,659,370
Storeup.sql 27-Jun-2007 05:30 2,585,294
Stoupddl.sql 27-Jun-2007 05:30 138
Stsadm.exe 12.0.6028.5000 27-Jun-2007 06:01 505,256
Stsap.dll 12.0.6023.5000 24-May-2007 12:33 628,136
Stslib.dll_0001 12.0.6023.5000 11-Jul-2007 18:18 132,480
Stsom.dll 12.0.6030.5000 11-Jul-2007 08:45 9,295,232
Stsom.dll_0001 12.0.6030.5000 11-Jul-2007 08:45 9,295,232
Stsomdr.dll 12.0.6028.5000 27-Jun-2007 06:02 464,256
Stssoap.dll 12.0.6028.5000 27-Jun-2007 06:02 312,704
Stswel.dll 12.0.6030.5000 11-Jul-2007 08:45 3,313,024
Svrsetup.exe 12.0.6022.5000 17-May-2007 19:02 442,240
Timezone.xml 06-Feb-2007 07:31 37,742
Tquery.dll_0002.x64 12.0.6021.5000 11-May-2007 13:09 4,666,720
Wrapinst.exe 12.0.6022.5000 17-May-2007 18:30 50,560
Wss.search.sql.x64 27-Jun-2007 10:55 400,396
Wss.search.up.sql.x64 27-Jun-2007 10:31 310,744
Wss.xsd 20-Mar-2007 11:34 72,277
Wssadmop.dll_0001 12.0.6017.5000 11-Jul-2007 18:18 472,448
Wsssetup.dll 12.0.6022.5000 17-May-2007 19:03 6,783,344

Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

Deployment Information

Installing the Update

This security update requires that Windows Installer 3.1 or later be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version.

To install the required version of Windows Installer, visit the following Microsoft Web site:

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.

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 versions and editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.

    5. On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.

      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.

Microsoft Office 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 The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention For Microsoft Office SharePoint Server 2007: officeserver2007-kb937832-fullfile-x86-glb /passive
For Microsoft Office SharePoint Server 2007 x64 Edition: officeserver2007-kb937832-fullfile-x64-glb /passive
Update log file Not applicable
Further information For detection and deployment, see the subsection, Detection and Deployment Tools and Guidance. For features you can selectively install, see the Office Features subsection in this section.
Restart Requirement
Restart required In most cases, this update does not require a restart. If the required files are being used, this update will require a 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 Not applicable
File Information See the next subsection, File Information, for the full file manifest.
Registry Key Verification Not applicable

File Information

The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

For all supported 32-bit editions of Microsoft Office SharePoint Server 2007:

File Name Version Date Time Size
Chtbrkr.dll.x86 12.0.6020.5000 05-May-2007 07:32 6,120,288
Mssdmn.exe.x86 12.0.6031.5000 20-Jul-2007 02:00 282,496
Mssph.dll.x86 12.0.6031.5000 20-Jul-2007 02:00 693,080
Notesph.dll.oss.x86 12.0.6020.5000 05-May-2007 07:33 836,504
Pkmexsph.dll_0001.x86 12.0.6013.5000 15-Mar-2007 13:07 184,160
Srchipp.dll.x86 12.0.6013.5000 16-Mar-2007 05:20 1,010,032
Mssrch.dll.x86 12.0.6028.5000 27-Jun-2007 10:55 2,052,960
Portal.dll 12.0.6026.5000 16-Jun-2007 01:42 6,399,392
Query9x.dll_0001.x86 12.0.6021.5000 11-May-2007 13:10 84,824
Searchom.dll.x86 12.0.6031.5000 20-Jul-2007 02:00 7,923,600
Searchom.dll_0001.x86 12.0.6031.5000 20-Jul-2007 02:00 7,923,600
Sharepointpub_gac.dll 12.0.6034.5000 08-Aug-2007 10:53 3,614,112
Tquery.dll.x86 12.0.6021.5000 11-May-2007 13:10 2,302,304
Microsoft.sharepoint.publishing.dll_isapi 12.0.6034.5000 08-Aug-2007 10:53 3,614,112
Portal.dll 12.0.6026.5000 16-Jun-2007 01:42 6,399,392
Portal.dll_001 12.0.6026.5000 16-Jun-2007 01:42 6,399,392
Profilesrp.sql 06-Dec-2006 13:18 547,229
Profilup.sql 06-Dec-2006 13:18 614,904
Reportcenterdoclibschema_xml 15-Mar-2007 12:47 354,280
Schema.xml_pubfeap 15-Mar-2007 12:47 354,280
Sharepointpub.dll 12.0.6034.5000 08-Aug-2007 10:53 3,614,112
Sharepointpub_gac.dll 12.0.6034.5000 08-Aug-2007 10:53 3,614,112
Ssosrv.exe_0001 12.0.6010.5000 26-Feb-2007 16:01 390,024
Upgrade.dll_001 12.0.6030.5000 11-Jul-2007 08:44 787,872

For all supported x64-based editions of Microsoft Office SharePoint Server 2007:

File Name Version Date Time Size
Chtbrkr.dll.x64 12.0.6020.5000 05-May-2007 13:20 6,133,088
Mssdmn.exe.x64 12.0.6031.5000 20-Jul-2007 01:58 810,368
Mssph.dll.x64 12.0.6031.5000 20-Jul-2007 01:58 1,933,144
Pkmexsph.dll_0001.x64 12.0.6013.5000 15-Mar-2007 13:06 652,128
Srchipp.dll.x64 12.0.6013.5000 15-Mar-2007 09:22 2,071,408
Mssrch.dll.x64 12.0.6028.5000 27-Jun-2007 10:55 4,721,504
Portal.dll 12.0.6026.5000 16-Jun-2007 01:39 6,399,392
Query9x.dll_0001.x64 12.0.6021.5000 11-May-2007 13:08 223,576
Searchom.dll.x64 12.0.6031.5000 20-Jul-2007 01:58 8,030,608
Searchom.dll_0001.x64 12.0.6031.5000 20-Jul-2007 01:58 8,030,608
Sharepointpub_gac.dll 12.0.6034.5000 08-Aug-2007 10:39 3,614,112
Tquery.dll.x64 12.0.6021.5000 11-May-2007 13:08 4,666,720
Microsoft.sharepoint.publishing.dll_isapi 12.0.6034.5000 08-Aug-2007 10:39 3,614,112
Portal.dll 12.0.6026.5000 16-Jun-2007 01:39 6,399,392
Portal.dll_001 12.0.6026.5000 16-Jun-2007 01:39 6,399,392
Profilesrp.sql 06-Dec-2006 13:18 547,229
Profilup.sql 06-Dec-2006 13:18 614,904
Reportcenterdoclibschema_xml 15-Mar-2007 12:47 354,280
Schema.xml_pubfeap 15-Mar-2007 12:47 354,280
Sharepointpub.dll 12.0.6034.5000 08-Aug-2007 10:39 3,614,112
Sharepointpub_gac.dll 12.0.6034.5000 08-Aug-2007 10:39 3,614,112
Ssosrv.exe_0001 12.0.6010.5000 23-Feb-2007 16:30 699,272
Upgrade.dll_001 12.0.6030.5000 11-Jul-2007 08:44 787,872

Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

Deployment Information

Installing the Update

This security update requires that Windows Installer 3.1 or later be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version.

To install the required version of Windows Installer, visit the following Microsoft Web site:

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. For more information about the installer, visit the Microsoft TechNet Web site.

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 versions and editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.

    5. On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.

      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.

Other Information

Support

  • Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
  • 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 9, 2007): Bulletin published.

Built at 2014-04-18T13:49:36Z-07:00