TechNet Home > TechNet Security > Bulletins

Microsoft Security Bulletin MS07-029

Vulnerability in Windows DNS RPC Interface Could Allow Remote Code Execution (935966)

Published: May 8, 2007 | Updated: June 6, 2007

Version: 1.2

Summary

Who Should Read this Document: Customers who use Microsoft Windows

Impact of Vulnerability: Remote Code Execution

Maximum Severity Rating: Critical

Recommendation: Customers should apply the update immediately

Security Update Replacement: None

Caveats: None

Tested Software and Security Update Download Locations:

Affected Software:

•	Microsoft Windows 2000 Server Service Pack 4 — Download the update
•	Microsoft Windows Server 2003 Service Pack 1 and Microsoft Windows Server 2003 Service Pack 2 — Download the update
•	Microsoft Windows Server 2003 with SP1 for Itanium-based Systems and Microsoft Windows Server 2003 with SP2 for Itanium-based Systems — Download the update
•	Microsoft Windows Server 2003 x64 Edition and Microsoft Windows Server 2003 x64 Edition Service Pack 2 — Download the update

Non-Affected Software:

•	Microsoft Windows 2000 Professional Service Pack 4
•	Microsoft Windows XP Service Pack 2
•	Microsoft Windows XP Professional x64 Edition and Microsoft Windows XP Professional x64 Edition Service Pack 2
•	Windows Vista
•	Windows Vista x64 Edition

The software in this list has been tested to determine whether the versions are affected. Other versions are either past their support life cycle or are not affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

Top of section

General Information

Executive Summary

Executive Summary:

This update resolves a publicly disclosed vulnerability. The vulnerability is documented in its own subsection in the Vulnerability Details section of this bulletin.

An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

We recommend that customers apply the update immediately.

Severity Ratings and Vulnerability Identifiers:

Vulnerability Identifiers	Impact of Vulnerability	Windows 2000 Server Service Pack 4	Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2	Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems	Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2
DNS RPC Management Vulnerability - CVE-2007-1748	Remote Code Execution	Critical	Critical	Critical	Critical

This assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.

Note The DNS Server Service may not be enabled by default in certain server role configurations. In server configurations where it is not enabled by default the bulletin severity it is considered Important. The Bulletin severity of Critical is reserved for Domain Controller with DNS Server Functionality, DNS Server, Microsoft Small Business Server, and Server role configurations where the DNS Server Service is enabled by default..

Top of section

Frequently Asked Questions (FAQ) Related to This Security Update

I am using an older version of the software discussed in this security bulletin; what should I do?
Theaffected software listed in this bulletin has been tested to determine whether the versions are affected. Other versions are past their support life cycle. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

It should be a priority for customers who have older versions of the software to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.

Customers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.

Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?
The following table provides the MBSA detection summary for this security update.

Product	MBSA 1.2.1	MBSA 2.0.1
Microsoft Windows 2000 Server Service Pack 4	Yes	Yes
Microsoft Windows Server 2003 Service Pack 1 and Microsoft Windows Server 2003 Service Pack 2	Yes	Yes
Microsoft Windows Server 2003 with SP1 for Itanium-based Systems and Microsoft Windows Server 2003 with SP2 for Itanium-based Systems	No	Yes
Microsoft Windows Server 2003 x64 Edition and Microsoft Windows Server 2003 x64 Edition Service Pack 2	No	Yes

For more information about MBSA, visit the MBSA Web site. For more information about the software that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.

Can I use Systems Management Server (SMS) to determine whether this update is required?
The following table provides the SMS detection summary for this security update.

Product	SMS 2.0	SMS 2003
Microsoft Windows 2000 Server Service Pack 4	Yes	Yes
Microsoft Windows Server 2003, Microsoft Windows Server 2003 Service Pack 1, and Microsoft Windows Server 2003 Service Pack 2	Yes	Yes
Microsoft Windows Server 2003 with SP1 for Itanium-based Systems and Microsoft Windows Server 2003 with SP2 for Itanium-based Systems	No	Yes
Microsoft Windows Server 2003 x64 Edition and Microsoft Windows Server 2003 x64 Edition Service Pack 2	No	Yes

