Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

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

SoftwareComponentMaximum Security ImpactAggregate Severity RatingBulletins Replaced By This Update
Windows Server 2003
Windows Server 2003 Service Pack 1Microsoft Windows SharePoint Services 3.0
(KB934525)
Elevation of PrivilegeImportantNone
Windows Server 2003 Service Pack 2Microsoft Windows SharePoint Services 3.0
(KB934525)
Elevation of PrivilegeImportantNone
Windows Server 2003 x64 EditionMicrosoft Windows SharePoint Services 3.0
(KB934525)
Elevation of PrivilegeImportantNone
Windows Server 2003 x64 Edition Service Pack 2Microsoft Windows SharePoint Services 3.0
(KB934525)
Elevation of PrivilegeImportantNone
Microsoft Office SharePoint Server 2007
Microsoft Office SharePoint Server 2007
(KB937832)
Elevation of PrivilegeImportantNone
Microsoft Office SharePoint Server 2007 x64 Edition
(KB937832)
Elevation of PrivilegeImportantNone

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

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

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

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.

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

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.

SoftwareSMS 2.0SMS 2003
Microsoft Windows SharePoint Services 3.0 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2NoYes
Microsoft Windows SharePoint Services 3.0 on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2NoYes
Microsoft Office SharePoint Server 2007NoYes

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.

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 PacksThe update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionFor 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 fileKB934525.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredIn 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.
HotpatchingNot applicable
Removal InformationNot applicable
File InformationSee the next subsection, File Information, for the full file manifest
Registry Key VerificationNot 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 NameVersionDateTimeSize
Configupddl.sql27-Jun-200705:30138
Configdb.sql27-Jun-200706:1663,050
Configup.sql27-Jun-200705:3046,283
Dbghelp1.dll6.6.7.521-Feb-200711:141,030,144
schema.xml15-Mar-200712:47357,595
Dwdcw20.dll12.0.4518.101427-Oct-200609:48439,568
Imnidle.png02-May-200702:07635
Imnidlebusy.png02-May-200702:07631
Imnidlebusyoof.png02-May-200702:07646
Imnidleoof.png02-May-200702:07654
Imnon.png02-May-200702:07647
Imnonoof.png02-May-200702:07652
Mssdmn.exe12.0.6031.500020-Jul-200702:00282,496
Mssph.dll12.0.6037.500029-Aug-200714:21693592
Mssrch.dll12.0.6028.500027-Jun-200710:552,052,960
Offfilt.dll2006.523.6035.500018-Aug-200723:40203,128
Onetnative.dll12.0.4518.101427-Oct-200609:21353,608
Onetutil.dll12.0.6039.500013-Sep-200700:131,983,528
Owssvr.dll_000112.0.6039.500013-Sep-200700:593,011112
Owstimer.exe12.0.6036.500022-Aug-200713:1958,232
Psconfig.exe12.0.6023.500024-May-200712:16579,008
Psconfigui.exe12.0.6023.500024-May-200712:16824,768
Query9.dll12.0.6021.500011-May-200713:1184,824
Schema.xml15-Mar-200712:47354,280
Schema.xml15-Mar-200712:47151,688
Schema.xml15-Mar-200712:4784,704
Microsoft.SharePoint.Search.dll12.0.6025.500007-Jun-200701:351,325,960
Microsoft.SharePoint.Search.dll12.0.6025.500007-Jun-200701:351,325,960
SIGCONFIGDB.CER27-Jun-200706:16689
SIGCONFIGDB.DLL27-Jun-200706:1611,624
SIGCONFIGDB.SQL27-Jun-200706:1641,290
SIGSEARCHDB.CER27-Jun-200710:55689
SIGSEARCHDB.DLL27-Jun-200710:5511,624
SIGSEARCHDB.SQL27-Jun-200710:55150,788
Sigstore.cer29-Aug-200713:52689
Sigstore.dll01-Sep-200709:4811,616
Sigstore.sql29-Aug-200713:52394,870
Spwriter.exe12.0.6036.500022-Aug-200713:1938,272
Store.sql29-Aug-200713:522,660362
Storeup.sql29-Aug-200713:342,586286
Storeupddl.sql27-Jun-200705:30138
Stsadm.exe12.0.6036.500022-aug-200713:19521640
Microsoft.SharePoint.ApplicationPages.dll12.0.6039.500013-Sep-200701:00627784
Microsoft.SharePoint.Library.dll12.0.6036.500012-Sep-200704:24132,136
Microsoft.SharePoint.dll12.0.6039.500013-Sep-200701:009,294888
Microsoft.SharePoint.dll12.0.6039.500013-Sep-200701:009,294888
Microsoft.SharePoint.intl.dll12.0.6028.500027-Jun-200706:16464,256
Stssoap.dll12.0.6028.500027-Jun-200706:16312,704
Stswel.dll12.0.6039.500013-Sep-20071:001,928,232
setup.exe12.0.6022.500017-May-200719:02442,240
Timezone.xml22-Aug-200712:4238437
Tquery.dll12.0.6021.500011-May-200713:112,302,304
Wrapinst.exe12.0.6022.500017-May-200718:3150,560
SEARCHDB.SQL27-Jun-200710:55400,396
SEARCHDBUPGRADE.SQL27-Jun-200710:31310,744
Wss.xsd20-Mar-200711:3472,277
Microsoft.SharePoint.AdministrationOperation.dll12.0.6017.500011-Jul-200718:18472,448
Wsssetup.dll12.0.6022.500017-May-200719:036,783,344

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

