Microsoft Security Bulletin MS08-032 - Moderate

What is a kill bit?
A security feature in Microsoft Internet Explorer makes it possible to prevent an ActiveX control from ever being loaded by the Internet Explorer HTML-rendering engine. This is done by making a registry setting and is referred to as setting the kill bit. After the kill bit is set, the control can never be loaded, even when it is fully installed. Setting the kill bit makes sure that even if a vulnerable component is introduced or is re-introduced to a system, it remains inert and harmless.

For more information on a kill bit, see Microsoft Knowledge Base Article 240797: How to stop an ActiveX control from running in Internet Explorer.

What is a security update of ActiveX kill bits? 
This security update only contains the class IDs (CLSID) of certain ActiveX controls that are the basis of this security update. This security bulletin lists these CLSIDs in the Vulnerability Section.

Why does this update not contain any binary files?
This update only makes changes to the registry to disable the control from instantiating in Internet Explorer.

Should I install this update if I do not have the affected component installed or use the affected platform?
Yes. Installing this update will block the vulnerable control from running in Internet Explorer.

Do I need to reapply this update if I install an ActiveX control discussed in this security update at a later date?
No, reapplying this update is not required. The kill bit will block Internet Explorer from running the control even if the control is installed at a later date.

Does this update contain any kill bits that are not Microsoft-specific? 
Yes. Microsoft has been requested by an organization to set the kill bit for a control that the organization owns and has found to be vulnerable.

Does this update contain kill bits that were previously shipped in an Internet Explorer security update?
No, this update does not include kill bits that were previously shipped in an Internet Explorer security update. We recommend that you install the latest Cumulative Security Update for Internet Explorer.

Why does this security update have different severity levels for different Windows operating systems?
This update has different severity levels because different mitigations apply to the vulnerability depending on the operating system. One such mitigation is that Internet Explorer on Windows Server 2003 and Windows Server 2008 runs in a restricted mode known as Enhanced Security Configuration.

Do users with a Windows Server 2008 server core installation need to install this update?
Users with a Windows Server 2008 server core installation will be offered this update, but do not need to install it. For more information on the Server Core installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.

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

It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. 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 software releases, 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.

*Windows Server 2008 server core installation not affected, but will be offered this update. Vulnerabilities addressed by this update do not affect supported editions of Windows Server 2008 if Windows Server 2008 was installed using the Server Core installation option, even though the files affected by these vulnerabilities may be present on the system. However, users with the affected files will still be offered this update because the update files are newer (with higher version numbers) than the files that are currently on your system. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.

Note for Affected Software  Microsoft does not rate the severity of third party controls for which this update sets a kill bit. However, the kill bit will be deployed across all platforms, including a platform which is not affected by a vulnerability in Microsoft software. See also the subsection, “Third Party Kill Bits,” in this section.

A remote code execution vulnerability exists in the Speech Components sapi.dll. An attacker could exploit the vulnerability by constructing a specially crafted Web page. When a user views the Web page, the vulnerability could allow remote code execution. The user must have the Speech Recognition feature in Windows enabled. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged on user.

This control was never intended to be instantiated in Internet Explorer.

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

Mitigating Factors for Speech API Vulnerability - CVE-2007-0675

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

•	By default the speech recognition feature of Windows Vista is not enabled.
•	In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail or Instant Messenger message that takes users to the attacker's Web site.
•	An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. 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.
•	By default, Internet Explorer on Windows Server 2003 and Windows Server 2008 runs in a restricted mode that is known as Enhanced Security Configuration. This mode sets the security level for the Internet zone to High. This is a mitigating factor for Web sites that you have not added to the Internet Explorer Trusted sites zone. See the FAQ subsection of this vulnerability section for more information about Internet Explorer Enhanced Security Configuration.

Top of section

Workarounds for Speech API Vulnerability - CVE-2007-0675

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:

•

Prevent COM objects from running in Internet Explorer You can disable attempts to instantiate a COM object in Internet Explorer by setting the kill bit for the control in the registry. Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. For detailed steps that you can use to prevent a control from running in Internet Explorer, see Microsoft Knowledge Base Article 240797. Follow these steps in this article to create a Compatibility Flags value in the registry to prevent a COM object from being instantiated in Internet Explorer. Note The Class Identifiers and corresponding files where the ActiveX objects are contained are documented under “What does the update do?” in the “FAQ for Speech API Vulnerability - CVE-2007-0675” section. Replace {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} below with the Class Identifiers found in this section. To set the kill bit for a CLSID with a value of {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}, paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{ XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX }] "Compatibility Flags"=dword:00000400 You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy. For more information about Group Policy, visit the following Microsoft Web sites: • Group Policy collection • What is Group Policy Object Editor? • Core Group Policy tools and settings Note You must restart Internet Explorer for your changes to take effect.

•

Impact of Workaround: There is no impact as long as the object is not intended to be used in Internet Explorer.

Top of section

FAQ for Speech API Vulnerability - CVE-2007-0675

What is the scope of the vulnerability? 
This is a remote code execution vulnerability. The user must have the Speech Recognition feature in Windows enabled. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user.

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.

What causes the vulnerability? 
When the speech recognition feature is activated and configured, it may be possible via playing an audio file in Internet Explorer, to issue commands in such a way that an attacker could execute arbitrary code.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. 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.

It is not possible through the use of voice commands to get the system to perform privileged functions such as creating a user without being prompted by UAC for Administrator credentials. The UAC prompt cannot be manipulated by voice commands by default. There are additional barriers that would make an attack difficult including speaker and microphone placement, microphone feedback, and the clarity of the dictation.

How could an attacker exploit the vulnerability? 
An attacker could host a specially crafted Web site that is designed to exploit this vulnerability through Internet Explorer and then convince a user to view the Web site. This can also include compromised Web sites and Web sites that accept or host user-provided content or advertisements. These Web sites 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 convince users to visit the Web site, typically by getting them to click a link in an e-mail message or in an Instant Messenger request that takes users to the attacker's Web site. It could also be possible to display specially crafted Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.

I am running Internet Explorer for Windows Server 2003 or Windows Server 2008. Does this mitigate this vulnerability? 
Yes. By default, Internet Explorer on Windows Server 2003 and Windows Server 2008 runs in a restricted mode that is known as Enhanced Security Configuration. Enhanced Security Configuration is a group of preconfigured settings in Internet Explorer that can reduce the likelihood of a user or administrator downloading and running specially crafted Web content on a server. This is a mitigating factor for Web sites that you have not added to the Internet Explorer Trusted sites zone. See also Managing Internet Explorer Enhanced Security Configuration.

What systems are primarily at risk from the vulnerability? 
This vulnerability requires that a user be logged on and visit a Web site for any malicious action to occur. Therefore, any systems where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability. Systems that have activated the speech recognition feature are at risk from this vulnerability.

What does the update do? 
This update sets the kill bit for a list of Class Identifiers (CLSIDs).

The Class Identifiers and corresponding files are as follows:

Class Identifier	File
{47206204-5eca-11d2-960f-00c04f8ee628}	sapi.dll
{3bee4890-4fe9-4a37-8c1e-5e7e12791c1f}	sapi.dll

Why does this security update not include Windows Vista Service Pack 1?
This update does not set kill bits for Windows Vista Service Pack 1 because the vulnerability described by CVE-2007-0675 has been addressed in the service pack update.

What is SAPI? 
SAPI is the Microsoft Speech Application Programming interface that is available for developers to add speech recognition and text-to-speech capabilities to applications.

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 number CVE-2007-0675. It also has been named “Vista Speech Recognition” by the larger security community.

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.

Top of section

This update includes kill bits that will prevent the following ActiveX controls from being run in Internet Explorer:

Manage the software and security updates you need to deploy to the servers, desktop, and mobile computers 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, Windows Update, and Office Update. Security updates are also available at the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."

Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, “MS08-010”), 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, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, 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.

For more information about MBSA 2.1, see MBSA 2.1 Frequently Asked Questions.

Windows Server Update Services

By using Windows Server Update Services (WSUS), administrators can 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 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.

For SMS 2.0 and SMS 2003, the SMS SUS Feature Pack (SUSFP), which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0.

For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about the Office Inventory Tool and other scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.

System Center Configuration Manager (SCCM) 2007 uses WSUS 3.0 for detection of updates. For more information about SCCM 2007 Software Update Management, visit System Center Configuration Manager 2007.

Note for Windows Vista and Windows Server 2008  Microsoft Systems Management Server 2003 with Service Pack 3 includes support for Windows Vista and Windows Server 2008 manageability.

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

For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.

Affected Software

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

Windows 2000 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs	The update for this issue may be included in a future update rollup
Deployment
Installing without user intervention	Microsoft Windows 2000 Service Pack 4: Windows2000-KB950760-x86-ENU /quiet
Installing without restarting	Microsoft Windows 2000 Service Pack 4: Windows2000-KB950760-x86-ENU /norestart
Update log file	Microsoft Windows 2000 Service Pack 4: KB950760.log
Further information	See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?	In some cases, this update does not require a restart. If a restart is required, a message appears that advises you to restart.
Hotpatching	Not applicable
Removal Information	Microsoft Windows 2000 Service Pack 4: Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB950760$\Spuninst folder
Registry Key Verification	Microsoft Windows 2000 Service Pack 4: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB950760\Filelist

Deployment Information

Installing the Update

For more information about the installer, visit the Microsoft TechNet 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
Switch	Description
/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
/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 the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
Switch	Description
/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

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.

•

Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section. These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Top of section

Top of section

Windows XP (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs	The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention	Windows XP Service Pack 2 and Windows XP Service Pack 3: Windowsxp-kb950760-x86-enu /quiet
	Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB950760-x64-enu /quiet
Installing without restarting	Windows XP Service Pack 2 and Windows XP Service Pack 3: Windowsxp-kb950760-x86-enu /norestart
	Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB950760-x64-enu / norestart
Update log file	All supported editions of Windows XP and Windows XP Professional: KB950760.log
Further information	See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?	In some cases, this update does not require a restart. If a restart is required, a message appears that advises you to restart.
Hotpatching	Not applicable
Removal Information	All supported editions of Windows XP and Windows XP Professional: Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB950760$\Spuninst folder
Registry Key Verification	Windows XP Service Pack 2 and Windows XP Service Pack 3: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB950760\Filelist
	Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB950760\Filelist

Note For supported versions of Windows XP Professional x64 Edition, this security update is the same as supported versions of the Windows Server 2003 x64 Edition security update.

Deployment Information

Installing the Update

For more information about the installer, visit the Microsoft TechNet 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
Switch	Description
/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 the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
Switch	Description
/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

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.

•

Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section. These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Top of section

Top of section

Windows Server 2003 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs	The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention	Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2: Windowsserver2003-kb950760-x86-enu /quiet
	Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB950760-x64-enu /quiet
	Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems Windowsserver2003-kb950760-ia64-enu /quiet
Installing without restarting	Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2: Windowsserver2003-kb950760-x86-enu /norestart
	Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB950760-x64-enu /norestart
	Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems: Windowsserver2003-kb950760-ia64-enu /norestart
Update log file	All supported Windows Server 2003 32-bit editions, x64-based editions, and Itanium-based editions of Windows Server 2003: KB950760.log
Further information	See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?	In some cases, this update does not require a restart. If a restart is required, a message appears that advises you to restart.
Hotpatching	This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.
Removal Information	All supported 32-bit editions, x64-based editions, and Itanium-based editions of Windows Server 2003: Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the Use the Spuninst.exe utility, located in the %Windir%\$NTUninstallKB950760$\Spuninst folder
Registry Key Verification	All supported editions of Windows Server 2003: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB950760\Filelist

Deployment Information

Installing the Update

For more information about the installer, visit the Microsoft TechNet 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
Switch	Description
/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.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
Switch	Description
/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

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.

•

Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section. These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Top of section

Top of section

Windows Vista (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs	The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention	All supported 32-bit editions of Windows Vista: Windows6.0-KB950760-x86 /quiet
	All supported 64-bit editions of Windows Vista: Windows6.0-KB950760-x64 /quiet
Installing without restarting	All supported 32-bit editions of Windows Vista: Windows6.0-KB950760-x86 /quiet /norestart
	All supported 64-bit editions of Windows Vista: Windows6.0-KB950760-x64 /quiet /norestart
Restart Requirement
Restart required?	In some cases, this update does not require a restart. If a restart is required, a message appears that advises you to restart.
Hotpatching	Not applicable.
Removal Information	WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.
Registry Key Verification	Note: A registry key does not exist to validate the presence of this patch.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

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
Switch	Description
/?, /h, /help	Displays help on supported switches.
/quiet	Suppresses the display of status or error messages.
/norestart	When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.

Note For more information about the installer, see Microsoft Knowledge Base Article 934307.

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.

Top of section

Top of section

Windows Server 2008 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs	The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention	All supported 32-bit editions of Windows Server 2008: Windows6.0-KB950760-x86 /quiet
	All supported x64-based editions of Windows Server 2008: Windows6.0-KB950760-x64 /quiet
	All supported Itanium-based editions of Windows Server 2008: Windows6.0-KB950760-ia64 /quiet
Installing without restarting	All supported 32-bit editions of Windows Server 2008: Windows6.0-KB950760-x86 /quiet /norestart
	All supported x64-based editions of Windows Server 2008: Windows6.0-KB950760-x64 /quiet /norestart
	All supported Itanium-based editions of Windows Server 2008: Windows6.0-KB950760-ia64 /quiet /norestart
Further information	See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?	In some cases, this update does not require a restart. If a restart is required, a message appears that advises you to restart.
Hotpatching	Not applicable.
Removal Information	WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.
Registry Key Verification	Note: A registry key does not exist to validate the presence of this patch.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

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
Switch	Description
/?, /h, /help	Displays help on supported switches.
/quiet	Suppresses the display of status or error messages.
/norestart	When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.

Note For more information about the installer, see Microsoft Knowledge Base Article 934307.

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.

Top of section

Top of section