SMS 2.0 and SMS 2003 Software Update Services (SUS) Feature Pack can use MBSA 1.2.1 for detection and therefore have the same limitation that is listed earlier in this bulletin related to programs that MBSA 1.2.1 does not detect.

For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about SUIT, visit the following Microsoft Web site. For more information about the limitations of SUIT, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

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, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

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.

Top of section

Vulnerability Details

DNS RPC Management Vulnerability - CVE-2007-1748:

A remote code execution vulnerability exists in the Domain Name System (DNS) Server Service in all supported server versions of Windows that could allow an attacker who successfully exploited this vulnerability to take complete control of the affected system.

Mitigating Factors for DNS RPC Management Vulnerability - CVE-2007-1478:

The DNS Server Service may not be enabled by default in certain server role configurations. On Domain Controller with DNS Server Functionality, DNS Server, and Microsoft Small Business Server configurations the DNS Server Service is enabled by default.

Top of section

Workarounds for DNS RPC Management Vulnerability - CVE-2007-1748:

Microsoft has tested the following workarounds. While the workaround will not correct the underlying vulnerability, it helps block known attack vectors. Specifically, all these workarounds have been tested and shown to block attempts to exploit the vulnerability over RPC traffic as well as port 139 and 445. When a workaround reduces functionality, it is identified in the following section.

•

Disable remote management over RPC capability for DNS Servers through the registry key setting.

Note Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in regedit.exe.

Note We recommend backing up the registry before you edit it.

1.	On the start menu click 'Run' and then type 'Regedit' and then press ENTER.
2.	Navigate to the following registry location: “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters”.
3.	On the 'Edit' menu select 'New' and then click 'DWORD Value'.
4.	Where 'New Value #1' is highlighted type 'RpcProtocol' for the name of the value and then press ENTER.
5.	Double-click on the newly created value and change the value's data to '4' (without the quotes).
6.	Restart the DNS service for the change to take effect.

•

Managed Deployment Script

The following sample registry script can be used to enable this registry setting:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters]
"RpcProtocol"=dword:00000004

The above registry script can be saved to a file with a .REG file extension and can be deployed silently as part of an automated deployment script using regedit.exe using the /s command line switch.

The DNS service needs to be restarted for this change to take effect.

For help using regedit.exe to deploy registry scripts please refer to Microsoft Knowledge Base Article Q82821: Registration Info Editor (REGEDIT) Command-Line Switches.

How to undo workaround: To undo the workaround perform the following steps:

1.	On the start menu click 'Run' and then type 'Regedit' and then press ENTER.
2.	Navigate to the following registry location: “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters”.
3.	Select Registry Key RpcProtocol.
4.	Right click on the RpcProtocol Key and select Delete.
5.	Restart the DNS service for the change to take effect.

RpcProtocol registry key values

The value ‘4’ being used above restricts the DNS RPC interface to local procedure calls (LPC) only. This allows for local management only.

The following values are available for the RpcProtocol registry entry:

•

0x1 - This value corresponds to a setting of DNS_RPC_USE_TCPIP #define DNS_RPC_USE_NAMED_PIPE0x2

•

0x2 - This value corresponds to a setting of DNS_RPC_USE_NAMED_PIPE

•

0x4 - This value corresponds to a setting of DNS_RPC_USE_LPC

•

Disable the capacity for remote management over RPC

You can re-configure the DNS server’s management interface to accept only LPC by setting a value in the registry. Other registry values will modify or disable RPC communication differently. For more information on the RpcProtocol registry key please see the following TechNet article.

•	Setting the value to 4 will mitigate a remote attempt to exploit the vulnerability
•	Setting the value to 0 will disable all DNS RPC functionality and will protect against both local and remote attempts to exploit the vulnerability.

