Computer Security
[EN] securityvulns.ru no-pyccku


Related information

  Microsoft SharePoint Services crossite scripting

From:MICROSOFT <secure_(at)_microsoft.com>
Date:08.02.2005
Subject:Microsoft Security Bulletin MS05-006

Microsoft Security Bulletin MS05-006
Vulnerability in Windows SharePoint Services and SharePoint Team Services Could Allow Cross-Site Scripting and Spoofing Attacks (887981)

Issued: February 8, 2005
Version: 1.0

Summary
Who should read this document: Customers who use Microsoft Windows SharePoint Services or SharePoint Team Services from Microsoft

Impact of Vulnerability: Remote Code Execution

Maximum Severity Rating: Moderate

Recommendation: Customers should consider applying the security update.

Security Update Replacement: None

Caveats: None

Tested Software and Security Update Download Locations:

Affected Software:

• Windows SharePoint Services for Windows Server 2003 – Download the update (KB887981)

• SharePoint Team Services from Microsoft– Download the update (KB890829) – Download the full-file update (KB890829)


Non-Affected Software:

• Microsoft Windows Server 2003 for Itanium-based Systems

• SharePoint Portal Server 2003 (all versions)

• SharePoint Portal Server 2001 (all versions)


SharePoint Team Services Users: Office XP Service Pack 2 for Office XP Web Components and Office XP Service Pack 3 for SharePoint Team Services are both vulnerable to this issue. However the security update for Office XP Service Pack 2 for Office XP Web Components is provided only as part of the Office XP full-file security update. For more information, see the “Security Update Information” section.

The software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

Top of section
General Information
Executive Summary

Executive Summary:

This update resolves a newly-discovered, privately-reported vulnerability. A cross-site scripting and spoofing vulnerability exists in the affected software that could allow an attacker to convince a user to run a malicious script. The vulnerability is documented in the “Vulnerability Details” section of this bulletin.

An attacker who successfully exploited the vulnerability could modify Web browser caches and intermediate proxy server caches. Additionally, they could put spoofed content into those caches. An attacker may also be able to exploit the vulnerability to perform cross-site scripting attacks.

We recommend that customers consider applying the security update.

Severity Ratings and Vulnerability Identifiers:

Vulnerability Identifiers Impact of Vulnerability Windows SharePoint Services for Windows Server 2003 SharePoint Team Services from Microsoft
Cross-site Scripting and Spoofing Vulnerability - CAN-2005-0049
Remote Code Execution
Moderate
Moderate


This assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.

Top of section
Frequently asked questions (FAQ) related to this security update

Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?
Yes. MBSA will determine whether this update is required, but only for programs that MBSA supports. For example, MBSA does support SharePoint Team Services, and will detect whether the update is required for that program. MBSA supports the SharePoint Team Services from Microsoft update by using the Office Detection Tool and is therefore limited to local scans.

MBSA does not support Windows SharePoint Services, and will not detect whether the update is required for that program. However, Microsoft has developed a version of the Enterprise Update Scanning Tool (EST) that will help customers determine if the Windows SharePoint Services security update is required.

For detailed information about the programs that MBSA currently does not detect, see Microsoft Knowledge Base Article 306460. For more information about MBSA, visit the MBSA Web site.

Note After April 20, 2004, the Mssecure.xml file that is used by MBSA 1.1.1 and earlier versions is no longer being updated with new security bulletin data. Therefore, scans that are performed after that date by using MBSA 1.1.1 or earlier will be incomplete. All users should upgrade to MBSA 1.2 because it provides more accurate security update detection and supports additional products. Users can download MBSA 1.2.1 from the MBSA Web site. For more information about MBSA support, visit the following Microsoft Baseline Security Analyzer (MBSA) 1.2.1 Q&A Web site.

What is the Enterprise Update Scanning Tool (EST)?
As part of an ongoing commitment to provide detection tools for bulletin-class security updates, Microsoft delivers a stand-alone detection tool whenever the Microsoft Baseline Security Analyzer (MBSA) and the Office Detection Tool (ODT) cannot detect whether the update is required for an MSRC release cycle. This stand-alone tool is called the Enterprise Update Scanning Tool (EST) and is designed for enterprise administrators. When a version of the Enterprise Update Scanning Tool is created for a specific bulletin, customers can run the tool from a command line interface (CLI) and view the results of the XML output file. To help customers better utilize the tool, detailed documentation will be provided with the tool. There is also a version of the tool that offers an integrated experience for SMS administrators.