File NameVersionDateTimeSize
Cfgupddl.sql27-Jun-200705:30138
Configdb.sql27-Jun-200706:1663,050
Configup.sql27-Jun-200705:3046,283
Dbghelp1.dll6.6.7.521-Feb-200711:141,319,936
DMSLSTSCHEMA_XML15-Mar-200712:47357,595
Dwdcw20.dll12.0.4518.101427-Oct-200609:471,079,568
Imnidle.png02-May-200702:07635
Imnidlebusy.png02-May-200702:07631
Imnidlebusyoof.png02-May-200702:07646
Imnidleoof.png02-May-200702:07654
Imnon.png02-May-200702:07647
Imnonoof.png02-May-200702:07652
Mssdmn.exe12.0.6028.500027-Jun-200710:55810,368
Mssph.dll_0001.x6412.0.6028.500027-Jun-200710:551,932,632
Mssrch.dll_0001.x6412.0.6028.500027-Jun-200710:554,721,504
Offfilt.dll_0002.x642006.523.6023.500023-May-200716:45392,568
Onetnative.dll12.0.4518.101427-Oct-200609:20951,112
Onetutil.dll12.0.6039.500011-Jul-200707:313,388,808
Owssvr.dll_000112.0.6039.500011-Jul-200708:455,129,600
Owstimer.exe_000112.0.6023.500024-May-200712:3393,048
Psconfig.exe12.0.6023.500024-May-200712:33579,008
Psconfigui.exe12.0.6023.500024-May-200712:33824,768
Query9x.dll_0002.x6412.0.6021.500011-May-200713:09223,576
Schema.xml_doclib15-Mar-200712:47354,280
Schema.xml_webtemp15-Mar-200712:47151,688
Schema.xml_wplib15-Mar-200712:4784,704
Searchom.dll_0003.x6412.0.6025.500007-Jun-200701:251,426,824
Searchom.dll_0005.x6412.0.6025.500007-Jun-200701:251,426,824
Sigcfg.cer27-Jun-200706:16689
Sigcfg.dll27-Jun-200706:1611,624
Sigcfg.sql27-Jun-200706:1641,290
Sigsdb.cer.x6427-Jun-200710:55689
Sigsdb.dll.x6427-Jun-200710:5511,624
Sigsdb.sql.x6427-Jun-200710:55150,788
Sigstore.cer27-Jun-200706:16689
Sigstore.dll27-Jun-200706:1611,616
Sigstore.sql27-Jun-200706:16394,870
Spwriter.exe_000112.0.6023.500024-May-200712:3359,776
Store.sql27-Jun-200706:162,659,370
Storeup.sql27-Jun-200705:302,585,294
Stoupddl.sql27-Jun-200705:30138
Stsadm.exe12.0.6028.500027-Jun-200706:01505,256
Stsap.dll12.0.6023.500024-May-200712:33628,136
Stslib.dll_000112.0.6023.500011-Jul-200718:18132,480
Stsom.dll12.0.6030.500011-Jul-200708:459,295,232
Stsom.dll_000112.0.6030.500011-Jul-200708:459,295,232
Stsomdr.dll12.0.6028.500027-Jun-200706:02464,256
Stssoap.dll12.0.6028.500027-Jun-200706:02312,704
Stswel.dll12.0.6030.500011-Jul-200708:453,313,024
Svrsetup.exe12.0.6022.500017-May-200719:02442,240
Timezone.xml06-Feb-200707:3137,742
Tquery.dll_0002.x6412.0.6021.500011-May-200713:094,666,720
Wrapinst.exe12.0.6022.500017-May-200718:3050,560
Wss.search.sql.x6427-Jun-200710:55400,396
Wss.search.up.sql.x6427-Jun-200710:31310,744
Wss.xsd20-Mar-200711:3472,277
Wssadmop.dll_000112.0.6017.500011-Jul-200718:18472,448
Wsssetup.dll12.0.6022.500017-May-200719:036,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.