Impact of Workaround: Setting the registry value to 4 will disable remote management and configuration of DNS server functionality using RPC or WMI. DNS management tools, will fail to work remotely. Local management and remote management through terminal services can be still used to manage your DNS Server configuration.

You will still be able to use the DNS management MMC Snap-in, DNSCMD.exe, and the DNS WMI provider if they are run locally from the server.

Setting the registry value to 0 will disable all DNS RPC management capability including local administration and configuration.

DNS Server local administration and configuration may not work if the server being managed has a computer name of 15 characters and is selected by its computer name. To avoid this issue, use the Fully Qualified Domain Name (FQDN) of the computer being managed in the DNS administration tools.

•

Block the following at the firewall:

Block TCP and UDP port 445 and 139 as well as all unsolicited inbound traffic on ports greater than 1024.

The RPC interface of Windows DNS is bound to a port greater than 1024. While the majority of RPC port binding occurs between the 1024 to 5000 range it is possible for the RPC interface to bind to higher unreserved port numbers. Blocking them at the firewall will help protect systems that are behind that firewall from attempts to exploit this vulnerability. We recommend that you block all unsolicited inbound communication from the Internet to help prevent attacks that may use other ports. For more information about ports that RPC uses, visit the following Web site. To block all unsolicited RPC requests while preserving DNS management functionality please see Microsoft Knowledge Base Article 555381.

NoteAn attacker would need to authenticate using a valid username and password to exploit the vulnerability using ports 139 or 445.

Impact of Workaround: Remote management of DNS server functionality using RPC will be disabled. DNS management tools, will fail to work remotely. Local and remote management through terminal services can be still used to manage your DNS Server configuration.

This includes the DNS management MMC Snap-in, DNSCMD.exe, DNS WMI provider. Additional management and control functionality may be lost for applications or components that use the affected ports.

Blocking port 445 will prevent computers from connecting to the server through SMB, and prevent servers from accessing shared network folders. Management tools that depend on SMB for connectivity will be unable to connect to the server.

•

Enable advanced TCP/IP filtering on systems

You can enable advanced TCP/IP filtering to block all unsolicited inbound traffic. For more information about how to configure TCP/IP filtering, see Microsoft Knowledge Base Article 309798.

•

Block TCP and UDP port 445 and 139 as well as affected ports greater than 1024 by using IPsec on the affected systems

Use Internet Protocol security (IPsec) to help protect network communications. Detailed information about IPsec and about how to apply filters is available in Microsoft Knowledge Base Article 313190 and Microsoft Knowledge Base Article 813878.

Note An attacker will need to authenticate using a valid username and password to exploit the vulnerability using ports 139 or 445.

This includes the DNS management MMC Snap-in, DNSCMD.exe, and the DNS WMI provider. Additional management and control functionality may be lost for applications or components that use affected ports.

Blocking port 445 will prevent computers connecting to the server through SMB as well as the server will being unable to access folders shared on the network. Management tools that depend on SMB for connectivity will be unable to connect to the server.

Top of section

FAQ for DNS RPC Management Vulnerability - CVE-2077-1748:

What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could remotely take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability?
A stack-based buffer overrun exists in the Remote Procedure Call (RPC) Management Interface in the Windows Domain Name System (DNS) Server service.

What is Remote Procedure Call (RPC)?
Remote Procedure Call (RPC) is a protocol that a program can use to request a service from a program located on another computer in a network. RPC helps with interoperability because the program using RPC does not have to understand the network protocols that are supporting communication. In RPC, the requesting program is the client and the service-providing program is the server.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.

How could an attacker exploit the vulnerability?
On servers running the DNS Server Service on all supported server versions of Windows, an anonymous attacker could try to exploit the vulnerability by sending a specially crafted RPC packet to an affected system. The vulnerability could allow an attacker to run code in the security context of the Domain Name System Server Service, which by default runs as Local SYSTEM.

