Export (0) Print
Expand All

Microsoft Security Bulletin MS06-017 - Moderate

Vulnerability in Microsoft FrontPage Server Extensions Could Allow Cross-Site Scripting (917627)

Published: April 11, 2006

Version: 1.0

Summary

Who should read this document: Customers who use Microsoft FrontPage Server Extensions 2002 or Microsoft SharePoint Team Services

Impact of Vulnerability: Remote Code Execution

Maximum Severity Rating: Moderate

Recommendation: Customers should consider applying the security update.

Security Update Replacement: This bulletin replaces a prior security update. See the frequently asked questions (FAQ) section of this bulletin for the complete list.

Caveats: Microsoft Knowledge Base Article 917627 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues. For more information, see Microsoft Knowledge Base Article 917627.

Tested Software and Security Update Download Locations:

Affected Software:

  • Microsoft FrontPage Server Extensions 2002 shipped on Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 – Download the update (KB908981)
  • Microsoft FrontPage Server Extensions 2002 shipped on Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems – Download the update (KB908981)
  • Microsoft FrontPage Server Extensions 2002 (x64 Edition) downloaded and installed on Microsoft Windows Server 2003 x64 Edition and Microsoft Windows XP Professional x64 Edition – Download the update (KB911831)
  • Microsoft FrontPage Server Extensions 2002 (x86 Editions) downloaded and installed on Microsoft Windows Server 2000 Service Pack 4, Microsoft Windows XP Service Pack 1, and Microsoft Windows XP Service Pack 2 – Download the update (KB911831)
  • Microsoft SharePoint Team Services – Download the update (KB911701)

Non-Affected Software:

  • Microsoft Windows SharePoint Services
  • Microsoft FrontPage 2002
  • Microsoft FrontPage Server Extensions 2000
  • Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME)

Note To determine what version of FrontPage Server Extensions that is installed on your system please see " How can I determine if I am running of FrontPage Server Extensions 2002 or SharePoint Team Services” in the FAQ section of this bulletin.

Note Review the FAQ section of this bulletin for information about why you may be prompted to install the SharePoint Team Services security update if you have Microsoft FrontPage 2002 installed.

Note The security updates for Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 also apply to Microsoft Windows Server 2003 R2.

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 Website.

General Information

Executive Summary:

This update resolves a newly-discovered, privately-reported vulnerability. The vulnerability is documented in the "Vulnerability Details" section of this bulletin.

If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

We recommend that customers consider applying the security update.

Severity Ratings and Vulnerability Identifiers:

Vulnerability IdentifiersImpact of VulnerabilityMicrosoft FrontPage Server Extensions 2002 shipped on Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1Microsoft FrontPage Server Extensions 2002 downloaded and installed on Microsoft Windows Server 2000 Service Pack 4, Microsoft Windows XP Service Pack 1, and Microsoft Windows XP Service Pack 2Microsoft SharePoint Team Services 2002
Cross-Site Scripting FrontPage Server Extensions Vulnerability - CVE-2006-0015Remote Code ExecutionModerateModerateModerate

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.

Note The severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows:

  • The Microsoft Windows Server 2003 R2 Systems severity rating is the same as the Windows Server 2003 severity rating.
  • The Microsoft Windows XP Professional x64 Edition severity rating is the same as the Windows XP Service Pack 2 severity rating.
  • The Microsoft Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.
  • The Microsoft Windows Server 2003 with SP1 for Itanium-based Systems severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.
  • The Microsoft Windows Server 2003 x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.

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

I am using SMS to deploy the security update for FrontPage Server Extensions 2002 when downloaded and installed on Microsoft Windows 2000 Service Pack 4, Microsoft XP Service Pack 1, or Microsoft XP Service Pack 2. Are there any issues that I need to be aware of?
Yes, there are unique issues with deployment that you need to be aware of for the Web downloaded Front Page Server Extensions 2002. For more information, see Microsoft Knowledge Base Article 917138.