Can I use a version of the Enterprise Update Scanning Tool (EST) to determine whether this update is required?
Yes. Microsoft has created a version of the EST that will determine if you need to apply this update. For more information about the version of the EST being released this month, see the following Microsoft Web site. For more detailed deployment information about the version of the EST being released this month, see the following Microsoft Web site. There is also a version of this tool that SMS customers can obtain from the following Microsoft Web site. This tool may also be available for SMS customers from the SMS Web site.

Can I use Systems Management Server (SMS) to determine whether this update is required?
Yes. SMS can help detect and deploy this security update. SMS uses MBSA for detection; therefore, SMS has the same limitation listed earlier in this bulletin related to programs that MBSA does not detect. However, there is a version of the EST that SMS customers can obtain that offers an integrated experience for SMS administrators from the following Microsoft Web site.

For information about SMS, visit the SMS Web site. The Security Update Inventory Tool is required for detecting Microsoft Windows and other affected Microsoft products. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460. SMS can also use the Microsoft Office Inventory Tool to detect for required updates for Microsoft Office applications such as SharePoint Team Services.

Top of section
Vulnerability Details

Cross-site Scripting and Spoofing Vulnerability - CAN-2005-0049:

This is a cross-site scripting and spoofing vulnerability. The cross-site scripting vulnerability could allow an attacker to convince a user to run a malicious script. If this malicious script is run, it would execute in the security context of the user. Attempts to exploit this vulnerability require user interaction. This vulnerability could allow an attacker access to any data on the affected systems that was accessible to the individual user.

It may also be possible for an attacker to exploit this vulnerability to modify Web browser caches and intermediate proxy server caches, and put spoofed content in those caches.

Mitigating Factors for Cross-site Scripting and Spoofing Vulnerability - CAN-2005-0049:

Mitigating factors for cross-site scripting attacks:

• An attacker who successfully exploited the cross-site scripting aspect of this vulnerability would gain only the same permissions as the user.


Mitigating factors for putting spoofed content in a user’s Web browser cache:

• Clients who have turned on the Do not save encrypted pages to disk advanced Internet option in Internet Explorer would not be at risk from any attempts to put spoofed content into the client cache if they accessed their Web site through the Secure Sockets Layer (SSL) protocol.


Mitigating factors for putting spoofed content in an intermediate proxy server cache”

• Clients who use SSL-protected connections to access the affected Web sites would not be vulnerable to attempts to put spoofed content on intermediate proxy server caches. This is because SSL session data is encrypted and is not cached on intermediate proxy servers.

• If spoofed content is successfully put in an intermediate proxy server’s cache, it could be difficult for an attacker to predict which users would be served the spoofed cached content.

• An attacker must be able to log on the affected Web site to try to exploit this vulnerability. If you do not allow anonymous access to your Web site, only authenticated users could try to exploit this vulnerability.


Top of section
Workarounds for Cross-site Scripting and Spoofing Vulnerability - CAN-2005-0049:

We have not identified any workarounds for this vulnerability.

Top of section
FAQ for Cross-site Scripting and Spoofing Vulnerability - CAN-2005-0049:

What is the scope of the vulnerability?
This is a cross-site scripting and spoofing vulnerability. The cross-site scripting vulnerability could allow an attacker to convince a user to run a malicious script. If this malicious script is run, it would execute in the security context of the user. Attempts to exploit this vulnerability require user interaction. This vulnerability could allow an attacker access to any data on the affected systems that was accessible to the individual user.

It may also be possible for an attacker to exploit the vulnerability to modify Web browser caches and intermediate proxy server caches and to put spoofed content in those caches.

What causes the vulnerability?
The affected software does not completely validate input that is provided to a HTML redirection query before it sends this input to the browser.