What systems are primarily at risk from the vulnerability?
DNS Servers, Domain Controllers and Small Business Servers are primarily at risk. These systems could be at more risk if they are placed on untrusted networks where unsolicited PRC management traffic permitted However, firewall best practices strongly discourage allowing this.

Could the vulnerability be exploited over the Internet?
Yes. An attacker could try to exploit this vulnerability over the Internet. Firewall best practices and standard default firewall configurations can help protect against attacks that originate from the Internet.

What does the update do?
The update removes the vulnerability by modifying the way that RPC validates the length of a message before it passes the message to the allocated buffer.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CVE-2007-1748.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
Yes. When the security bulletin was released, Microsoft had received information that this vulnerability was being exploited.

Does this security update remove or roll back any of the mitigation listed in Microsoft Security Advisory (935964)?
No. This security update does not remove or undo any of the mitigations recommended in Microsoft Security Advisory (935964) Vulnerability in RPC on Windows DNS Server Could Allow Remote Code Execution . If any of the mitigations were deployed as recommended in the Advisory, users may manually remove them after the successful installation of the security update.

Does applying this security update help protect customers from the code that has been published publicly that attempts to exploit this vulnerability?
Yes. This security update addresses the vulnerability that is currently being exploited. The vulnerability that has been addressed has been assigned the Common Vulnerability and Exposure number CVE-2007-1748.

Top of section

Security Update Information

Affected Software:

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

Windows 2000 (all versions)

Prerequisites
For Windows 2000, this security update requires Service Pack 4 (SP4). For Small Business Server 2000, this security update requires Small Business Server 2000 Service Pack 1a (SP1a) or Small Business Server 2000 running with Windows 2000 Server Service Pack 4 (SP4).This security update also requires that the system be a DNS Server or makes use of DNS Server functionality.

The software that is listed has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

For more information about how to obtain the latest service pack, see Microsoft Knowledge Base Article 260910.

Inclusion in Future Service Packs
There are no more service packs planned for this operating system. The update for this issue may be included in a future update rollup.

Installation Information

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 forces other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Displays a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart	Display a dialog box prompting the local user to allow a restart.
Special Options
/overwriteoem	Overwrites OEM files without prompting.
/nobackup	Does not back up files needed for uninstallation.
/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. For more information about the Update.exe 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.

Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for Windows 2000 Service Pack 4:

Windows2000-kb935966-x86-enu /quiet

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

To install the security update without forcing the system to restart, use the following command at a command prompt for Windows 2000 Service Pack 4:

Windows2000-kb935966-x86-enu /norestart

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

Restart Requirement

This update requires a restart.

Removal Information

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

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

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 forces other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Displays a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart	Display a dialog box prompting the local user to allow a restart.
Special Options
/forceappsclose	Forces other programs to close when the computer shuts down.
/log:path	Allows the redirection of installation log files.

File Information

The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Windows 2000 Service Pack 4 and Small Business Server 2000:

File Name	Version	Date	Time	Size	Folder
dns.exe	5.0.2195.7135	13-Apr-2007	15:18	327,952	.

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 frequently asked question, “Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?” in the section, Frequently Asked Questions (FAQ) Related to This Security Update, earlier in this bulletin.

•

File Version Verification

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

1.	Click Start, and then click Search.
2.	In the Search Results pane, click All files and folders under Search Companion.
3.	In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
4.	In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
5.	On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table. Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

•

Registry Key Verification

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

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

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

Top of section

Windows Server 2003 (all versions)

Prerequisites
This security update requires Windows Server 2003 Service Pack 1, Windows Server 2003 Service Pack 2, Windows Server 2003 for Itanium-based Systems, Windows Server 2003 with SP1 for Itanium-based Systems, Windows Server 2003 with SP2 for Itanium-based Systems, Windows Server 2003 x64 Edition, or Windows Server 2003 x64 Edition Service Pack 2. This security update also requires that the system be a DNS Server or makes use of DNS Server functionality.