Can I get the security update for FrontPage Server Extensions 2002 for Microsoft Windows 2000, Microsoft Windows XP, and Microsoft Windows Server 2003, x64 edition, from Microsoft Update (MU), Automatic Updates (AU), or Windows Software Update Services (WSUS)?|
No. The security update for FrontPage Server Extensions 2002 for Microsoft Windows 2000, Microsoft Windows XP, and Microsoft Windows Server 2003, x64 edition, will not be available via MU, AU, or WSUS. However, you will be able to use the Enterprise Scan Tool to detect whether or not any machines in your organization need this update. Please refer to Microsoft Knowledge Base Article 894193 for instructions on how to download and use the Enterprise Scan Tool. In addition, please read Microsoft Knowledge Base Article 917138 for instructions on how to deploy this specific security update using SMS.

I have FrontPage 2002 installed, but it is not listed in the affected software section. Why am I being offered the security update?
FrontPage 2002 is not vulnerable to the vulnerability. However, because FrontPage 2002 uses some of the updated files, the security update will be recommended through Office Update and through MBSA to customers who have FrontPage 2002 installed.

How can I determine if I am running FrontPage Server Extensions 2002 or SharePoint Team Services?
To determine the version of FrontPage Server Extensions that is installed on your computer, follow these steps.

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 fpadmdll.dll and then click Search.
  4. If you find the fpadmdll.dll file, you have either FrontPage Server Extensions 2002 installed or SharePoint Team Services installed.

To determine which of these programs you have installed, follow these steps:

  1. In Control Panel, open Add or Remove Programs.
  2. See if "Microsoft SharePoint" as appears in the list of installed software.

If a list entry called "Microsoft SharePoint" exists, then you do have SharePoint Team Services installed.

What updates does this release replace?
This security update replaces a prior security update. The security bulletin ID and affected operating systems are listed in the following table.

Bulletin IDMicrosoft FrontPage Server Extensions 2002 shipped on Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1Microsoft FrontPage Server Extensions 2002 downloaded and installed on Microsoft Windows Server 2000 Service Pack 4, Microsoft Windows XP Service Pack 1, and Microsoft Windows XP Service Pack 2Microsoft SharePoint Team Services 2002
MS03-051 Not ApplicableReplacedNot Applicable
MS05-006 Not ApplicableNot ApplicableReplaced

Can I use the Microsoft Baseline Security Analyzer (MBSA) 1.2.1 to determine whether this update is required?
Yes, MBSA 1.2.1 will support SharePoint Team Services for Local Scans only. MBSA uses an integrated version of the Office Detection Tool (ODT) which does not support remote scans of this issue. For more information about MBSA, visit the MBSA Website. For more information about MBSA support, visit the following Microsoft Baseline Security Analyzer 1.2 Q&A Website.

MBSA 1.2.1 does not support the detection of support Web downloadable FrontPage Server Extensions 2002. For more information about MBSA, visit the MBSA Website.

For more information about the programs that MBSA 1.2.1 currently does not detect, see Microsoft Knowledge Base Article 306460. However, Microsoft has developed a version of the Enterprise Scan Tool (EST) that will help customers determine whether the security updates provided in this security bulletin are required. For more information, see the "Can I use a version of the Enterprise Scan Tool (EST) to determine whether this update is required?" question in this section.

Can I use the Microsoft Baseline Security Analyzer (MBSA) 2.0 to determine whether this update is required?
Yes. MBSA 2.0 will determine whether this update is required for SharePoint Team Services. MBSA 2.0 can detect security updates for products that Microsoft Update supports. For more information about MBSA, visit the MBSA Website.

MBSA 2.0 does not currently support the detection of Web downloadable FrontPage Server Extensions. However, Microsoft has developed a version of the Enterprise Scan Tool (EST) that will help customers determine whether the security updates provided in this security bulletin are required. For more information, see the "Can I use a version of the Enterprise Scan Tool (EST) to determine whether this update is required?" question in this section. For more information about the programs that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.

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 Scan 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.
Note The Enterprise Scan Tool (EST) will only be able to detect not deploy for the Web downloaded Front Page Server Extensions 2002 on Windows Server 2000 Service Pack 4, Windows XP Service Pack 1, or Windows XP Service Pack 2.
Can I use a version of the Enterprise Scan Tool (EST) to determine whether this update is required?
Yes. Microsoft has created a version of the EST that will determine if you have to apply this update. For download links and more information about the version of the EST that is being released this month, visit the following Microsoft Web site. SMS customers should review the "Can I use Systems Management Server (SMS) to determine whether this update is required?" FAQ for more information about SMS and EST.

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. To obtain this version of the EST, visit the following Microsoft Web site.

