Microsoft Security Bulletin MS07-062 – Important

I am using an older version or edition of the software discussed in this security bulletin. What should I do? 
The affected software listed in this bulletin has been tested to determine which versions or editions are affected. Other versions and editions are past their support life cycle. To determine the support life cycle for your product and version, visit Microsoft Support Lifecycle.

It should be a priority for customers who have older versions or editions 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. 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.

A spoofing vulnerability exists in Windows DNS Servers. The vulnerability could allow non-privileged users to send malicious responses to DNS requests, thereby spoofing or redirecting Internet traffic from legitimate locations.

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

Mitigating Factors for DNS Spoofing Attack Vulnerability – CVE-2007-3898

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. Microsoft has not identified any mitigations for this vulnerability.

Top of section

Workarounds for DNS Spoofing Attack Vulnerability – CVE-2007-3898

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has not identified any workarounds for this vulnerability.

Top of section

FAQ for DNS Spoofing Attack Vulnerability – CVE-2007-3898

What is the scope of the vulnerability? 
A spoofing vulnerability exists in Windows DNS Severs. An attacker who successfully exploited this vulnerability could impersonate a legitimate address.

What causes the vulnerability? 
The Windows DNS Server service doesn’t provide enough entropy in its random choice of transaction values when it sends out queries to upstream DNS servers.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could gain information about the DNS server’s transaction IDs, and use that information to send malicious responses to DNS requests, thus redirecting Internet traffic from legitimate locations to an address of the attacker’s choice.

How could an attacker exploit the vulnerability? 
An attacker who successfully exploited this vulnerability could respond to a DNS query with false or misleading information, thereby redirecting Internet traffic from legitimate locations.

Could the vulnerability be exploited over the Internet? 
Yes, an attacker could exploit this vulnerability over the Internet by sending specific responses to an Internet-facing DNS server that is performing recursive lookups.

What systems are primarily at risk from the vulnerability? 
This vulnerability applies to Windows DNS servers that perform recursive lookups. For more information on recursive queries, please refer to the Technet article on How DNS query works.

What does the update do? 
The update removes this vulnerability by increasing the randomness of the transaction IDs in recursive DNS server communications.

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.

Top of section

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

Security updates are available from Microsoft Update, Windows Update, and Office Update. Security updates are also available 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.

Windows Server Update Services

By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 to Windows 2000 and later operating systems. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.

Systems Management Server

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

For SMS 2.0, the SMS SUS Feature Pack, 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.

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

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

Affected Software

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

Microsoft Windows 2000 Server Service Pack 4

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	Windows 2000 Server Service Pack 4: Windows2000-kb941672-x86-enu /quiet
Installing without restarting	Windows 2000 Server Service Pack 4: Windows2000-kb941672-x86-enu /norestart
Further information	See the subsection, Microsoft Detection and Deployment Tools and Guidance
Update log File	KB941672.log
Restart Requirement
Restart required	Yes, you must restart your system after you apply this security update
Hotpatching	Not applicable
Removal Information	Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB941672$\Spuninst folder
File Information	See the next subsection, File Information for the full file manifest
Registry Key Verification	Windows 2000 Server Service Pack 4: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB941672\Filelist

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.

For all supported editions of Microsoft Windows 2000 Server Service Pack 4:

File Name	Version	Date	Time	Size
dns.exe	5.0.2195.7147	18-Oct-2007	03:39	330512

Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

Top of section

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.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch	Description
/help	Displays the command-line options
Setup Modes
/passive	Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet	Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart	Does not restart when installation has completed
/forcerestart	Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart	Display a dialog box prompting the local user to allow a restart
Special Options
/overwriteoem	Overwrites OEM files without prompting
/nobackup	Does not back up files needed for uninstall
/forceappsclose	Forces other programs to close when the computer shuts down
/log:path	Allows the redirection of installation log files
/extract[:path]	Extracts files without starting the Setup program
/ER	Enables extended error reporting
/verbose	Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

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

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
Switch	Description
/help	Displays the command-line options
Setup Modes
/passive	Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet	Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart	Does not restart when installation has completed
/forcerestart	Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart	Display a dialog box prompting the local user to allow a restart
Special Options
/forceappsclose	Forces other programs to close when the computer shuts down
/log:path	Allows the redirection of installation log files

Verifying That the Update Has Been Applied

•

Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

•

File Version Verification 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 registry keys listed in the Reference Table in this section. These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Top of section

Top of section

Microsoft 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 may be included in a future update rollup
Deployment
Installing without user intervention	For all supported 32-bit editions of Windows Server 2003: Windowsserver2003-kb941672-x86-enu /quiet For all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB941672-ia64-enu /quiet For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB941672-x64-enu /quiet
Installing without restarting	For all supported 32-bit editions of Windows Server 2003: Windowsserver2003-kb941672-x86-enu /norestart For all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB941672-ia64-enu /norestart For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB941672-x64-enu /norestart
Further information	See the subsection, Microsoft Detection and Deployment Tools and Guidance
Update Log File	KB941672.log
Restart Requirement
Restart required	Yes, you must restart your system after you apply this security update. See Restart Note below for more information.
Hotpatching	This security update does not support HotPatching. For more information about HotPatching see Microsoft Knowledge Base Article 897341.
Removal Information	For all supported 32-bit editions, x64-based editions, and Itanium-based editions of Windows Server 2003: Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the Use the Spuninst.exe utility, located in the %Windir%\$NTUninstallKB941672$\Spuninst folder
File Information	See the next subsection, File Information for the full file manifest
Registry Key Verification	For all supported 32-bit editions, x64-based editions, and Itanium-based editions of Windows Server 2003: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB941672\Filelist