Supported Security Update Installation Switches
SwitchDescription
/? or /helpDisplays usage dialog.
/passiveSpecifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel.
/quietSpecifies quiet mode, or suppresses prompts, when files are being extracted.
/norestartSuppresses restarting the system if the update requires a restart.
/forcerestartAutomatically restarts the system after applying the update, regardless of whether the update requires the restart.
/extractExtracts 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 PacksThe update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionFor 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 fileNot applicable
Further informationFor 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 requiredIn 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.
HotpatchingNot applicable
Removal InformationNot applicable
File InformationSee the next subsection, File Information, for the full file manifest.
Registry Key VerificationNot 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 NameVersionDateTimeSize
Chtbrkr.dll.x8612.0.6020.500005-May-200707:326,120,288
Mssdmn.exe.x8612.0.6031.500020-Jul-200702:00282,496
Mssph.dll.x8612.0.6031.500020-Jul-200702:00693,080
Notesph.dll.oss.x8612.0.6020.500005-May-200707:33836,504
Pkmexsph.dll_0001.x8612.0.6013.500015-Mar-200713:07184,160
Srchipp.dll.x8612.0.6013.500016-Mar-200705:201,010,032
Mssrch.dll.x8612.0.6028.500027-Jun-200710:552,052,960
Portal.dll12.0.6026.500016-Jun-200701:426,399,392
Query9x.dll_0001.x8612.0.6021.500011-May-200713:1084,824
Searchom.dll.x8612.0.6031.500020-Jul-200702:007,923,600
Searchom.dll_0001.x8612.0.6031.500020-Jul-200702:007,923,600
Sharepointpub_gac.dll12.0.6034.500008-Aug-200710:533,614,112
Tquery.dll.x8612.0.6021.500011-May-200713:102,302,304
Microsoft.sharepoint.publishing.dll_isapi12.0.6034.500008-Aug-200710:533,614,112
Portal.dll12.0.6026.500016-Jun-200701:426,399,392
Portal.dll_00112.0.6026.500016-Jun-200701:426,399,392
Profilesrp.sql06-Dec-200613:18547,229
Profilup.sql06-Dec-200613:18614,904
Reportcenterdoclibschema_xml15-Mar-200712:47354,280
Schema.xml_pubfeap15-Mar-200712:47354,280
Sharepointpub.dll12.0.6034.500008-Aug-200710:533,614,112
Sharepointpub_gac.dll12.0.6034.500008-Aug-200710:533,614,112
Ssosrv.exe_000112.0.6010.500026-Feb-200716:01390,024
Upgrade.dll_00112.0.6030.500011-Jul-200708:44787,872

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

File NameVersionDateTimeSize
Chtbrkr.dll.x6412.0.6020.500005-May-200713:206,133,088
Mssdmn.exe.x6412.0.6031.500020-Jul-200701:58810,368
Mssph.dll.x6412.0.6031.500020-Jul-200701:581,933,144
Pkmexsph.dll_0001.x6412.0.6013.500015-Mar-200713:06652,128
Srchipp.dll.x6412.0.6013.500015-Mar-200709:222,071,408
Mssrch.dll.x6412.0.6028.500027-Jun-200710:554,721,504
Portal.dll12.0.6026.500016-Jun-200701:396,399,392
Query9x.dll_0001.x6412.0.6021.500011-May-200713:08223,576
Searchom.dll.x6412.0.6031.500020-Jul-200701:588,030,608
Searchom.dll_0001.x6412.0.6031.500020-Jul-200701:588,030,608
Sharepointpub_gac.dll12.0.6034.500008-Aug-200710:393,614,112
Tquery.dll.x6412.0.6021.500011-May-200713:084,666,720
Microsoft.sharepoint.publishing.dll_isapi12.0.6034.500008-Aug-200710:393,614,112
Portal.dll12.0.6026.500016-Jun-200701:396,399,392
Portal.dll_00112.0.6026.500016-Jun-200701:396,399,392
Profilesrp.sql06-Dec-200613:18547,229
Profilup.sql06-Dec-200613:18614,904
Reportcenterdoclibschema_xml15-Mar-200712:47354,280
Schema.xml_pubfeap15-Mar-200712:47354,280
Sharepointpub.dll12.0.6034.500008-Aug-200710:393,614,112
Sharepointpub_gac.dll12.0.6034.500008-Aug-200710:393,614,112
Ssosrv.exe_000112.0.6010.500023-Feb-200716:30699,272
Upgrade.dll_00112.0.6030.500011-Jul-200708:44787,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.

Supported Security Update Installation Switches
SwitchDescription
/? or /helpDisplays usage dialog.
/passiveSpecifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel.
/quietSpecifies quiet mode, or suppresses prompts, when files are being extracted.
/norestartSuppresses restarting the system if the update requires a restart.
/forcerestartAutomatically restarts the system after applying the update, regardless of whether the update requires the restart.
/extractExtracts 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-16T02:39:51Z-07:00

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.