Note If you are using SMS to deploy the security update for FrontPage Server Extensions 2002 when downloaded and installed on Microsoft Windows 2000 Service Pack 4, Microsoft XP Service Pack 1, or Microsoft XP Service Pack 2, see Microsoft Knowledge Base Article 917138 for more information.

SMS can use the SMS Software Update Services (SUS) Feature Pack to detect security updates. The SMS SUS Feature Pack includes the Security Update Inventory Tool (SUIT). For more information about the Security Update Inventory Tool, visit the following Microsoft Web site. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460.

The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect for required updates for Microsoft Office applications.

SMS can use the SMS 2003 Inventory Tool for Microsoft Updates 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 Inventory Tool for Microsoft Updates, visit the following Microsoft Web site.

SMS 2.0 and SMS 2003 customers who do not use the SMS 2003 Inventory Tool for Microsoft Updates must download and deploy an updated version of the Extended Security Update Inventory Tool to receive full detection and deployment for this update.

For more information about SMS, visit the SMS Website.

Cross-site Scripting FrontPage Server Extensions Vulnerability - CVE-2006-0015

The cross-site scripting vulnerability could allow an attacker to run client-side script on behalf of an FPSE user. The script could spoof content, disclose information, or take any action that the user could take on the affected web site. Attempts to exploit this vulnerability require user interaction. An attacker who successfully exploited this vulnerability against an administrator could take complete control of a Front Page Server Extensions 2002 server.

Mitigating Factors for Cross-site Scripting FrontPage Server Extensions Vulnerability - CVE-2006-0015:

  • By default, Microsoft Internet Information Services (IIS) 6.0 is not enabled on Microsoft Windows Server 2003.
  • By default, FrontPage Server Extensions are not enabled on Microsoft Windows Server 2003.
  • You are not vulnerable if you have installed Microsoft Internet Information Services (IIS) 5.0 on Windows Server 2000 Service Pack 4. You are also not vulnerable if you have installed Microsoft Internet Information Services (IIS) 5.1 on Windows XP Service Pack 1 or on Windows XP Service Pack2 and if you have the default installation of FrontPage Server Extensions 2000.
  • In a Web-based attack scenario, an attacker would have to know the name of the Front Page Server Extensions 2002 or SharePoint Team Services 2002 server to inject the malicious script. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site.
  • The vulnerability could not be exploited automatically through e-mail. For an attack to be successful, a user must click a Web link that is sent in an e-mail message.
  • An attacker who successfully exploited this vulnerability could gain the same rights as the user’s rights on the Front Page Server Extensions 2002 or SharePoint Team Services 2002 server. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

Workarounds for Cross-site Scripting FrontPage Server Extensions Vulnerability - CVE-2006-0015:

We have not identified any workarounds for this vulnerability.

FAQ for FrontPage Server Extensions Vulnerability - CVE-2006-0015:

What is the scope of the vulnerability?
This is a cross-site scripting vulnerability that 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.

The script could take any action on the user's behalf that the Web site is authorized to take. This could include monitoring the Web session and forwarding information to a third party, running other code on the user's system, and reading or writing cookies.

If a user has administrative user rights on the Front Page Server Extensions 2002 or SharePoint Team Services 2002 server, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

What causes the vulnerability?
A cross-site scripting (XSS) vulnerability is caused by the way that FrontPage Server Extensions handles parameter validation.

What are the FrontPage Server Extensions?
FrontPage Server Extensions is a set of tools that can be installed on a Web site. They allow authorized personnel to manage the server, add or change content, and perform other tasks. They also add functions that Web pages frequently use, such as search and forms support.

What is cross-site scripting?
Cross-site scripting (XSS) is a security vulnerability that could enable an attacker to "inject" code into a user's session with a Website. The attack involves Web servers that dynamically generate HTML pages. If these servers embed browser input in the dynamic pages that they send back to the browser, these servers can be manipulated to include content in the dynamic pages. This will allow malicious script to be executed. Web browsers may perpetuate this problem through their basic assumptions of "trusted" sites and their use of cookies to maintain persistent state with the Websites that they frequent. This attack does not modify Website content. Instead, it inserts new, malicious script that can execute at the browser level in the information context that is associated with a trusted server.