Restart Note: A system restart can be avoided for Windows Server 2003 by stopping the DNS service, installing the update, and then restarting the DNS service. If the DNS service is not stopped before installing the update, then a system restart will still be required.

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.

For all supported 32-bit editions of Windows Server 2003:

File Name	Version	Date	Time	Size	Folder
dns.exe	5.2.3790.3027	16-Oct-2007	17:27	444,928	SP1GDR
dns.exe	5.2.3790.3027	16-Oct-2007	19:05	445,440	SP1QFE
w03a2409.dll	5.2.3790.2957	18-Jun-2007	11:31	28,672	SP1QFE
dns.exe	5.2.3790.4171	16-Oct-2007	17:52	445,440	SP2GDR
dns.exe	5.2.3790.4171	16-Oct-2007	21:20	445,952	SP2QFE
w03a2409.dll	5.2.3790.4106	28-Jun-2007	14:33	453,632	SP2QFE

For all supported x64-based editions of Windows Server 2003:

File Name	Version	Date	Time	Size	CPU	Folder
dns.exe	5.2.3790.3027	17-Oct-2007	18:02	763,392	X64	SP1GDR
wdns.exe	5.2.3790.3027	17-Oct-2007	18:02	444,928	X86	SP1GDR\wow
dns.exe	5.2.3790.3027	17-Oct-2007	18:03	765,440	X64	SP1QFE
w03a2409.dll	5.2.3790.2957	17-Oct-2007	18:03	29,184	X64	SP1QFE
wdns.exe	5.2.3790.3027	17-Oct-2007	18:03	445,440	X86	SP1QFE\wow
ww03a2409.dll	5.2.3790.2957	17-Oct-2007	18:03	28,672	X86	SP1QFE\wow
dns.exe	5.2.3790.4171	17-Oct-2007	18:10	764,416	X64	SP2GDR
dns.exe	5.2.3790.4171	17-Oct-2007	18:02	765,952	X64	SP2QFE
w03a2409.dll	5.2.3790.4082	17-Oct-2007	18:02	454,144	X64	SP2QFE
ww03a2409.dll	5.2.3790.4106	17-Oct-2007	18:02	453,632	X86	SP2QFE\wow

For all supported Itanium-based editions of Windows Server 2003:

File Name	Version	Date	Time	Size	CPU	Folder
dns.exe	5.2.3790.3027	17-Oct-2007	18:04	1,129,472	IA-64	SP1GDR
wdns.exe	5.2.3790.3027	17-Oct-2007	18:04	444,928	X86	SP1GDR\wow
dns.exe	5.2.3790.3027	17-Oct-2007	18:04	1,132,544	IA-64	SP1QFE
w03a2409.dll	5.2.3790.2957	17-Oct-2007	18:04	27,648	IA-64	SP1QFE
wdns.exe	5.2.3790.3027	17-Oct-2007	18:04	445,440	X86	SP1QFE\wow
ww03a2409.dll	5.2.3790.2957	17-Oct-2007	18:04	28,672	X86	SP1QFE\wow
dns.exe	5.2.3790.4171	17-Oct-2007	18:10	1,131,520	IA-64	SP2GDR
dns.exe	5.2.3790.4171	17-Oct-2007	18:04	1,132,544	IA-64	SP2QFE
w03a2409.dll	5.2.3790.4082	17-Oct-2007	18:04	452,608	IA-64	SP2QFE
ww03a2409.dll	5.2.3790.4106	17-Oct-2007	18:04	453,632	X86	SP2QFE\wow

Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

Top of section

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.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch	Description
/help	Displays the command-line options
Setup Modes
/passive	Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet	Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart	Does not restart when installation has completed
/forcerestart	Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart	Display a dialog box prompting the local user to allow a restart
Special Options
/overwriteoem	Overwrites OEM files without prompting
/nobackup	Does not back up files needed for uninstall
/forceappsclose	Forces other programs to close when the computer shuts down
/log:path	Allows the redirection of installation log files
/integrate:path	Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path]	Extracts files without starting the Setup program
/ER	Enables extended error reporting
/verbose	Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

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

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
Switch	Description
/help	Displays the command-line options
Setup Modes
/passive	Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet	Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart	Does not restart when installation has completed
/forcerestart	Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart	Display a dialog box prompting the local user to allow a restart
Special Options
/forceappsclose	Forces other programs to close when the computer shuts down
/log:path	Allows the redirection of installation log files

Verifying that the Update Has Been Applied

•

Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

•

File Version Verification 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 registry keys listed in the Reference Table in this section. These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Top of section

Top of section