Security Bulletin
Microsoft Security Bulletin MS09-008 - Important
Vulnerabilities in DNS and WINS Server Could Allow Spoofing (962238)
Published: March 10, 2009 | Updated: May 12, 2009
Version: 2.0
General Information
Executive Summary
This security update resolves two privately reported vulnerabilities and two publicly disclosed vulnerabilities in Windows DNS server and Windows WINS server. These vulnerabilities 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 Server, 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 correcting the way that Windows DNS servers cache and validate queries, and by modifying the way that Windows DNS servers and Windows WINS servers handle WPAD and ISATAP registration. 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 294781.
For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update at the earliest opportunity 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 962238 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
*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.
Non-Affected Software
| Operating System |
|---|
| Windows 2000 Professional Service Pack 4 |
| Windows XP Service Pack 2 and Windows XP Service Pack 3 |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 |
| 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 security bulletin revised on May 12, 2009?
Microsoft revised this security bulletin to remove MS08-066 as a bulletin replaced by this update to resolve a detection issue. The issue caused the MS08-066 update to not be correctly offered to affected systems running supported editions of Windows Server 2003 in a non-DNS server role. As a result of this change, the MS08-066 update may now be offered to affected systems running supported editions of Windows Server 2003 that have not previously been updated with MS08-066. Microsoft recommends that customers offered the MS08-066 update apply the update at the earliest opportunity.
Where are the file information details?
The file information details can be found in Microsoft Knowledge Base Article 962238.
Why does this bulletin contain two updates for each affected operating system?
This bulletin contains two updates, identified by KB number, for each affected operating system because the modifications that are required to address the vulnerabilities are located in separate components. Customers need to install security update package 961063 for each DNS server and 961064 for each WINS server in their environment.
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.
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
Severity Ratings and Vulnerability Identifiers
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 March bulletin summary. For more information, see Microsoft Exploitability Index.
| Affected Software | DNS Server Query Validation Vulnerability - CVE-2009-0233 | DNS Server Response Validation Vulnerability - CVE-2009-0234 | DNS Server Vulnerability in WPAD Registration Vulnerability- CVE-2009-0093 | WPAD WINS Server Registration Vulnerability - CVE-2009-0094 | Aggregate Severity Rating |
|---|---|---|---|---|---|
| Microsoft Windows 2000 Server Service Pack 4 | Important\ Spoofing | Important\ Spoofing | Important\ Spoofing | Important\ Spoofing | Important |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Important\ Spoofing | Important\ Spoofing | Important\ Spoofing | Important\ Spoofing | Important |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Important\ Spoofing | Important\ Spoofing | 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\ Spoofing | Important\ Spoofing | Important |
| Windows Server 2008 for 32-bit Systems* | Important\ Spoofing | Important\ Spoofing | Not applicable | Not applicable | Important |
| Windows Server 2008 for x64-based Systems* | Important\ Spoofing | Important\ Spoofing | Not applicable | Not applicable | 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. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.
DNS Server Query Validation Vulnerability - CVE-2009-0233
A spoofing vulnerability exists in Windows DNS server. This vulnerability could allow a remote unauthenticated attacker to quickly and reliably spoof responses and insert records into the DNS server's cache, thereby redirecting Internet traffic.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-0233.
Mitigating Factors for DNS Server Query Validation Vulnerability - CVE-2009-0233
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:
- Sites using SSL/TLS are not affected by this vulnerability.
Workarounds for DNS Server Query Validation Vulnerability - CVE-2009-0233
Microsoft has not identified any workarounds for this vulnerability.
FAQ for DNS Server Query Validation Vulnerability - CVE-2009-0233
What is the scope of the vulnerability?
A spoofing vulnerability exists in Windows DNS server. An attacker who successfully exploited this vulnerability could insert arbitrary addresses into the DNS cache.
What causes the vulnerability?
Windows DNS server does not cache specific responses to specially crafted queries, thereby allowing greater predictability of subsequent transaction IDs used by the DNS server.
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.
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 TechNet article or the DNS Resolver Cache Service TechNet article. See the Attack detection 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 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?
Windows DNS servers are at risk from this vulnerability.
What does the update do?
The update removes this vulnerability by correcting the way that Windows DNS server validates specifically crafted 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 Server Response Validation Vulnerability - CVE-2009-0234
A response validation vulnerability exists in Windows DNS Server. The vulnerability could allow an unauthenticated remote attacker to send specially crafted queries to a DNS server so as to allow greater predictability of transaction IDs used by the DNS server and thus to redirect Internet traffic from legitimate locations.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-0234.
Mitigating Factors for DNS Server Response Validation Vulnerability - CVE-2009-0234
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:
- Sites using SSL/TLS are not affected by this vulnerability.
Workarounds for DNS Server Response Validation Vulnerability - CVE-2009-0234
Microsoft has not identified any workarounds for this vulnerability.
FAQ for DNS Server Response Validation Vulnerability - CVE-2009-0234
What is the scope of the vulnerability?
A spoofing vulnerability exists in Windows DNS server. This vulnerability could allow a remote unauthenticated attacker to have greater predictability of transaction IDs used by the DNS server, and thus facilitate DNS cache poisoning and redirection of Internet traffic.
What causes the vulnerability?
Windows DNS server does not correctly cache specially crafted DNS responses. This results in the DNS server making unnecessary lookups and leads to greater predictability of subsequent transaction IDs used by the DNS server.
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.
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 TechNet article or the DNS Resolver Cache Service TechNet article. See the Attack detection 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 in conjunction with other DNS cache vulnerabilities could poison the DNS cache and redirect internet traffic.
How could an attacker exploit the vulnerability?
An attacker who successfully exploited this vulnerability could send multiple specifically crafted queries to the DNS server. As a result, the DNS server would make unnecessary lookups and thereby allow for greater predictability of subsequent transaction IDs used by the server.
What systems are primarily at risk from the vulnerability?
Windows DNS servers are at risk from this vulnerability.
What does the update do?
The update removes this vulnerability by correcting the way that Windows DNS servers cache and validate responses.
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 Server Vulnerability in WPAD Registration Vulnerability- CVE-2009-0093
A man-in-the-middle attack vulnerability exists in Windows DNS servers where dynamic update is used and ISATAP and WPAD are not already registered in DNS. This vulnerability could allow a remote authenticated attacker to spoof a web proxy thereby redirect Internet traffic to an address of the attacker’s choice.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-0093.
Mitigating Factors for DNS Server Vulnerability in WPAD Registration Vulnerability- CVE-2009-0093
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.
- If WPAD and ISATAP is already registered on DNS it will not be possible for an attacker to register WPAD as well.
Workarounds for DNS Server Vulnerability in WPAD Registration Vulnerability- CVE-2009-0093
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:
Create a WPAD.DAT Proxy Auto Configuration File on a Host Named WPAD in Your Organization to Direct Web Browsers to Your Organization’s Proxy
To create a WPAD.DAT proxy auto configuration file, follow these steps:
- Create a WPAD.DAT file that adheres to the Proxy auto-config specification. For more information on Proxy Auto-Configuration (PAC) files including a sample file, see the following MSDN article.
- Place the WPAD.DAT file in the root directory of a web server in your organization and ensure the file can be requested anonymously.
- Create a MIME type for the WPAD.DAT file on the web server of "application/x-ns-proxy-autoconfig".
- Create the appropriate entries in your organizations DHCP or DNS server to allow discovery of the WPAD server.
For information on how to register WPAD, see Microsoft Knowledgebase Article 934864.
Impact of workaround. None
FAQ for DNS Server Vulnerability in WPAD Registration Vulnerability- CVE-2009-0093
What is the scope of the vulnerability?
A spoofing vulnerability exists in Windows DNS server. An attacker who successfully exploited this vulnerability could redirect Internet traffic.
What causes the vulnerability?
The Windows DNS server does not correctly validate who can register WPAD entries on the DNS server. By default a DNS server will allow any user to create a registration in the DNS database for WPAD if the name registration does not already exist.
What is Web Proxy Auto-Discovery (WPAD)?
The Web Proxy Auto-Discovery (WPAD) feature enables web clients to automatically detect proxy settings without user intervention. The WPAD feature prepends the hostname "wpad" to the fully-qualified domain name and progressively removes subdomains until it finds a WPAD server answering the domain name. For more information, see WinHTTP AutoProxy Support.
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.
What is Dynamic Update?
Dynamic update enables DNS client computers to register and dynamically update their resource records with a DNS server whenever changes occur. This reduces the need for manual administration of zone records, especially for clients that frequently move or change locations and use DHCP to obtain an IP address. For more information, see the dynamic update TechNet article.
What is ISATAP?
The Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) provides IPv6 connectivity within an IPv4 Intranet. For information on ISATAP, see RFC4214: Intra-Site Automatic Tunnel Addressing Protocol (ISATAP).
What might an attacker use the vulnerability to do?
An attacker who has successfully exploited this vulnerability could spoof the legitimate web proxy and intercept or redirect internet traffic.
How could an attacker exploit the vulnerability?
If an attacker registers "WPAD" in the DNS database and points it to an IP address that the attacker controls, it would allow the attacker to conduct man-in-the-middle (MITM) attacks against any browsers configured to use WPAD to discover proxy server settings.
What systems are primarily at risk from the vulnerability?
Windows DNS servers are at risk from the vulnerability.
What does the update do?
The update removes this vulnerability by modifying the way that Windows DNS servers respond to WPAD name resolution requests.
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-0093.
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.
WPAD WINS Server Registration Vulnerability - CVE-2009-0094
A man-in-the-middle attack vulnerability exists in Windows WINS servers. This vulnerability could allow a remote authenticated attacker to spoof a web proxy and thereby redirect Internet traffic to an address of the attacker’s choice.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-0094.
Mitigating Factors for WPAD WINS Server Registration Vulnerability - CVE-2009-0094
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.
- If WINS server already has WPAD and ISATAP registered than an attacker will not be able to register these as well.
Workarounds for WPAD WINS Server Registration Vulnerability - CVE-2009-0094
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:
Create a WPAD.DAT Proxy Auto Configuration File on a Host Named WPAD in Your Organization to Direct Web Browsers to Your Organization’s Proxy
To create a WPAD.DAT proxy auto configuration file, follow these steps:
- Create a WPAD.DAT file that adheres to the Proxy auto-config specification. For more information on Proxy Auto-Configuration (PAC) files including a sample file, see the following MSDN article.
- Place the WPAD.DAT file in the root directory of a web server in your organization and ensure the file can be requested anonymously.
- Create a MIME type for the WPAD.DAT file on the web server of "application/x-ns-proxy-autoconfig".
- Create the appropriate entries in your organizations DHCP or DNS server to allow discovery of the WPAD server.
For information on how to register WPAD, see Microsoft Knowledgebase Article 934864.
Impact of workaround. None
FAQ for WPAD WINS Server Registration Vulnerability - CVE-2009-0094
What is the scope of the vulnerability?
A spoofing vulnerability exists in Windows WINS server. An attacker who successfully exploited this vulnerability could redirect internet traffic.
What causes the vulnerability?
The Windows WINS server does not correctly validate who can register WPAD or ISATAP entries on the WINS server. By default a WINS server will allow any user to create a registration in the WINS database for WPAD or ISATAP if the name registration does not already exist.
What is Web Proxy Auto-Discovery (WPAD)?
The Web Proxy Auto-Discovery (WPAD) feature enables web clients to automatically detect proxy settings without user intervention. The WPAD feature prepends the hostname "wpad" to the fully-qualified domain name and progressively removes subdomains until it finds a WPAD server answering the domain name. For more information see WinHTTP AutoProxy Support.
What is WINS?
WINS was designed specifically to support NetBIOS over TCP/IP (NetBT). WINS is required for any environment in which users access resources that have NetBIOS names. If you do not use WINS in such a network, you cannot connect to a remote network resource by using its NetBIOS name unless you use Lmhosts files, and you might be unable to establish file and print sharing connections. For more information, see the WINS TechNet article.
What is ISATAP?
The Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) provides IPv6 connectivity within an IPv4 Intranet. For information on ISATAP, see RFC4214: Intra-Site Automatic Tunnel Addressing Protocol (ISATAP).
What might an attacker use the vulnerability to do?
An attacker who has successfully exploited this vulnerability could spoof the legitimate web proxy or ISATAP route and intercept or redirect Internet traffic.
How could an attacker exploit the vulnerability?
If an attacker registers WPAD or ISATAP in the WINS database and points it to an IP address they control, it would allow the attacker to conduct man-in-the-middle (MITM) attacks against any browsers configured to use WPAD to discover proxy server settings.
What systems are primarily at risk from the vulnerability?
Windows WINS servers are at risk from the vulnerability.
What does the update do?
The update removes this vulnerability by modifying the way that Windows WINS servers responds to WPAD and ISATAP name resolution requests.
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-0094.
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. 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 Server Service Pack 4 | 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.
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.
| Software | SMS 2.0 | SMS 2003 with SUSFP | SMS 2003 with ITMU | Configuration Manager 2007 |
|---|---|---|---|---|
| Microsoft Windows 2000 Server Service Pack 4 | Yes | Yes | 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.
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 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.
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.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Windows 2000 Server (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 | DNS server on Microsoft Windows 2000 Server Service Pack 4:\ Windows2000-KB961063-x86-enu /quiet\ \ WINS server on Microsoft Windows 2000 Server Service Pack 4:\ Windows2000-KB961064-x86-enu /quiet |
| Installing without restarting | DNS server on Microsoft Windows 2000 Server Service Pack 4:\ Windows2000-KB961063-x86-enu /norestart\ \ WINS server on Microsoft Windows 2000 Server Service Pack 4:\ Windows2000-KB961064-x86-enu /norestart |
| Update log file | DNS server on Microsoft Windows 2000 Server Service Pack 4:\ kb961063.log\ \ WINS server on Microsoft Windows 2000 Server Service Pack 4:\ kb961064.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 | DNS server on Microsoft Windows 2000 Server Service Pack 4:\ Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%$NTUninstallKB961063$\Spuninst folder\ \ WINS server on Microsoft Windows 2000 Server Service Pack 4:\ Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%$NTUninstallKB961064$\Spuninst folder |
| File Information | See Microsoft Knowledge Base Article 962238 |
| Registry Key Verification | DNS server on Microsoft Windows Service Pack 4: \ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB961063\Filelist\ \ WINS server on Microsoft Windows Service Pack 4: \ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB961064\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.
| 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.
Removing the Update
This security update supports the following setup 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.- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- 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.
- 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 | DNS server on all supported 32-bit editions of Windows Server 2003:\ Windowsserver2003-kb961063-x86-enu /quiet\ \ WINS server on all supported 32-bit editions of Windows Server 2003:\ Windowsserver2003-kb961064-x86-enu /quiet |
| DNS server on all supported x64-based editions of Windows Server 2003:\ Windowsserver2003.WindowsXP-KB961063-x64-enu /quiet\ \ WINS server on all supported x64-based editions of Windows Server 2003:\ Windowsserver2003.WindowsXP-KB961064-x64-enu /quiet | |
| DNS server on all supported Itanium-based editions of Windows Server 2003:\ Windowsserver2003-KB961063-ia64-enu /quiet\ \ WINS server on all supported Itanium-based editions of Windows Server 2003:\ Windowsserver2003-KB961064-ia64-enu /quiet | |
| Installing without restarting | DNS server on all supported 32-bit editions of Windows Server 2003:\ Windowsserver2003-kb961063-x86-enu /norestart\ \ WINS server on all supported 32-bit editions of Windows Server 2003:\ Windowsserver2003-kb961064-x86-enu /norestart |
| DNS server on all supported x64-based editions of Windows Server 2003:\ Windowsserver2003.WindowsXP-KB961063-x64-enu /norestart\ \ WINS server on all supported x64-based editions of Windows Server 2003:\ Windowsserver2003.WindowsXP-KB961064-x64-enu /norestart | |
| DNS server on all supported Itanium-based editions of Windows Server 2003:\ Windowsserver2003-KB961063-ia64-enu /norestart\ \ WINS server on all supported Itanium-based editions of Windows Server 2003:\ Windowsserver2003-KB961064-ia64-enu /norestart | |
| Update log file | KB961063.log\ KB961064.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 | DNS server on Windows Server 2003:\ Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%$NTUninstallKB961063$\Spuninst folder\ \ WINS server on Windows Server 2003:\ Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%$NTUninstallKB961064$\Spuninst folder |
| File Information | See Microsoft Knowledge Base Article 962238 |
| Registry Key Verification | DNS server on all supported editions of Windows Server 2003:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB961063\Filelist\ \ WINS server on all supported editions of Windows Server 2003:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB961064\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.
| 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.
Removing the Update
This security update supports the following setup 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.- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- 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.
- 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 | DNS server on all supported 32-bit editions of Windows Server 2008:\ Windows6.0-KB961063-x86 /quiet |
| DNS server on all supported x64-based editions of Windows Server 2008:\ Windows6.0-KB961063-x64 /quiet | |
| Installing without restarting | DNS server on all supported 32-bit editions of Windows Server 2008:\ Windows6.0-KB961063-x86 /quiet /norestart |
| DNS server on all supported x64-based editions of Windows Server 2008:\ Windows6.0-KB961063-x64 /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 962238 |
| 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.
| 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.
- Click Start and then enter an update file name in Start Search.
- When the file appears under Programs, right-click on the file name and click Properties.
- Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- 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.
- 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:
- Kevin Day for working with us on the DNS Server Query Vulnerability (CVE-2009-0233) and the DNS Server Response Validation Vulnerability (CVE-2009-0234)
- Dave Dagon of Georgia Tech Information Security Center for working with us on the DNS Server Query Vulnerability (CVE-2009-0233) and the DNS Server Response Validation Vulnerability (CVE-2009-0234)
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 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 (March 10, 2009): Bulletin published.
- V1.1 (March 11, 2009): Clarified that CVE-2009-0093 does not apply to supported editions of Windows Server 2008. Added a link to Microsoft Knowledge Base Article 962238 under Known Issues in the Executive Summary. Clarified what systems are primarily at risk for CVE-2009-2033. Finally, updated a finder acknowledgment for CVE-2009-0233 and CVE-2009-0234.
- V2.0 (May 12, 2009): Added an entry in the section, Frequently Asked Questions (FAQ) Related to This Security Update, explaining a detection change. As a result of this change, the MS08-066 update may be offered to affected systems running supported editions of Windows Server 2003 in a non-DNS server role. Microsoft recommends that customers offered the MS08-066 update apply the update at the earliest opportunity.
Built at 2014-04-18T13:49:36Z-07:00