What is Windows SharePoint Services for Windows Server 2003?
Windows SharePoint Services lets teams create Web sites for information sharing and document collaboration, benefits that help increase individual and team productivity. Available as a separate download, Windows SharePoint Services 2003 is a component of the Windows Server 2003 information worker infrastructure and provides team services and sites to Microsoft Office System and other desktop programs. It also serves as a platform for application development. For more information about Windows SharePoint Services, visit the following Microsoft Web site.

What is SharePoint Team Servicesfrom Microsoft?
SharePoint Team Services from Microsoft provides both Web publishing and collaboration features to make communicating ideas and sharing information easier. SharePoint Team Services is a superset of Microsoft FrontPage Server Extensions 2002, and includes all the features that are available with the server extensions. Additionally, SharePoint Team Services contains new workgroup features that create a rich environment for Web publishing and team communication. By using SharePoint Team Services, administrators can create, author, and administer Web sites that help a team organize and advance on a project. For more information about SharePoint Team Services, visit the following Microsoft Web site. FrontPage Server Extensions 2002 are not vulnerable to this issue.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited the vulnerability could perform cross-site scripting attacks, display spoofed responses to users, or redirect server responses to another user.

How could an attacker exploit the vulnerability?
An attacker could create an e-mail message that is specially crafted to try to exploit this vulnerability. An attacker could exploit the vulnerability by sending this specially crafted e-mail message to a user of a server that is running an affected software application. An attacker could then persuade the user to click a link in the e-mail message.

It may also be possible to exploit the vulnerability to modify Web browser caches and intermediate proxy server caches and to put spoofed content in those caches.

Could the vulnerability be exploited over the Internet?
Yes. An attacker could try to exploit this vulnerability over the Internet.

What does the update do?
The update removes the vulnerability by modifying the way that the affected software validates input that is provided to an HTTP redirection query before it sends this input to the client.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft had not received any information indicating that this vulnerability had been publicly disclosed when this security bulletin was originally issued.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information indicating that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

Top of section
Top of section
Top of section
Security Update Information

Affected Software:

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

Windows SharePoint Services for Windows Server 2003

Prerequisites and Additional Update Details

Important: Before you install this update, make sure that the following requirement has been met:

• Windows SharePoint Services 2003 Service Pack 1 must be installed. For additional information about how to install Windows SharePoint Services Service Pack 1, visit the following Microsoft Web site.


Inclusion in Future Service Packs:

The fix for this issue will be included in a future service pack.

Restart Requirement

This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart."

Removal Information

After you install the update, you cannot remove it. To revert to an installation before the update was installed, you must remove the application, and then install it again from the original CD-ROM.

Top of section
Automated Client Installation Information

Windows Update Web Site

We recommend that you install this update by using the Windows Update Web site. The Windows Update Web site detects your particular installation and prompts you to install exactly what you must have to make sure that your installation is completely up-to-date.

Top of section
Manual Client Installation Information

For detailed information about how to manually install this update please review the following section.

Installation Information

The security update supports the following setup switches:

  /Q Specifies quiet mode, or suppresses prompts, when files are being extracted.

  /Q:U Specifies user-quiet mode, which presents some dialog boxes to the user.

  /Q:A Specifies administrator-quiet mode, which does not present any dialog boxes to the user.

  /T: <full path> Specifies the target folder for extracting files.

  /C Extracts the files without installing them. If /T: path is not specified, you are prompted for a target folder.

  /C: <Cmd> Override Install Command defined by author. Specifies the path and name of the setup .inf or .exe file.

  /R:N Never restarts the computer after installation.

  /R:I Prompts the user to restart the computer if a restart is required, except when used with /Q:A.

  /R:A Always restarts the computer after installation.

  /R:S Restarts the computer after installation without prompting the user.

  /N:V No version checking - Install the program over any earlier version.

Note These switches do not necessarily work with all updates. If a switch is not available, that functionality is required for the correct installation of the update. Also, using the /N:V switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should contact your support professional to understand why it could not install.

For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147.

Client Deployment Information

1.
Download this security update.

2.
Click Save this program to disk, and then click OK.

3.
Click Save.

4.
Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file.

5.
If you are prompted to install the update, click Yes.

6.
Click Yes to accept the License Agreement.

7.
Insert your original source CD-ROM if you are prompted to do so, and then click OK.

8.
When you receive a message that states the installation was successful, click OK.


Note If the security update is already installed on your computer, you receive the following error message: This update has already been applied or is included in an update that has already been applied.

Client Installation File Information

The English version of this 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.

Windows SharePoint Services for Windows Server 2003:

File Name Version Date Time Size
Microsoft_sharepoint_dsp_xmlurl.dll
11.0.6407.0
01-Oct-2004
03:01
84,728

Onetutil.dll
11.0.6411.0
11-Nov-2004
04:47
1,410,248

Owssvr.dll_0001
Installed Name: Owssvr.dll
11.0.6411.0
11-Nov-2004
04:50
2,222,784

Sqmsto.dll
11.0.6411.0
11-Nov-2004
04:36
2,255,560

Sqmstoup.dll
11.0.6411.0
11-Nov-2004
04:36
2,190,024

Store.sql

04-Nov-2004
05:31
1,141,841

Storeup.sql

04-Nov-2004
05:31
1,108,009

Stsadm.exe
11.0.6409.0
16-Oct-2004
18:39
137,920

Stsap.dll
11.0.6409.0
16-Oct-2004
18:39
248,576

Stslib.dll_0001
Installed Name: Microsoft.SharePoint.Library.dll
11.0.6402.0
27-Aug-2004
01:03
92,912

Stsom.dll
Installed Name: Microsoft.SharePoint.dll
11.0.6411.0
11-Nov-2004
04:50
1,501,920

Stsom.dll_0001
Installed Name: Microsoft.SharePoint.dll
11.0.6411.0
11-Nov-2004
04:50
1,501,920

Stswel.dll
11.0.6411.0
11-Nov-2004
04:50
1,055,424



Verifying that the Update Has Been Applied

• File Version Verification

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. 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 computer 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.



Top of section
Top of section

SharePoint Team Services from Microsoft

Prerequisites and Additional Update Details

Important: Before you install this update, make sure that the following requirements have been met:

• Microsoft Windows Installer 2.0 must be installed. Microsoft Windows Server 2003, Windows XP and Microsoft Windows 2000 Service Pack 3 (SP3) include Windows Installer 2.0 or a later version. To install the latest version of the Windows Installer, visit one of the following Microsoft Web sites:

Windows Installer 2.0 for Windows 2000 and Windows NT 4.0

• Office XP Service Pack 3 (SP3) for SharePoint Team Services must be installed. Before you install this update, install Office XP Service Pack 3 (SP3) for SharePoint Team Services. For additional information about how to install Office XP Service Pack 3 (SP3) for SharePoint Team Services, see Microsoft Knowledge Base Article 839025. The full-file update can also be installed on systems that are running Office XP Service Pack 2 for Office Web Components or Office XP Service Pack 3 for SharePoint Team Services.


Inclusion in Future Service Packs:

The fix for this issue will be included in a future service pack.

Restart Requirement

This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart."

If you install the update by using the Office Update Web site you may need to restart the affected system. To avoid the restart requirement follow the steps in the “Office Update Web Site” section of this bulletin.

Removal Information

After you install the update, you cannot remove it. To revert to an installation before the update was installed, you must remove the application, and then install it again from the original CD-ROM.

Top of section
Automated Client Installation Information

Office Update Web Site

We recommend that you install the client updates by using the Office Update Web site. The Office Update Web site detects your particular installation and prompts you to install exactly what you must have to make sure that your installation is completely up-to-date.

To have the Office Update Web site detect the required updates that you must install on your computer, visit the Office Update Web site, and then click Check for Updates. After detection is complete, you will receive a list of recommended updates for your approval. Click Start Installation to complete the process.

Note When you install the update by using the Office Update Web site you will need to restart the affected system unless you stop both the iisreset service and the sptimer service before installing the update. To avoid the server restart requirement, follow these steps:

1.
On the Windows Start menu, click Run.

2.
In the Open box, type “CMD” (without the quotes) and then click OK.

3.
At the command prompt, follow these steps:

• Type “net stop iisadmin /y” (without the quotes) and press ENTER.

• Type “net stop sptimer” (without the quotes) and press ENTER.


4.
Install the update by using the Office Update Web site

5.
At the command prompt, follow these steps:

• Type “net start w3svc” (without the quotes) and press ENTER.

• Type “net start sptimer” (without the quotes) and press ENTER.


6.
Type “Exit” (without the quotes) to return to Windows.


Top of section
Manual Client Installation Information

For detailed information about how to manually install this update please review the following section.

Installation Information

The security update supports the following setup switches:

  /Q Specifies quiet mode, or suppresses prompts, when files are being extracted.

  /Q:U Specifies user-quiet mode, which presents some dialog boxes to the user.

  /Q:A Specifies administrator-quiet mode, which does not present any dialog boxes to the user.

  /T: <full path> Specifies the target folder for extracting files.

  /C Extracts the files without installing them. If /T: path is not specified, you are prompted for a target folder.

  /C: <Cmd> Override Install Command defined by author. Specifies the path and name of the setup .inf or .exe file.

  /R:N Never restarts the computer after installation.

  /R:I Prompts the user to restart the computer if a restart is required, except when used with /Q:A.

  /R:A Always restarts the computer after installation.

  /R:S Restarts the computer after installation without prompting the user.

  /N:V No version checking - Install the program over any earlier version.

Note These switches do not necessarily work with all updates. If a switch is not available, that functionality is required for the correct installation of the update. Also, using the /N:V switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should contact your support professional to understand why it could not install.

For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147.

Client Deployment Information

1.
Download the client version of this security update.

Or download the full-file version of this security update.

2.
Click Save this program to disk, and then click OK.

3.
Click Save.

4.
Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file.

5.
If you are prompted to install the update, click Yes.

6.
Click Yes to accept the License Agreement.

7.
Insert your original source CD-ROM if you are prompted to do so, and then click OK.

8.
When you receive a message that states the installation was successful, click OK.


Note If the security update is already installed on your computer, you receive the following error message: This update has already been applied or is included in an update that has already been applied.

Client and Full-File Installation File Information

The English version of this 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.

SharePoint Team Services from Microsoft (client and full-file update):

File Name Version Date Time Size
Fp5amsft.dll
10.0.6738.0
29-Oct-2004
22:38
142,024

Fp5autl.dll
10.0.6711.0
08-Apr-2004
02:24
944,840

Fp5awec.dll
10.0.6711.0
08-Apr-2004
02:24
608,968

Fp5awel.dll
10.0.6738.0
29-Oct-2004
22:38
1,379,016

Fpcutl.dll
10.0.6738.0
29-Oct-2004
22:38
1,170,112

Fpeditax.dll
10.0.6714.0
26-Jan-2005
22:21
4,258,504

Fpmmc.dll
10.0.6738.0
29-Oct-2004
22:38
400,064

Owssvr.dll
10.0.6738.0
29-Oct-2004
22:38
834,240

Owstimer.exe
10.0.6711.0
08-Apr-2004
02:24
346,824



Verifying that the Update Has Been Applied

• Microsoft Baseline Security Analyzer

To verify that a security update is installed on an affected system you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool, which allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.

• File Version Verification

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. 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 computer 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.



Top of section
Top of section

Top of section
Obtaining Other Security Updates:

Updates for other security issues are available at the following locations:

• Security updates are available in the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch."

• Updates for consumer platforms are available at the Windows Update Web site.


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.


Security Resources:

• The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.

• Microsoft Software Update Services

• Microsoft Baseline Security Analyzer (MBSA)

• Windows Update

• Windows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.

• Office Update


Software Update Services:

By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.

For more information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site.

Systems Management Server:

Microsoft Systems Management Server (SMS) delivers a highly-configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and can perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, visit the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site.

Note SMS uses the Microsoft Baseline Security Analyze, Microsoft Office Detection Tool, and the Enterprise Update Scanning Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.

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 (February 8, 2005): Bulletin published

About | Terms of use | Privacy Policy
© SecurityVulns, 3APA3A, Vladimir Dubrovin
Nizhny Novgorod