How does cross-site scripting work?
Web pages contain text and HTML markup. Text and HTML markup are generated by the server and are interpreted by the client. Servers that generate static pages have full control over the way that the client interprets the pages that the server sends. However, servers that generate dynamic pages do not have control over the way that the client interprets the servers’ output. If untrusted content is introduced into a dynamic page, neither the server nor the client has sufficient information to recognize that this action has occurred and to take protective measures.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited the vulnerability could perform actions on the behalf of the user on the Web site.

Who could 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.

In a Web-based attack scenario, an attacker would have to know the name of the Front Page Server Extensions 2002 or SharePoint Team Services 2002 server to be successful which the user has access to in order to inject the malicious script. An attacker would have no way to force users to visit a malicious Website. Instead, an attacker would have to persuade them to visit the Website, typically by getting them to click a link that takes them to the attacker's site.

What systems are primarily at risk from the vulnerability?
Workstations and servers that have Microsoft Internet Information Services (IIS), FrontPage Server Extensions 2002 or SharePoint Team Services installed are primarily at risk. Servers could be at more risk if users who do not have sufficient administrative permissions are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this.

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 FrontPage Server Extensions handles HTML validation.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure.

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

Affected Software:

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

Microsoft FrontPage Server Extensions 2002 included with Microsoft Windows Server 2003, Microsoft Windows Server 2003 Service Pack 1, Microsoft Windows Server 2003 for Itanium-based Systems, and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems

Prerequisites
This security update requires Windows Server 2003 or Windows Server 2003 Service Pack 1 running FrontPage Server Extensions 2002.

Note Users who have not installed FrontPage Server Extensions 2002 will not be able to install this update.

Inclusion in Future Service Packs:
The update for this issue will be included in future Service Pack or Update Rollup.

Installation Information

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/help Displays the command-line options
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed
/forcerestart Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart Display a dialog box prompting the local user to allow a restart
Special Options
/overwriteoem Overwrites OEM files without prompting
/nobackup Does not back up files needed for uninstall
/forceappsclose Forces other programs to close when the computer shuts down
/log: path Allows the redirection of installation log files
/integrate:path Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path] Extracts files without starting the Setup program
/ER Enables extended error reporting
/verbose Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

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 Update.exe installer, visit the Microsoft TechNet Website.

Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for Windows Server 2003:

Windowsserver2003-kb908981-x86-enu /quiet
Or
Windowsserver2003-kb908981-ia64-enu /quiet

Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB908981.log file for any failure messages when they use this switch.

To install the security update without forcing the system to restart, use the following command at a command prompt for Windows Server 2003:

Windowsserver2003-kb908981-x86-enu /norestart
Or
Windowsserver2003-kb908981-ia64-enu / norestart

For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Website. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Website. This security update will also be available through the Microsoft Update Website.

Restart Requirement

In some cases, this update does not require a restart. The installer stops IIS services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if files being updated are in use by some other service or application, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

To help reduce the chance that a reboot will be required, close all applications prior to installing the security update.

For more information about the reasons that you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.

Note If you are prompted to restart the computer, you will not be secure until you do so.

Removal Information

To remove this update, use the Add or Remove Programs tool in Control Panel.

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB908981$\Spuninst folder.

Supported Spuninst.exe Switches
SwitchDescription
/help Displays the command-line options
Setup Modes
/passive Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart Does not restart when installation has completed
/forcerestart Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x] Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart Display a dialog box prompting the local user to allow a restart
Special Options
/forceappsclose Forces other programs to close when the computer shuts down
/log:path Allows the redirection of installation log files

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.

Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Datacenter Edition; Windows Server 2003, Enterprise Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; and Windows Server 2003, Datacenter Edition with SP1:

File NameVersionDateTimeSize
Admin.dll10.0.6754.023-Mar-200619:2120,480
Author.dll10.0.6754.023-Mar-200619:2120,480
Cfgwiz.exe10.0.6754.030-Dec-200500:3698,304
Fp5amsft.dll10.0.6790.014-Feb-200623:13142,024
Fp5autl.dll10.0.6790.014-Feb-200623:13944,840
Fp5avss.dll10.0.6754.023-Mar-200619:2132,768
Fp5awel.dll10.0.6790.014-Feb-200623:131,383,112
Fpadmdll.dll10.0.6790.014-Feb-200623:1327,336
Fpcount.exe10.0.6754.030-Dec-200500:3690,112
Fpexedll.dll10.0.6754.023-Mar-200619:2120,480
Fpmmc.dll10.0.6790.014-Feb-200623:13400,064
Owsadm.exe10.0.6754.030-Dec-200500:3620,480
Owsrmadm.exe10.0.6754.030-Dec-200500:3645,056
Shtml.dll10.0.6754.023-Mar-200619:2120,480

Windows Server, 2003 Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; and Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems:

File NameVersionDateTimeSize
Admin.dll10.0.6783.023-Mar-200619:5113,824
Author.dll10.0.6783.023-Mar-200619:5113,824
Cfgwiz.exe10.0.6783.023-Mar-200619:51318,464
Fp5amsft.dll10.0.6790.023-Mar-200619:51506,056
Fp5autl.dll10.0.6790.023-Mar-200619:513,597,512
Fp5avss.dll10.0.6783.023-Mar-200619:5176,288
Fp5awel.dll10.0.6790.023-Mar-200619:516,195,912
Fpadmdll.dll10.0.6790.023-Mar-200619:5120,680
Fpcount.exe10.0.6783.023-Mar-200619:51264,704
Fpexedll.dll10.0.6783.023-Mar-200619:5110,752
Fpmmc.dll10.0.6790.023-Mar-200619:511,647,808
Owsadm.exe10.0.6783.023-Mar-200619:5132,256
Owsrmadm.exe10.0.6783.023-Mar-200619:51112,128
Shtml.dll10.0.6783.023-Mar-200619:5113,824

Notes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE or SP1QFE files to your system. Otherwise, the installer copies the RTMGDR or SP1GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.

For more information about this behavior, see Microsoft Knowledge Base Article 824994.

For more information about the Update.exe installer, visit the Microsoft TechNet Website.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

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.
  • Registry Key Verification

    You may also be able to verify the files that this security update has installed by reviewing the following registry key.

    Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; Windows Server 2003, Datacenter Edition with SP1; Windows Server 2003, Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP2\KB908981\Filelist

    Note This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly if an administrator or an OEM integrates or slipstreams the 908981 security update into the Windows installation source files.

Microsoft FrontPage Server Extensions 2002 downloaded and installed on Microsoft Windows Server 2000 Service Pack 4, Microsoft Windows XP Service Pack 1, and Microsoft Windows XP Service Pack 2

Prerequisites

This security update requires FrontPage Server Extensions 2002 installed on Microsoft Windows Server 2000 Service Pack 4, Microsoft Windows XP Service Pack 1, and Microsoft Windows XP Service Pack 2.

Restart Requirement

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.

Note that if you are prompted for a reboot, you will not be secure until you restart your machine.

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 download.

Installation Information

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

Installation Information

The security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/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: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:path 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 more information about the supported setup switches, see Microsoft Knowledge Base Article 197147.

Deployment Information

Note In order to install this update you must have administrative rights.

  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. When you receive a message that states the installation was successful, click OK.

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.

Microsoft FrontPage 2002 downloaded and installed on Microsoft Windows Server 2000 Service Pack 4, Microsoft Windows XP Service Pack 1, and Microsoft Windows XP Service Pack 2:

File NameVersionDateTimeSize
Fp30reg.dll10.0.4205.012-Jun-200221:0736,424
Fp5amsft.dll10.0.6790.010-Feb-200608:25142,024
Fp5areg.dll10.0.4205.012-Jun-200221:0736,424
Fp5autl.dll10.0.6790.010-Feb-200608:25944,840
Fp5awel.dll10.0.6790.010-Feb-200608:251,383,112
Fpadmdll.dll10.0.6790.010-Feb-200608:2527,336
Fpmmc.dll10.0.6790.010-Feb-200608:25400,064

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. MBSA 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 Website.

  • 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.