Inclusion in Future Service Packs
The update for this issue will be included in future service pack or update rollup.

Installation Information

This security update supports the following setup switches.

Supported Security Update Installation Switches
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 forces other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Displays a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart	Display a dialog box prompting the local user to allow a restart.
Special Options
/overwriteoem	Overwrites OEM files without prompting.
/nobackup	Does not back up files needed for uninstallation.
/forceappsclose	Forces other programs to close when the computer shuts down.
/log: path	Allows the redirection of installation log files.
/integrate:path	Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path]	Extracts files without starting the Setup program.
/ER	Enables extended error reporting.
/verbose	Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

Deployment Information

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

Windowsserver2003-kb935966-x86-enu /quiet

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

Windowsserver2003-kb935966-x86-enu /norestart

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

Restart Requirement

You must restart your system after you apply this security update.

This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.

Note Not all security updates support HotPatching, and some security updates that support HotPatching might require that you restart the server after you install the security update. HotPatching is only supported if the files being replaced by the security update are General Distribution Release (GDR) files. HotPatching is not supported if you have previously installed a hotfix to update one of the files included in the security update. For more information about this behavior, see Microsoft Knowledge Base Article 897341and Microsoft Knowledge Base Article 824994.

Removal Information

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

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

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 forces other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Displays a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart	Display a dialog box prompting the local user to allow a restart.
Special Options
/forceappsclose	Forces other programs to close when the computer shuts down.
/log:path	Allows the redirection of installation log files.

File Information

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

File Name	Version	Date	Time	Size	Folder
dns.exe	5.2.3790.2915	12-Apr-2007	12:57	442,880	SP1GDR
dns.exe	5.2.3790.2915	12-Apr-2007	12:56	443,392	SP1QFE
w03a2409.dll	5.2.3790.2925	26-Apr-2007	10:54	27,648	SP1QFE
dns.exe	5.2.3790.4059	12-Apr-2007	13:40	443,392	SP2GDR
dns.exe	5.2.3790.4059	12-Apr-2007	13:27	443,392	SP2QFE
w03a2409.dll	5.2.3790.4069	26-Apr-2007	18:02	453,632	SP2QFE

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

File Name	Version	Date	Time	Size	CPU	Folder
dns.exe	5.2.3790.2915	27-Apr-2007	13:13	1,122,816	IA-64	SP1GDR
wdns.exe	5.2.3790.2915	27-Apr-2007	13:13	442,880	X86	SP1GDR\wow
dns.exe	5.2.3790.2915	27-Apr-2007	13:13	1,124,864	IA-64	SP1QFE
w03a2409.dll	5.2.3790.2925	27-Apr-2007	13:13	26,624	IA-64	SP1QFE
wdns.exe	5.2.3790.2915	27-Apr-2007	13:13	443,392	X86	SP1QFE\wow
ww03a2409.dll	5.2.3790.2925	27-Apr-2007	13:13	27,648	X86	SP1QFE\wow
dns.exe	5.2.3790.4059	27-Apr-2007	13:17	1,124,864	IA-64	SP2GDR
dns.exe	5.2.3790.4059	27-Apr-2007	13:12	1,125,376	IA-64	SP2QFE
w03a2409.dll	5.2.3790.4069	27-Apr-2007	13:12	452,608	IA-64	SP2QFE
ww03a2409.dll	5.2.3790.4069	27-Apr-2007	13:12	453,632	X86	SP2QFE\wow

Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; Windows Server 2003, Datacenter x64 Edition; Windows Server 2003 R2, Standard x64 Edition; Windows Server 2003 R2, Enterprise x64 Edition; Windows Server 2003 R2, Datacenter x64 Edition; Windows Server 2003 with SP2, Standard x64 Edition; Windows Server 2003 with SP2, Enterprise x64 Edition; Windows Server 2003 with SP2, Datacenter x64 Edition; Windows Server 2003 R2, Standard x64 Edition with SP2; Windows Server 2003 R2, Enterprise x64 Edition with SP2; and Windows Server 2003 R2, Datacenter x64 Edition with SP2:

File Name	Version	Date	Time	Size	CPU	Folder
dns.exe	5.2.3790.2915	27-Apr-2007	13:11	758,272	X64	SP1GDR
wdns.exe	5.2.3790.2915	27-Apr-2007	13:11	442,880	X86	SP1GDR\wow
dns.exe	5.2.3790.2915	27-Apr-2007	13:12	760,832	X64	SP1QFE
w03a2409.dll	5.2.3790.2925	27-Apr-2007	13:12	28,160	X64	SP1QFE
wdns.exe	5.2.3790.2915	27-Apr-2007	13:12	443,392	X86	SP1QFE\wow
ww03a2409.dll	5.2.3790.2925	27-Apr-2007	13:12	27,648	X86	SP1QFE\wow
dns.exe	5.2.3790.4069	27-Apr-2007	13:16	759,808	X64	SP2GDR
dns.exe	5.2.3790.4069	27-Apr-2007	13:11	760,832	X64	SP2QFE
w03a2409.dll	5.2.3790.4069	27-Apr-2007	13:11	454,144	X64	SP2QFE
ww03a2409.dll	5.2.3790.4069	27-Apr-2007	13:11	453,632	X86	SP2QFE\wow

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

If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, 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 this behavior, see Microsoft Knowledge Base Article 824994.

For more information about the Update.exe 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.

Verifying that the Update Has Been Applied

•

Microsoft Baseline Security Analyzer

•

File Version Verification

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

1.	Click Start, and then click Search.
2.	In the Search Results pane, click All files and folders under Search Companion.
3.	In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
4.	In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
5.	On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table. Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

•

Registry Key Verification

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

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

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP1\KB935966\Filelist

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

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB935966\Filelist

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

Top of section

Acknowledgments

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

•	Mark Hofman of the SANS ISC Handlers for working with us on the DNS RPC Management Vulnerability – (CVE-2007-1748).
•	Bill O'Malley with the Information Security Office at Carnegie Mellon University for working with us on the DNS RPC Management Vulnerability – (CVE-2007-1748).

Obtaining Other Security Updates:

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

•	Security updates are available at the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch."
•	Updates for consumer platforms are available at the Microsoft Update Web site.

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.

Security Resources:

•	The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
•	TechNet Update Management Center
•	Microsoft Software Update Services
•	Microsoft Windows Server Update Services
•	Microsoft Baseline Security Analyzer (MBSA)
•	Windows Update
•	Microsoft Update
•	Windows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.
•	Office Update

Software Update Services:

By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.

For more information about how to deploy security updates by using Software Update Services, visit the Software Update Services Web site.

In response to customer feedback, and in order to provide customers with additional time to migrate from Software Update Services (SUS) 1.0, Microsoft has announced an extension to the end of support date to Tuesday, July 10, 2007. Windows Server Update Services, (WSUS), the successor to SUS, supports updating for a broader set of Microsoft products and provides robust management and reporting features. Customers can download WSUS from Windows Server Update Services (WSUS).

Windows Server Update Services:

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

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

Systems Management Server:

Microsoft Systems Management Server (SMS) delivers a highly configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and can perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, visit the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site.

Note SMS uses the Microsoft Baseline Security Analyzer, the Microsoft Office Detection Tool, and the Enterprise Update Scan Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.

Disclaimer:

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

Revisions:

•	V1.0 (May 8, 2007): Bulletin published.
•	V1.1 (May 31, 2007): Bulletin revised. File Information updated for Windows Server 2003. Clarification added throughout the bulletin for server configurations that may require the installation of DNS functionality as a prerequisite for the security update installation.
•	V1.2 (June 6, 2007): Bulletin revised. Removed the literal “Service Pack 1” from all instances of “Windows Server 2003 x64 Edition Service Pack 1” throughout the bulletin.

Top of page