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

Microsoft Security Bulletin MS09-013 - Critical

Vulnerabilities in Windows HTTP Services Could Allow Remote Code Execution (960803)

Published: April 14, 2009 | Updated: April 29, 2009

Version: 1.1

General Information

Executive Summary

This security update resolves one publicly disclosed vulnerability and two privately reported vulnerabilities in Microsoft Windows HTTP Services (WinHTTP). The most severe vulnerability could allow remote code execution. 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.

This security update is rated Critical for all supported editions of Microsoft Windows 2000, Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerabilities by changing the way that Windows HTTP Services handles errors and validates certificates, and by ensuring that Windows HTTP Services correctly use NTLM credential reflection protection mechanisms. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

Recommendation. The majority of customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.

For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update immediately using update management software, or by checking for updates using the Microsoft Update service.

See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.

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

Affected and Non-Affected Software

The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.

Affected Software

Operating SystemMaximum Security ImpactAggregate Severity RatingBulletins Replaced by this Update
Microsoft Windows 2000 Service Pack 4 Remote Code ExecutionCriticalNone
Windows XP Service Pack 2 and Windows XP Service Pack 3 Remote Code ExecutionCriticalNone
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Remote Code ExecutionCriticalNone
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Remote Code ExecutionCriticalNone
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 Remote Code ExecutionCriticalNone
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems Remote Code ExecutionCriticalNone
Windows Vista and Windows Vista Service Pack 1 Remote Code ExecutionCriticalNone
Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 Remote Code ExecutionCriticalNone
Windows Server 2008 for 32-bit Systems*Remote Code ExecutionCriticalNone
Windows Server 2008 for x64-based Systems*Remote Code ExecutionCriticalNone
Windows Server 2008 for Itanium-based Systems Remote Code ExecutionCriticalNone

*Windows Server 2008 server core installation affected. For supported editions of Windows Server 2008, this update applies, with the same severity rating, whether or not Windows Server 2008 was installed using the Server Core installation option. 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.

Why was this bulletin revised on April 29, 2009? 
This bulletin was revised to communicate that the Known issues with this security update section in the associated Microsoft Knowledge Base Article 960803 has been updated to describe an application compatibility issue between this update and systems running the Websense Logon Agent configured to use Windows Challenge/Response (NTLM) authentication.

Where are the file information details? 
The file information details can be found in Microsoft Knowledge Base Article 960803.

Are the Windows Server 2008 Service Pack 2 Beta, Windows Vista Service Pack 2 Beta, and Windows 7 Beta releases affected by this vulnerability?
Yes. These vulnerabilities were reported after the release of Windows Server 2008 Service Pack 2 Beta, Windows Vista Service Pack 2 Beta, and Windows 7 Beta. Customers running these platforms are encouraged to download and apply the update to their systems.

Security updates are available from Microsoft Update and Windows Update.

How is this security update related to MS09-014? 
The Windows HTTP Services Credential Reflection Vulnerability, CVE-2009-0550, described in this security bulletin also affects Internet Explorer and the Windows Internet (WinINet) API. Microsoft recommends that users of Internet Explorer also install the security update provided by MS09-014, Cumulative Security Update for Internet Explorer (963027).

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

Why does this update address several reported security vulnerabilities? 
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers need to install this update only.

Does this update contain any security-related changes to functionality? 
Yes, in order to resolve the issue described in CVE-2009-0089, Microsoft has implemented a new registry key UseFQDNFallbackForCnCompare under SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp, which controls the behavior of WinHTTP when validating the fully qualified domain name of a host against a certificate's distinguished name entry.

By default, this registry key does not exist, which ensures WinHTTP fully validates that the distinguished name (DN) contained in the certificate is identical to the DN to which the connection was initiated. The old behavior can be re-enabled by setting this registry key to True. In this case, validation will be less strict and will accept if the certificate matches a name change through forwarding at the DNS level. This is the less secure behavior which is default prior to the installation of this security update.

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 Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services.

Customers who require custom support for older releases 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 Microsoft Worldwide Information, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.

Vulnerability Information

The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the April bulletin summary. For more information, see Microsoft Exploitability Index.

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareWindows HTTP Services Integer Underflow Vulnerability - CVE-2009-0086Windows HTTP Services Certificate Name Mismatch Vulnerability - CVE-2009-0089Windows HTTP Services Credential Reflection Vulnerability - CVE-2009-0550Aggregate Severity Rating
Microsoft Windows 2000 Service Pack 4 Critical
Remote Code Execution
Important
Spoofing
Important
Remote Code Execution
Critical
Windows XP Service Pack 2 and Windows XP Service Pack 3 Critical
Remote Code Execution
Important
Spoofing
Important
Remote Code Execution
Critical
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Critical
Remote Code Execution
Important
Spoofing
Important
Remote Code Execution
Critical
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Critical
Remote Code Execution
Important
Spoofing
Important
Remote Code Execution
Critical
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 Critical
Remote Code Execution
Important
Spoofing
Important
Remote Code Execution
Critical
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems Critical
Remote Code Execution
Important
Spoofing
Important
Remote Code Execution
Critical
Windows Vista Critical
Remote Code Execution
Important
Spoofing
Important
Remote Code Execution
Critical
Windows Vista Service Pack 1 Critical
Remote Code Execution
Not applicable Important
Remote Code Execution
Critical
Windows Vista x64 Edition Critical
Remote Code Execution
Important
Spoofing
Important
Remote Code Execution
Critical
Windows Vista x64 Edition Service Pack 1 Critical
Remote Code Execution
Not applicable Important
Remote Code Execution
Critical
Windows Server 2008 for 32-bit Systems* Critical
Remote Code Execution
Not applicable Important
Remote Code Execution
Critical
Windows Server 2008 for x64-based Systems* Critical
Remote Code Execution
Not applicable Important
Remote Code Execution
Critical
Windows Server 2008 for Itanium-based Systems Critical
Remote Code Execution
Not applicable Important
Remote Code Execution
Critical

*Windows Server 2008 server core installation affected. For supported editions of Windows Server 2008, this update applies, with the same severity rating, whether or not Windows Server 2008 was installed using the Server Core installation option. 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.

A remote code execution vulnerability exists in the way that Windows HTTP Services handle specific values that are returned by a remote Web 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 the same user rights as the service or application which calls the WinHTTP API to connect to the attacker's Web server.

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

Mitigating Factors for Windows HTTP Services Integer Underflow Vulnerability - CVE-2009-0086

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:

  • All supported editions of Internet Explorer are not affected by this vulnerability because Windows HTTP Services is not used by the software.

Workarounds for Windows HTTP Services Integer Underflow Vulnerability - CVE-2009-0086

Microsoft has not identified any workarounds for this vulnerability.

FAQ for Windows HTTP Services Integer Underflow Vulnerability - CVE-2009-0086

What is the scope of the vulnerability? 
This is a remote code execution vulnerability. 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 the same user rights as the service or application which calls the WinHTTP API to connect to the attacker's Web server.

This vulnerability affects Windows components and third-party applications that use Windows HTTP Services and are configured to connect to remote, untrusted Web servers.

What causes the vulnerability? 
The vulnerability is caused by lack of validation of a parameter returned by a remote Web server. This could lead to arbitrary code execution.

What is Windows HTTP Services? 
Windows HTTP Services (WinHTTP) provides developers with an HTTP client application programming interface (API) to send requests through the HTTP protocol to Web servers. WinHTTP can be used by both Microsoft Windows components and third-party software. WinHTTP is, amongst others, used by the Universal Plug and Play (UPNP) Service.

What is Universal Plug and Play? 
Universal Plug and Play (UPnP) is a capability that allows devices on a network to discover other devices and determine how to work with them. UPnP is most easily understood by comparison to plug-and-play (PnP) capability that most Windows users already are familiar with. PnP allows the operating system to detect new hardware when you install it on a system. For instance, when you install a new mouse onto your computer, PnP allows Windows to detect it, load the needed drivers, and begin using it. UPnP extends this concept to devices on a network, rather than on the local system itself. UPnP lets computers learn about other devices on the network, and determine how to use them. For instance, a computer could use UPnP to detect whether there are printers on the network that it can use and learn how to use them.

What is the Simple Service Discovery Protocol (SSDP)? 
Device discovery is the process through which UPnP-capable computers become aware of the availability of devices they can use, and learn how to request services from them. When a UPnP-capable computer boots, there may already be devices on the network that it can use. To determine whether this is the case, the computer sends a broadcast request (called an M-SEARCH directive), asking that any UPnP-capable device within the subnet respond directly to it and provide information about using it.

Similarly, when a device that supports UPnP (for instance, a UPnP-capable printer) boots, there may already be UPnP-capable computers on the network that would like to use it. The device broadcasts a message (called a NOTIFY directive) to all computers within the subnet, announcing its presence on the network and inviting computers to make use of its services.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could gain the same user rights as the service or application which calls the WinHTTP API to connect to the attacker's Web server. Applications running under accounts that are configured to have fewer user rights on the system could be less impacted than applications running under accounts with administrative user rights.