Microsoft FrontPage Server Extensions 2002 (x64)downloaded and installed on Microsoft Windows Server 2003 x64 Edition and Microsoft Windows XP Professional x64 Edition

Prerequisites

This security update requires FrontPage Server Extensions 2002 installed on Microsoft Windows Server 2003 X64 Edition and Microsoft Windows XP Professional x64 Edition.

Restart Requirement

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.

Note that if you are prompted for a reboot, you will not be secure until you restart your machine.

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 download.

Installation Information

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

Installation Information

The security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/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: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:path 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 more information about the supported setup switches, see Microsoft Knowledge Base Article 197147.

Note In order to install this update you must have administrative rights.

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. When you receive a message that states the installation was successful, click OK.

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.

Microsoft FrontPage Server Extensions 2002 downloaded and installed on Microsoft Windows Server 2003 x64 Edition and Microsoft Windows XP Professional x64 Edition:

File NameVersionDateTimeSize
Fp30reg.dll10.0.4205.012-Jun-200221:0736,424
Fp5amsft.dll10.0.6790.010-Feb-200608:25142,024
Fp5areg.dll10.0.4205.012-Jun-200221:0736,424
Fp5autl.dll10.0.6790.010-Feb-200608:25944,840
Fp5awel.dll10.0.6790.010-Feb-200608:251,383,112
Fpadmdll.dll10.0.6790.010-Feb-200608:2527,336
Fpmmc.dll10.0.6790.010-Feb-200608:25400,064

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. MBSA 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 Website.

  • 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.

Microsoft SharePoint Team Services

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 Websites:

Windows Installer 2.0 for Windows 95, Windows 98, Windows 98 SE, and Windows Millennium Edition

Windows Installer 2.0 for Windows 2000 and Windows NT 4.0

Restart Requirement

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.

Removal Information

To remove this security update, use the Add or Remove Programs tool in Control Panel.

Note When you remove this update, you may be prompted to insert the original product CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.

Automated Installation Information

Microsoft Update Website

This update will be available through the Microsoft Update Website. Microsoft Update consolidates updates that are provided by Windows Update and Office Update into one location and lets you choose automatic delivery and installation of high-priority and security updates. We recommend that you install this update by using the Microsoft Update Website. The Microsoft Update Website 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 Microsoft Update Website detect the required updates that you must install on your computer, visit the Microsoft Update Website. You will be given the choice of Express (Recommended) or Custom. After detection is complete, you will receive a list of recommended updates for your approval. Click Install Updates or Review and Install Updates to complete the process.

Installation Information

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

Installation Information

The security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/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: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:path 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 more information about the supported setup switches, see Microsoft Knowledge Base Article 197147.

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 when 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.

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 for Microsoft:

File NameVersionDateTimeSize
Fp5amsft.dll10.0.6790.010-Feb-200608:25142,024
Fp5autl.dll10.0.6790.010-Feb-200608:25944,840
Fp5awec.dll10.0.6711.008-Apr-200402:24608,968
Fp5awel.dll10.0.6790.010-Feb-200608:251,383,112
Fpadmdll.dll10.0.6790.010-Feb-200608:2527,336
Fpcutl.dll10.0.6738.029-Oct-200422:381,170,112
Fpeditax.dll10.0.6714.026-Jan-200522:214,258,504
Fpmmc.dll10.0.6790.010-Feb-200608:25400,064
Owssvr.dll10.0.6738.029-Oct-200422:38834,240
Owstimer.exe10.0.6711.008-Apr-200402:24346,824

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. MBSA 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 Website.

  • 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.

Other Information

Acknowledgments

Microsoft thanks the following for working with us to help protect customers:

Obtaining Other Security Updates:

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

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 Website.

Security Resources:

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 security updates by using Software Update Services, visit the Software Update Services Website.

Windows Server Update Services:

By using Windows Server Update Services (WSUS), administrators can quickly and reliably deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 onto Windows 2000 and later operating systems.

For more information about how to deploy security updates using Windows Server Update Services, visit the Windows Server Update Services Website.

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 Website. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Website.

Note SMS uses the Microsoft Baseline Security Analyzer, the 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 Website. 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 (April 11, 2006): Bulletin published.

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

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft