Security Bulletin

Microsoft Security Bulletin MS08-037 - Important

Vulnerabilities in DNS Could Allow Spoofing (953230)

Published: July 08, 2008 | Updated: December 09, 2009

Version: 3.1

General Information

Executive Summary

This security update resolves two privately reported vulnerabilities in the Windows Domain Name System (DNS) that could allow spoofing. These vulnerabilities exist in both the DNS client and DNS server and could allow a remote attacker to redirect network traffic intended for systems on the Internet to the attacker’s own systems.

This security update is rated Important for all supported editions of Microsoft Windows 2000, Windows XP, Windows Server 2003, 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 using strongly random DNS transaction IDs, using random sockets for UDP queries, and updating the logic used to manage the DNS cache. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

Recommendation. Microsoft recommends that customers apply the update at the earliest opportunity.

Known Issues. Microsoft Knowledge Base Article 953230 documents the currently known issues that customers may experience when they install this security update.

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

DNS Client (KB951748) DNS Server (KB951746) Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by this Update
Microsoft Windows 2000 Service Pack 4 See row below Spoofing Important MS08-001,
MS08-020
See row above Microsoft Windows 2000 Server Service Pack 4 Spoofing Important MS07-062
Windows XP Service Pack 2 Not applicable Spoofing Important MS06-064,
MS08-001
Windows XP Service Pack 3 Not applicable Spoofing Important None
Windows XP Professional x64 Edition Not applicable Spoofing Important MS06-064,
MS08-001
Windows XP Professional x64 Edition Service Pack 2 Not applicable Spoofing Important MS08-001
Windows Server 2003 Service Pack 1 See row below Spoofing Important MS06-064,
MS08-001
Windows Server 2003 Service Pack 2 See row below Spoofing Important MS08-001
See row above Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Spoofing Important MS07-062
Windows Server 2003 x64 Edition See row below Spoofing Important MS06-064,
MS08-001
Windows Server 2003 x64 Edition Service Pack 2 See row below Spoofing Important MS08-001
See row above Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 Spoofing Important MS07-062
Windows Server 2003 with SP1 for Itanium-based Systems See row below Spoofing Important MS06-064,
MS08-001
Windows Server 2003 with SP2 for Itanium-based Systems See row below Spoofing Important MS08-001
See row above Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems Spoofing Important MS07-062
Not applicable Windows Server 2008 for 32-bit Systems\* Spoofing Important None
Not applicable Windows Server 2008 for x64-based Systems\* Spoofing Important None
**\*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](http://msdn.microsoft.com/en-us/library/ms723891(vs.85).aspx). Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see [Compare Server Core Installation Options](http://www.microsoft.com/windowsserver2008/en/us/compare-core-installation.aspx). **Non-Affected Software** | Operating System | |------------------------------------------------------------------------| | Windows Vista and Windows Vista Service Pack 1 | | Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 | | Windows Server 2008 for Itanium-based Systems | Frequently Asked Questions (FAQ) Related to This Security Update ---------------------------------------------------------------- **Why was this bulletin rereleased on December 8, 2009?**  Microsoft rereleased this bulletin to reoffer the update for the DNS client on Microsoft Windows 2000 Service Pack 4 (KB951748) to provide strongly random DNS transaction IDs to an additional code path. Unlike the other Windows platforms, on Microsoft Windows 2000, there are two code paths for DNS transactions. The previous update only provided the transaction ID randomization on one of the code paths. The rerelease of this update provides the same transaction ID randomization to the other code path on Microsoft Windows 2000. Customers who have previously installed the update for the DNS client on Microsoft Windows 2000 Service Pack 4 (KB951748) need to install the automatically reoffered update. No other updates are affected by this rerelease. **Why was this security bulletin revised on January 13, 2009?** Microsoft revised this bulletin to communicate that the update offered by this bulletin may not have been correctly offered to all systems running Windows XP Service Pack 3. The detection and deployment issue has been fixed, and customers with Windows XP Service Pack 3 systems who have not already applied the update from this bulletin will now be correctly offered the update. There were no changes to the binaries for this update. Customers who have successfully updated their systems do not need to reinstall this update. **Why was this security bulletin revised on July 25, 2008?** Microsoft revised this security bulletin to add three new known issues to **Frequently Asked Questions (FAQ) Related to This Security Update**. These FAQs are as follows: - **What are the port conflict issues that customers may encounter after installing this update?** DNS servers performing additional services that require static UDP ports within the port range that the DNS server allocates for its socket pool may experience port conflicts leading to service failures. For additional information, [Microsoft Knowledge Base Article 953230](http://support.microsoft.com/kb/953230) documents the currently known issues that customers may experience when they install this security update. - **What are the issues that SBS customers may encounter after installing this update?** Supported editions of Windows Small Business Server (SBS) 2003 contain the same affected code as Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2. However, SBS systems may encounter service failures or may not work properly after installing the DNS server security update offered in this bulletin. For additional information, [Microsoft Knowledge Base Article 953230](http://support.microsoft.com/kb/953230) documents the currently known issues that customers may experience when they install this security update. - **What are the issues that perimeter firewalls and perimeter NAT devices may encounter after installing this update?** After installing the security update offered by this bulletin on a Windows-based computer, the DNS queries from that host across a firewall may no longer use random source ports. For additional information, [Microsoft Knowledge Base Article 953230](http://support.microsoft.com/kb/953230) documents the currently known issues that customers may experience when they install this security update. **Why was this security bulletin revised on July 23, 2008?** Microsoft revised this security bulletin to list MS06-064, MS07-062, and MS08-001 as bulletins replaced by this update. **Why was this security bulletin revised on July 10, 2008?** Microsoft revised this security bulletin to inform users of ZoneAlarm and Check Point Endpoint Security (previously known as Check Point Integrity), from [Check Point Software Technologies Ltd.](http://www.checkpoint.com/), of an Internet connectivity issue detailed in the following FAQ. The revision did not change the security update files in this bulletin. Customers who have already applied the update do not have to reapply the update. Users of the above software from Check Point should, however, read the following FAQ for further guidance. **What is the issue that users of ZoneAlarm and Check Point Endpoint Security may experience after installing this update?** Microsoft is aware of recent reports that users of ZoneAlarm and Check Point Endpoint Security (previously known as Check Point Integrity), from Check Point Software Technologies Ltd., are experiencing an Internet connectivity issue after applying the security updates offered by this security bulletin, MS08-037. Microsoft is continuing to investigate this issue with Check Point. Microsoft encourages the users of [ZoneAlarm](http://download.zonealarm.com/bin/free/pressreleases/2008/lossofinternetaccessissue.html) and Check Point Endpoint Security to review the appropriate [Check Point Web site](https://supportcenter.checkpoint.com/supportcenter/index.jsp) and this security bulletin for the latest guidance or software updates. Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information. The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products. **What are the uninstall issues that customers may experience after installing these security updates?** Supported editions of Microsoft Windows 2000 and Windows 2003 systems will receive the DNS server update as well as the DNS client updates. The DNS server update and the DNS client updates share binaries and must be uninstalled in the reverse order that they were installed to avoid regressing the shared binaries to previous versions. [Microsoft Knowledge Base Article 823836](http://support.microsoft.com/kb/823836) documents the currently known issues that customers may experience when they uninstall these security updates. **What are the random socket connection issues that customers may experience when installing this security update?** By default, the DNS updates offered by this security bulletin will take advantage of a large number of available sockets to offer greater entropy. However, if the user has defined port ranges in the registry, then the updates will respect the user-defined settings and will only allocate the defined sockets. Socket ranges can be defined in the following registry location: **HKLM\\System\\CurrentControlSet\\Services\\DNS\\Parameters Reg key Name: SocketPoolSize** **Note** The DNS service must be restarted to implement these changes. **What does defining the socket pool range do?** It may be necessary to define the range of sockets that DNS can choose from to avoid conflicting with other applications or services that need the same socket pool for their communications. See [MaxUserPort](http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentry/58791.mspx?mfr=true) and [Microsoft Knowledge Base Article 812873](http://support.microsoft.com/kb/812873) for more details about these registry key settings. **What are the differences between operating systems when defining the socket pool ranges?** The MaxUserPort registry Key has different meanings on Windows Vista and Windows Server 2008 than on Microsoft Windows Server 2000 and Windows Server 2003. [Microsoft knowledge Base Article 929851](http://support.microsoft.com/kb/929851) details the change in behavior for Windows Vista and Windows Server 2008. In Microsoft Windows Server 2000 and Windows Server 2003, setting the MaxUserPort defines the ending point of the dynamic port range. The range starts at 1024 and continues to the user-defined value in the MaxUserPort registry key setting. After installing the updates offered by this security bulletin, the default behavior on Microsoft Windows Server 2000 and Windows Server 2003 will be to allocate sockets randomly from the port range 49152 to 65535. If the MaxUserPort range has been defined, then ports will be allocated randomly from 1024 to the defined value in the MaxUserPort registry key setting. Visit [Microsoft Knowledge Base Article 812873](http://support.microsoft.com/kb/812873) for more information on reserving port ranges on Microsoft Windows 2000 Server and Windows Server 2003. In Windows Vista and Windows Server 2008, setting the MaxUserPort defines the starting point of the dynamic port range. By default, the range on Windows Vista and Windows Server 2008 is 49152 to 65535. **Where are the file information details?**  The file information details can be found in [Microsoft Knowledge Base Article 953230](http://support.microsoft.com/kb/953230). **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](http://go.microsoft.com/fwlink/?linkid=21742). 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](http://go.microsoft.com/fwlink/?linkid=21742). For more information about the extended security update support period for these software versions or editions, visit [Microsoft Product Support Services](http://go.microsoft.com/fwlink/?linkid=33328). 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](http://go.microsoft.com/fwlink/?linkid=33329), 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](http://go.microsoft.com/fwlink/?linkid=33330). ### Vulnerability Information Severity Ratings and Vulnerability Identifiers ----------------------------------------------

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software DNS Insufficient Socket Entropy Vulnerability - CVE-2008-1447 DNS Cache Poisoning Vulnerability - CVE-2008-1454 Aggregate Severity Rating
Microsoft Windows 2000 Service Pack 4 Important
Spoofing		 Important
Spoofing		 Important
Windows XP Service Pack 2 and Windows XP Service Pack 3 Important
Spoofing		 Not applicable Important
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Important
Spoofing		 Not applicable Important
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Important
Spoofing		 Important
Spoofing		 Important
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 Important
Spoofing		 Important
Spoofing		 Important
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems Important
Spoofing		 Important
Spoofing		 Important
Windows Server 2008 for 32-bit Systems\* Not applicable Important
Spoofing		 Important
Windows Server 2008 for x64-based Systems\* Not applicable Important
Spoofing		 Important
**\*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](http://msdn.microsoft.com/en-us/library/ms723891(vs.85).aspx). Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see [Compare Server Core Installation Options](http://www.microsoft.com/windowsserver2008/en/us/compare-core-installation.aspx). DNS Insufficient Socket Entropy Vulnerability - CVE-2008-1447 ------------------------------------------------------------- A spoofing vulnerability exists in Windows DNS client and Windows DNS server. This vulnerability could allow a remote unauthenticated attacker to quickly and reliably spoof responses and insert records into the DNS server or client cache, thereby redirecting Internet traffic. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2008-1447](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2008-1447). #### Mitigating Factors for DNS Insufficient Socket Entropy Vulnerability - CVE-2008-1447 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. - Cryptographic protocols operating above the TCP and IP layers, such as IPsec or SSL/TLS, may prevent an attacker from being able to monitor or interfere with redirected traffic. #### Workarounds for DNS Insufficient Socket Entropy Vulnerability - CVE-2008-1447 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 not identified any workarounds for this vulnerability. #### FAQ for DNS Insufficient Socket Entropy Vulnerability - CVE-2008-1447 **What is the scope of the vulnerability?**  A spoofing vulnerability exists in Windows DNS client and DNS server. An attacker who successfully exploited this vulnerability could insert arbitrary addresses into the DNS cache. **What causes the vulnerability?**  The Windows DNS service in the Windows DNS client and DNS server does not provide enough entropy when performing DNS queries. **What is the Domain Name System (DNS)?** 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, such as www.microsoft.com, 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 article [what is DNS](http://technet2.microsoft.com/windowsserver/en/library/ff937311-03ce-4d04-b72c-b39c4d51cb361033.mspx). **What is DNS Cache?** Domain Name System (DNS) caching resolver service is a service that saves the responses to DNS queries so that the DNS server is not repeatedly queried for the same information. For more information, see the [DNSCache](http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentry/30643.mspx?mfr=true) Technet article or the [DNS Resolver Cache Service](http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/cnet/cnbc_imp_qxht.mspx?mfr=true) Technet article. See the [Attack detection](http://www.microsoft.com/technet/isa/2004/help/fw_alertattack.mspx?mfr=true) TechNet article for more information on DNS cache poisoning. **What might an attacker use the vulnerability to do?**  An attacker who has successfully exploited this vulnerability can insert arbitrary addresses into the DNS cache, also known as DNS cache poisoning. **How could an attacker exploit the vulnerability?** An attacker could send specific queries to a vulnerable DNS server or client, and at the same time respond back in a manner that allows the attacker to insert false or misleading DNS data. The attacker could then redirect Internet traffic from legitimate locations to an address of the attacker’s choice. **What systems are primarily at risk from the vulnerability?**  Any Windows system connected to a network or the Internet would be at risk. Windows Vista and Windows Server 2008 are not affected by this vulnerability. **What does the update do?** The update removes this vulnerability by using strongly random DNS transaction ID values and random UDP sockets for remote queries. **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. DNS Cache Poisoning Vulnerability - CVE-2008-1454 ------------------------------------------------- A cache poisoning vulnerability exists in Windows DNS Server. The vulnerability could allow an unauthenticated remote attacker to send specially crafted responses to DNS requests made by vulnerable systems, thereby poisoning the DNS cache and redirecting Internet traffic from legitimate locations. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2008-1454](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2008-1454). #### Mitigating Factors for DNS Cache Poisoning Vulnerability - CVE-2008-1454 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. - Microsoft has not identified any mitigations for this vulnerability. #### Workarounds for DNS Cache Poisoning Vulnerability - CVE-2008-1454 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 not identified any workarounds for this vulnerability. #### FAQ for DNS Cache Poisoning Vulnerability - CVE-2008-1454 **What is the scope of the vulnerability?**  A cache poisoning vulnerability exists in Windows DNS Server. An attacker who successfully exploited this vulnerability could insert false or misleading DNS data in the response to specific DNS requests, thereby redirecting Internet traffic. **What causes the vulnerability?**  Under certain conditions the DNS server accepts records from a response that is outside the remote server’s authority. **What is the Domain Name System (DNS)?** 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 address 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 article [What is DNS](http://technet2.microsoft.com/windowsserver/en/library/ff937311-03ce-4d04-b72c-b39c4d51cb361033.mspx). **What is DNS Cache?** Domain Name System (DNS) caching resolver service is a service that saves the responses to DNS queries so that the DNS server is not repeatedly queried for the same information. For more information, see the [DNSCache](http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentry/30643.mspx?mfr=true) Technet article or the [DNS Resolver Cache Service](http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/cnet/cnbc_imp_qxht.mspx?mfr=true) Technet article. See the [Attack detection](http://www.microsoft.com/technet/isa/2004/help/fw_alertattack.mspx?mfr=true) TechNet article for more information on DNS cache poisoning. **What might an attacker use the vulnerability to do?**  An attacker who successfully exploited this vulnerability could poison the DNS cache. **How could an attacker exploit the vulnerability?** An attacker who successfully exploited this vulnerability could insert false or misleading DNS data in the response to specific DNS requests, thereby redirecting Internet traffic. **What systems are primarily at risk from the vulnerability?**  Windows DNS servers are at risk. **What does the update do?**  The update removes the vulnerability by correcting internal DNS processing to avoid cache poisoning. **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. ### Update Information Detection and Deployment Tools and Guidance ------------------------------------------- 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](http://go.microsoft.com/fwlink/?linkid=69903). The [Microsoft TechNet Security Web site](http://go.microsoft.com/fwlink/?linkid=21132) provides additional information about security in Microsoft products. Security updates are available from [Microsoft Update](http://go.microsoft.com/fwlink/?linkid=40747), [Windows Update](http://go.microsoft.com/fwlink/?linkid=21130), and [Office Update](http://go.microsoft.com/fwlink/?linkid=21135). Security updates are also available from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?linkid=21129). 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](http://go.microsoft.com/fwlink/?linkid=96155). 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](http://go.microsoft.com/fwlink/?linkid=97900). **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](http://support.microsoft.com/kb/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](http://www.microsoft.com/technet/security/tools/mbsahome.mspx). The following table provides the MBSA detection summary for this security update. | Software | MBSA 2.1 | |-------------------------------------------------------------------------------------------------------------------|----------| | Microsoft Windows 2000 Service Pack 4 | Yes | | Windows XP Service Pack 2 and Windows XP Service Pack 3 | Yes | | Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Yes | | Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Yes | | Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Yes | | Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Yes | | Windows Server 2008 for 32-bit Systems | Yes | | Windows Server 2008 for x64-based Systems | Yes | For more information about MBSA 2.1, see [MBSA 2.1 Frequently Asked Questions](http://www.microsoft.com/technet/security/tools/mbsa2/qa.mspx). **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](http://go.microsoft.com/fwlink/?linkid=50120). **Systems Management Server** The following table provides the SMS detection and deployment summary for this security update. | Software | SMS 2.0 | SMS 2003 with SUSFP | SMS 2003 with ITMU | SCCM 2007 | |-------------------------------------------------------------------------------------------------------------------|---------|---------------------|--------------------------------------------|-----------| | Microsoft Windows 2000 Service Pack 4 | Yes | Yes | Yes | Yes | | Windows XP Service Pack 2 and Windows XP Service Pack 3 | Yes | Yes | Yes | Yes | | Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | No | No | Yes | Yes | | Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Yes | Yes | Yes | Yes | | Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | No | No | Yes | Yes | | Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | No | No | Yes | Yes | | Windows Server 2008 for 32-bit Systems | No | No | See **Note for Windows Server 2008** below | Yes | | Windows Server 2008 for x64-based Systems | No | No | See **Note for Windows Server 2008** below | Yes | 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](http://technet.microsoft.com/en-us/sms/bb676799.aspx). 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](http://update.microsoft.com/microsoftupdate) and that are supported by [Windows Server Update Services](http://go.microsoft.com/fwlink/?linkid=50120). For more information about the SMS 2003 ITMU, see [SMS 2003 Inventory Tool for Microsoft Updates](http://technet.microsoft.com/en-us/sms/bb676783.aspx). 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](http://technet.microsoft.com/en-us/sms/bb676786.aspx). See also [Downloads for Systems Management Server 2003](http://technet.microsoft.com/en-us/sms/bb676766.aspx). 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](http://technet.microsoft.com/en-us/library/bb735860.aspx). **Note for Windows Server 2008** Microsoft Systems Management Server 2003 with Service Pack 3 includes support for Windows Server 2008 manageability. For more information about SMS, visit the [SMS Web site](http://go.microsoft.com/fwlink/?linkid=21158). For more detailed information, see [Microsoft Knowledge Base Article 910723](http://support.microsoft.com/kb/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](http://technet2.microsoft.com/windowsvista/en/library/4279e239-37a4-44aa-aec5-4e70fe39f9de1033.mspx?mfr=true) components included with [Application Compatibility Toolkit 5.0](https://www.microsoft.com/download/details.aspx?familyid=24da89e9-b581-47b0-b45e-492dd6da2971&displaylang=en). 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. Security Update Deployment -------------------------- **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 For the DNS server update for Microsoft Windows 2000 Service Pack 4:
Windows2000-kb951746-x86-enu /quiet
For the DNS client update for Microsoft Windows 2000 Service Pack 4:
Windows2000-KB951748-V2-x86-ENU /quiet
Installing without restarting For the DNS server update for Microsoft Windows 2000 Service Pack 4:
Windows2000-kb951746-x86-enu /norestart
For the DNS client update for Microsoft Windows 2000 Service Pack 4:
Windows2000-KB951748-V2-x86-ENU /norestart
Update log file For the DNS server update for Microsoft Windows 2000 Service Pack 4:
kb951746.log
For the DNS client update for Microsoft Windows 2000 Service Pack 4:
kb951748-v2.log
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required? Yes, you must restart your system after you apply this security update
HotPatching Not applicable
Removal Information For the DNS server update 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%\$NTUninstallKB951746$\Spuninst folder
For the DNS client update 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%\$NTUninstallKB951748$-v2\Spuninst folder
File Information See Microsoft Knowledge Base Article 953230
Registry Key Verification For the DNS server update for Microsoft Windows 2000 Service Pack 4:  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\kb951746\Filelist
For the DNS client update for Microsoft Windows 2000 Service Pack 4:  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\kb951748-v2\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
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** 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](http://support.microsoft.com/kb/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** 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 intervention Windows XP Service Pack 2 and Windows XP Service Pack 3:
Windowsxp-kb951748-x86-enu /quiet
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-kb951748-x86-enu /quiet
Installing without restarting Windows XP Service Pack 2 and Windows XP Service Pack 3:
Windowsxp-kb951748-x86-enu /norestart
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-kb951748-x86-enu /norestart
Update log file kb951748.log
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required? Yes, you must restart your system after you apply this security update
HotPatching Not applicable
Removal Information Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallkb951748$\Spuninst folder
File Information See Microsoft Knowledge Base Article 953230
Registry Key Verification For Windows XP Service Pack 2 and Windows XP Service Pack 3:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\kb951748\Filelist
For 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\kb951748\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
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** 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](http://support.microsoft.com/kb/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** 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 intervention For the DNS server update for all supported 32-bit editions of Windows Server 2003:
Windowsserver2003-kb951746-x86-enu /quiet
For the DNS client update for all supported 32-bit editions of Windows Server 2003:
Windowsserver2003-kb951748-x86-enu /quiet
For the DNS server update for all supported x64-based editions of Windows Server 2003:
Windowsserver2003.WindowsXP-kb951746-x64-enu /quiet
For the DNS client update for all supported x64-based editions of Windows Server 2003:
Windowsserver2003.WindowsXP-kb951748-x64-enu /quiet
For the DNS server update for all supported Itanium-based editions of Windows Server 2003:
Windowsserver2003-kb951746-ia64-enu /quiet
For the DNS client update for all supported Itanium-based editions of Windows Server 2003:
Windowsserver2003-kb951748-ia64-enu /quiet
Installing without restarting For the DNS server update for all supported 32-bit editions of Windows Server 2003:
Windowsserver2003-kb951746-x86-enu /norestart
For the DNS client update for all supported 32-bit editions of Windows Server 2003:
Windowsserver2003-kb951748-x86-enu /norestart
For the DNS server update for all supported x64-based editions of Windows Server 2003:
Windowsserver2003.WindowsXP-kb951746-x64-enu /norestart
For the DNS client update for all supported x64-based editions of Windows Server 2003:
Windowsserver2003.WindowsXP-kb951748-x64-enu /norestart
For the DNS server update for all supported Itanium-based editions of Windows Server 2003:
Windowsserver2003-kb951746-ia64-enu /norestart
For the DNS client update for all supported Itanium-based editions of Windows Server 2003:
Windowsserver2003-kb951748-ia64-enu /norestart
Update log file For the DNS server update for Windows Server 2003: kb951746.log
For the DNS client update for Windows Server 2003: kb951748.log
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required? Yes, you must restart your system after you apply this security update.
HotPatching This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.
Removal Information For the DNS server update for Windows Server 2003, use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallkb951746$\Spuninst folder
For the DNS client update for Windows Server 2003, use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallkb951748$\Spuninst folder
File Information See Microsoft Knowledge Base Article 953230
Registry Key Verification For the DNS server update for Windows Server 2003: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\kb951746\Filelist
For the DNS client update for Windows Server 2003: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\kb951748\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](http://support.microsoft.com/kb/824994). For more information about the installer, visit the [Microsoft TechNet Web site](http://go.microsoft.com/fwlink/?linkid=38951). For more information about the terminology that appears in this bulletin, such as *hotfix*, see [Microsoft Knowledge Base Article 824684](http://support.microsoft.com/kb/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** 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](http://support.microsoft.com/kb/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** 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 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 For all supported 32-bit editions of Windows Server 2008:
Windows6.0-kb951746-x86 /quiet

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

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

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

For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-kb951746-ia64 /quiet /norestart
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required? Yes, you must restart your system after you apply this security update.
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.
File Information See Microsoft Knowledge Base Article 953230
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](http://support.microsoft.com/kb/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 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:

  • Dan Kaminsky of IOActive for reporting the DNS Insufficient Socket Entropy Vulnerability (CVE-2008-1447)

Support

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

Disclaimer

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

Revisions

  • V1.0 (July 8, 2008): Bulletin published.
  • V2.0 (July 10, 2008): Bulletin revised to inform users of ZoneAlarm and Check Point Endpoint Security of an Internet connectivity issue detailed in the section, Frequently Asked Questions (FAQ) Related to this Security Update. The revision did not change the security update files in this bulletin, but users of ZoneAlarm and Check Point Endpoint Security should read the FAQ entries for guidance.
  • V2.1 (July 23, 2008): Affected Software table revised to add MS06-064, MS07-062, and MS08-001 as bulletins replaced by this update.
  • V2.2 (July 25, 2008): Added three new known issues entries to Frequently Asked Questions (FAQ) Related to This Security Update.
  • V2.3 (January 13, 2009): Added a new entry to the Frequently Asked Questions (FAQ) Related to This Security Update section to communicate the fix to a detection and deployment issue with Windows XP Service Pack 3. There were no changes to the binaries or packages for this update. Customers who have successfully updated their systems do not need to reinstall this update.
  • V3.0 (December 8, 2009): Updated to communicate the rerelease of the security update for the DNS client on Microsoft Windows 2000 Service Pack 4 (KB951748). Also corrected the bulletin replacement information for this update. Customers who have previously installed this update need to reinstall the automatically reoffered update. No other updates are affected by this rerelease.
  • V3.1 (December 9, 2009): Corrected the registry key verification and removal information in the reference table for the DNS client on Microsoft Windows 2000 Service Pack 4 (KB951748). This is an informational change only.

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