How could an attacker exploit the vulnerability? 
An attacker would need to force or entice a program using Windows HTTP Services to connect to his malicious Web server. It is important to note that the Universal Plug and Play (UPnP) service uses the WinHTTP libraries. When this service is enabled, malicious users on the local subnet may respond to SSDP requests and lead the UPnP service to connect using WinHTTP to a malicious host that could then exploit this vulnerability. The UPNP service runs under the LocalService account, which is an account with limited privileges on the system.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The update removes the vulnerability by modifying the way that Windows HTTP Services handles the error resulting in the exploitable condition.

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.

A spoofing vulnerability exists in Windows HTTP Services as a result of the incomplete validation of the distinguished name in a digital certificate. When combined with specific other attacks, such as DNS spoofing, this may allow an attacker to successfully spoof the digital certificate of a Web site for any application that uses Windows HTTP Services.

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

Mitigating Factors for Windows HTTP Services Certificate Name Mismatch Vulnerability - CVE-2009-0089

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:

  • All supported editions of Internet Explorer are not affected by this vulnerability because Windows HTTP Services is not used by the software.

Workarounds for Windows HTTP Services Certificate Name Mismatch Vulnerability - CVE-2009-0089

Microsoft has not identified any workarounds for this vulnerability.

FAQ for Windows HTTP Services Certificate Name Mismatch Vulnerability - CVE-2009-0089

What is the scope of the vulnerability? 
This is a spoofing vulnerability that exists in Windows HTTP Services. When combined with specific other attacks, such as DNS spoofing, this may allow an attacker to successfully spoof the digital certificate of a Web site for any application that uses Windows HTTP Services.

What causes the vulnerability? 
When an application calls into Windows HTTP Services to set up a connection to a remote Web server, WinHTTP only validates the fully qualified domain name of the URL against the certificate of the original Web site to which the host attempted connect to. Specific combinations of DNS spoofing may forward a connection to a different Web server that has a valid certificate for that specific host, but not for the web page to which WinHTTP initiated the connection. The combination of DNS spoofing and this vulnerability could lead to WinHTTP incorrectly considering the certificate for the remote Web server as acceptable. As WinHTTP depends on the application for user interaction, the user might not be warned of this discrepancy by the application.

What is Windows HTTP Services? 
Windows HTTP Services (WinHTTP) provides developers with an HTTP client application programming interface (API) to send requests through the HTTP protocol to other HTTP servers.

What are digital certificates? 
The digital certificate is a common credential that's used to authenticate identity. A trusted organization assigns a certificate to an individual or an entity, the subject of that certificate. The trusted organization that issues the certificate is a Certification Authority (CA) and is known as the certificate's issuer. A trustworthy CA will issue a certificate only after verifying the identity of the certificate's subject.

What is DNS spoofing? 
Domain Name System (DNS) is one of the industry-standard suite of protocols that comprise TCP/IP. DNS is implemented using two software components: the DNS server and the DNS client (or resolver). Both components are run as background service applications. Network resources are identified by numeric IP addresses, but these IP addresses are difficult for network users to remember. The DNS database contains records that map user-friendly alphanumeric names for network resources to the IP addresses used by those resources for communication. In this way, DNS acts as a mnemonic device, making network resources easier to remember for network users. For more information and to view logical diagrams illustrating how DNS fits with other Windows technologies, review the TechNet article, What is DNS?

DNS Spoofing is a broad category of attacks in which at one point within the DNS system, incorrect DNS responses are introduced by a third party not normally responsible for those responses. Such an attack may cause a domain or host name to resolve to an IP address to which it was not intended to resolve by the owners of that name. As such, a host may be elicited to connect to a third-party, potentially malicious server.

What might an attacker use the vulnerability to do? 
An attacker could impersonate a secure Web site and offer malicious content to the application using Windows HTTP Services, which would trust it as if it originated from a secure Web site.

How could an attacker exploit the vulnerability? 
An attacker would need to combine this vulnerability with DNS spoofing or a similar attack in order to direct the outbound connection to a server under his control. He would then offer a certificate valid for the his Web site connected to which would be incorrectly validated by Windows HTTP Services as valid for the destination host Web site to which the user originally tried to connect.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The update removes the vulnerability by changing the way Windows HTTP Services validates certificates belonging to a secure Web site.

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.

A remote code execution vulnerability exists in the way that Windows HTTP Services handles NTLM credentials when a user connects to an attacker's Web server. This vulnerability allows an attacker to replay the user's credentials back to the attacker and execute code in the context of 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.

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

Mitigating Factors for Windows HTTP Services Credential Reflection Vulnerability - CVE-2009-0550

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

  • In a Web-based attack scenario, 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 or advertisements 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 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.
  • All supported editions of Windows Vista and Windows Server 2008 by default have the profile for the Windows firewall set to public, which reduces exposure on these platforms to this vulnerability because, under public profile, the firewall blocks SMB traffic. Since the client would need to be running a service which accepts NTLM authentication in order for the attack to be successful and the credentials reflected, the most common attack vector would be SMB.

Workarounds for Windows HTTP Services Credential Reflection Vulnerability - CVE-2009-0550

Microsoft has not identified any workarounds for this vulnerability.

FAQ for Windows HTTP Services Credential Reflection Vulnerability - CVE-2009-0550

What is the scope of the vulnerability? 
This is a remote code execution vulnerability. 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.

In addition, this issue also affects Internet Explorer and the Windows Internet API. Microsoft recommends that users of Internet Explorer install the security update provided by MS09-014, Cumulative Security Update for Internet Explorer (963027).

What causes the vulnerability? 
Windows HTTP Services does not correctly opt-in to NTLM credential-reflection protections to ensure that a user's credentials are not reflected back and used against the user.

What is Microsoft Windows HTTP Services? 
Microsoft Windows HTTP Services (WinHTTP) provides developers with an HTTP client application programming interface (API) to send requests through the HTTP protocol to other HTTP servers.

What might an attacker use the vulnerability to do? 
An attacker could gain the rights of the logged-on user and do anything that the logged-on user has privileges to do. 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.

How could an attacker exploit the vulnerability? 
This vulnerability requires that a user with an affected version of Windows HTTP Services accesses a malicious server. An attacker would have to host a specially crafted Web server which captures the user's NTLM log on credentials. The attacker then replays those credentials to a service on the user's client that accepts NTLM authentication. An attacker would have no way to force users to visit a specially crafted server. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the attacker's site.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The security update remediates the vulnerability by ensuring that Windows HTTP Services opts appropriately into credential protection mechanisms available from Windows.

Why is this vulnerability and the WinINet Credential Reflection Vulnerability assigned the same CVE number (CVE-2009-0550) in MS09-014, Cumulative Security Update for Internet Explorer (963027)? 
CVE-2009-0550 affects both WinINet, as used by Internet Explorer, and Windows HTTP Services, a component of the Windows operating system. Microsoft recommends that users of Internet Explorer also install the security update provided by MS09-014, Cumulative Security Update for Internet Explorer (963027).

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-2009-0550.

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.

Update Information

Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.

Security updates are available from Microsoft Update, Windows Update, and Office Update. Security updates are also available from 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, "MS07-036"), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.

Detection and Deployment Guidance

Microsoft has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, 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.

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

Software MBSA 2.1
Microsoft Windows 2000 Service Pack 4Yes
Windows XP Service Pack 2 and Windows XP Service Pack 3Yes
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2Yes
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2Yes
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2Yes
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based SystemsYes
Windows Vista and Windows Vista Service Pack 1Yes
Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1Yes
Windows Server 2008 for 32-bit SystemsYes
Windows Server 2008 for x64-based SystemsYes
Windows Server 2008 for Itanium-based SystemsYes

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. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.

Systems Management Server

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

SoftwareSMS 2.0SMS 2003 with SUSFPSMS 2003 with ITMUConfiguration Manager 2007
Microsoft Windows 2000 Service Pack 4YesYesYesYes
Windows XP Service Pack 2 and Windows XP Service Pack 3YesYesYesYes
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2NoNoYesYes
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2YesYesYesYes
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2NoNoYesYes
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based SystemsNoNoYesYes
Windows Vista and Windows Vista Service Pack 1NoNoSee Note for Windows Vista and Windows Server 2008 belowYes
Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1NoNoSee Note for Windows Vista and Windows Server 2008 belowYes
Windows Server 2008 for 32-bit SystemsNoNoSee Note for Windows Vista and Windows Server 2008 belowYes
Windows Server 2008 for x64-based SystemsNoNoSee Note for Windows Vista and Windows Server 2008 belowYes
Windows Server 2008 for Itanium-based SystemsNoNoSee Note for Windows Vista and Windows Server 2008 belowYes

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 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 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.

Update Compatibility Evaluator and Application Compatibility Toolkit

Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit 5.0.

The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.

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 interventionFor Microsoft Windows 2000 Service Pack 4:
Windows2000-KB960803-x86-ENU /quiet
Installing without restartingFor Microsoft Windows 2000 Service Pack 4:
Windows2000-KB960803-x86-ENU /norestart
Update log fileFor Microsoft Windows 2000 Service Pack 4:
kb960803.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?Yes, you must restart your system after you apply this security update.
HotPatchingNot applicable
Removal Information For Microsoft Windows 2000 Service Pack 4:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB960803$\Spuninst folder
File Information See Microsoft Knowledge Base Article 960803
Registry Key Verification For Microsoft Windows Service Pack 4: 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB960803\Filelist


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.

If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR 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 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
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 Displays 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
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 Displays 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.

  • File Version Verification

    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

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

      Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
  • 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.

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 interventionFor all supported 32-bit editions of Windows XP:
WindowsXP-KB960803-x86-ENU /quiet
For all supported x64-based editions of Windows XP:
WindowsServer2003.WindowsXP-KB960803-x64-ENU /quiet
Installing without restartingFor all supported 32-bit editions of Windows XP:
WindowsXP-KB960803-x86-ENU /norestart
For all supported x64-based editions of Windows XP:
WindowsServer2003.WindowsXP-KB960803-x64-ENU /norestart
Update log fileKB960803.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?Yes, you must restart your system after you apply this security update.
HotPatchingNot applicable
Removal Information Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB960803$\Spuninst folder
File Information See Microsoft Knowledge Base Article 960803
Registry Key Verification For all supported 32-bit editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB960803\Filelist
For all supported x64-based editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB960803\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

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.

If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR 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 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
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 Displays 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
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 Displays 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.

  • File Version Verification

    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

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

      Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
  • 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.

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 interventionFor all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB960803-x86-ENU /quiet
For all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB960803-x64-ENU /quiet
For all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB960803-ia64-ENU /quiet
Installing without restartingFor all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB960803-x86-ENU /norestart
For all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB960803-x64-ENU /norestart
For all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB960803-ia64-ENU /norestart
Update log fileKB960803.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?Yes, you must restart your system after you apply this security update.
HotPatchingThis security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.
Removal Information Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB960803$\Spuninst folder
File Information See Microsoft Knowledge Base Article 960803
Registry Key Verification HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB960803\Filelist

Deployment Information

Installing the Update

When you install this security update, 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, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR 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 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
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 Displays 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
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 Displays 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.

  • File Version Verification

    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

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

      Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
  • 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.

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 interventionFor all supported 32-bit editions of Windows Vista:
Windows6.0-KB960803-x86 /quiet

For all supported x64-based editions of Windows Vista:
Windows6.0-KB960803-x64 /quiet
Installing without restartingFor all supported 32-bit editions of Windows Vista:
Windows6.0-KB960803-x86 /quiet /norestart

For all supported x64-based editions of Windows Vista:
Windows6.0-KB960803-x64 /quiet /norestart
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?Yes, you must restart your system after you apply this security update.
HotPatchingNot 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.
File Information See Microsoft Knowledge Base Article 960803
Registry Key Verification Note A registry key does not exist to validate the presence of this update.

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
SwitchDescription
/?, /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 wusa.exe 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.

  • File Version Verification

    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start and then enter an update file name in Start Search.
    2. When the file appears under Programs, right-click on the file name and click Properties.
    3. Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
    4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
    5. Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

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 interventionFor all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB960803-x86 /quiet

For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB960803-x64 /quiet

For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB960803-ia64 /quiet
Installing without restartingFor all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB960803-x86 /quiet /norestart

For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB960803-x64 /quiet /norestart

For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB960803-ia64 /quiet /norestart
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?Yes, you must restart your system after you apply this security update.
HotPatchingNot 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.
File Information See Microsoft Knowledge Base Article 960803
Registry Key Verification Note A registry key does not exist to validate the presence of this update.

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
SwitchDescription
/?, /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 wusa.exe 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.

  • File Version Verification

    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start and then enter an update file name in Start Search.
    2. When the file appears under Programs, right-click on the file name and click Properties.
    3. Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
    4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
    5. Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Other Information

Acknowledgments

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

  • Greg MacManus of iSIGHT Partners Labs for reporting the Windows HTTP Services Integer Underflow Vulnerability (CVE-2009-0086)
  • Wan-Teh Chang and Cem Paya of Google for reporting the Windows HTTP Services Certificate Name Mismatch Vulnerability (CVE-2009-0089)

Microsoft Active Protections Program (MAPP)

To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.

Support

  • Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support.
  • International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.

Disclaimer

The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

Revisions

  • V1.0 (April 14, 2009): Bulletin published.
  • V1.1 (April 29, 2009): Added entry to the section, Frequently Asked Questions (FAQ) Related to This Security Update, to communicate that the Known issues with this security update section in the associated Microsoft Knowledge Base Article 960803 has been updated. This is an informational change only.

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

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