Microsoft Security Bulletin MS06-007 - Important
Vulnerability in TCP/IP Could Allow Denial of Service (913446)
Published: February 14, 2006 | Updated: March 17, 2006
Version: 1.2
Summary
Who should read this document: Customers who use Microsoft Windows
Impact of Vulnerability: Denial of Service
Maximum Severity Rating: Important
Recommendation: Customers should apply the update at the earliest opportunity.
Security Update Replacement: This bulletin replaces a prior security update. See the frequently asked questions (FAQ) section of this bulletin for the complete list.
Caveats: None
Tested Software and Security Update Download Locations:
Affected Software:
- Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 - Download the update
- Microsoft Windows XP Professional x64 Edition - Download the update
- Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 - Download the update
- Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems - Download the update
- Microsoft Windows Server 2003 x64 Edition - Download the update
- Note The security updates for Microsoft Windows Server 2003, Microsoft Windows Server 2003 Service Pack 1, and Microsoft Windows Server 2003 x64 Edition also apply to Microsoft Windows Server 2003 R2.
Non-Affected Software:
- Microsoft Windows 2000 Service Pack 4
- Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME)
The software in this list 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.
General Information
Executive Summary
Executive Summary:
This update resolves a newly-discovered, privately-reported vulnerability. The vulnerability is documented in the "Vulnerability Details" section of this bulletin.
We recommend that customers apply the update at the earliest opportunity.
Severity Ratings and Vulnerability Identifiers:
Vulnerability Identifiers | Impact of Vulnerability | Windows XP Service Pack 1 | Windows XP Service Pack 2 | Windows Server 2003 | Windows Server 2003 Service Pack 1 |
---|---|---|---|---|---|
IGMP v3 DoS Vulnerability - CAN-2006-0021 | Denial of Service | Important | Important | Important | Important |
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 severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows:
- The Microsoft Windows XP Professional x64 Edition severity rating is the same as the Windows XP Service Pack 2 severity rating.
- The Microsoft Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.
- The Microsoft Windows Server 2003 with SP1 for Itanium-based Systems severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.
- The Microsoft Windows Server 2003 x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.
Frequently asked questions (FAQ) related to this security update
Why did Microsoft update this Security Bulletin on February 14th 2006?
After the release of MS06-007 on Tuesday 14 February 2006, Microsoft became aware of an issue affecting the installation of MS06-007 through Automatic Updates, Windows Update, Windows Server Update Services and Systems Management Server 2003 when using the Inventory Tool for Microsoft Updates (ITMU). The issue did not affect customers who installed the updates through Software Update Services or through Systems Management Server when not using ITMU, or manually installed the Security Update from the Microsoft Download Center.
The issue did not affect the security update MS06-007 itself. When successfully installed, MS06-007 fully protects against the Internet Group Management Protocol (IGMP) vulnerability.
Microsoft revised this security bulletin to notify customers that the distribution channels have been updated to correct these issues.
Customers using Automatic Updates need to take no action as the new updates will be automatically downloaded on their regularly set update schedule. Microsoft Update and Windows Update customers who visited these sites before 8:30 PM PST on Tuesday February 14th, should revisit them and accept the security updates being offered. Windows Server Update Services and Systems Management Server 2003 administrators who had synchronized their servers to obtain the updates released on Tuesday 14 February, before 8:30PM PST that evening should manually synchronize their servers and approve the new updates.
What updates does this release replace?
This security update replaces a prior security update. The security bulletin ID and affected operating systems are listed in the following table.
Bulletin ID | Windows XP Service Pack 1 | Windows XP Service Pack 2 | Windows Server 2003 | Windows Server 2003 Service Pack 1 |
---|---|---|---|---|
MS05-019 | Replaced | Replaced | Replaced | Not Applicable |
Can I use the Microsoft Baseline Security Analyzer (MBSA) 1.2.1 to determine whether this update is required?
Yes. MBSA 1.2.1 will determine whether this update is required. For more information about MBSA, visit the MBSA Web site.
Can I use the Microsoft Baseline Security Analyzer (MBSA) 2.0 to determine whether this update is required?
Yes. MBSA 2.0 will determine whether this update is required. MBSA 2.0 can detect security updates for products that Microsoft Update supports. For more information about MBSA, visit the MBSA Web site.
Can I use Systems Management Server (SMS) to determine whether this update is required?
Yes. SMS can help detect and deploy this security update. For information about SMS, visit the SMS Web site.
The Security Update Inventory Tool can be used by SMS for detecting security updates that are offered by Windows Update, that are supported by Software Update Services, and other security updates that are supported by MBSA 1.2.1. For more information about the Security Update Inventory Tool, see the following Microsoft Web site. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460.
The SMS 2003 Inventory Tool for Microsoft Updates can be used by SMS for detecting security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 Inventory Tool for Microsoft Updates, visit the following Microsoft Web site.
For more information about SMS, visit the SMS Web site.
Vulnerability Details
IGMP v3 DoS Vulnerability - CVE-2006-0021:
A denial of service vulnerability exists that could allow an attacker to send a specially crafted IGMP packet to an affected system. An attacker could cause the affected system to stop responding.
Mitigating Factors for IGMP v3 DoS Vulnerability - CVE-2006-0021:
- Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems that are connected to the Internet have a minimal number of ports exposed. Note Windows Firewall will help protect against attacks utilizing a unicast IGMP v3 packet, however, it will not help protect against an attack utilizing a multicast IGMP v3 packet.
Workarounds for IGMP v3 DoS Vulnerability - CVE-2006-0021:
Microsoft has tested the following workarounds. While these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section.
Disable IGMP
Disabling IGMP will prevent an affected host from processing IGMP related packets that could cause a system to stop responding. IGMP processing can be disabled by following these steps: 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 Regedt32.exe. Note We recommend backing up the registry before you edit it.- Click Start, click Run, type "regedit32 " (without the quotation marks), and then click OK.
- In Registry Editor, locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\
- Add the DWORD Value: IGMPLevel. Set the value to 0. This value disables IGMP processing. By default, this key does not exist.
- You must restart your system for this change to take effect.
Block all IGMP network packets at the firewall or router
Blocking IGMP packets at the firewall or at the router will help protect systems that are behind that firewall or router from attempts to exploit this vulnerability. We recommend that you block all unsolicited inbound communication from the Internet. ISA Server 2000 and ISA Server 2004 can be used to block the affected types of traffic.Impact of Workaround: These changes will help prevent attacks by restricting the ability of an attacker to send malformed IGMP packets to the affected host. This setting can also negatively impact network performance and communication by preventing the ability of routers to properly forward packets between subnets.
Note Windows Firewall will help protect against attacks utilizing a unicast IGMP v3 packet, however, it will not help protect against an attack utilizing a multicast IGMP v3 packet.
FAQ for IGMP v3 DoS Vulnerability - CVE-2006-0021:
What is the scope of the vulnerability?
This is a denial of service vulnerability. An attacker who exploited this vulnerability could cause the affected system to stop responding. During that time, the server cannot respond to requests. Note that the denial of service vulnerability would not allow an attacker to execute code or to elevate their user rights, but it could cause the affected system to stop accepting requests.
What causes the vulnerability?
The affected messages are not being ignored in certain cases that allow an attacker to send a malformed packet which may cause affected system to stop responding.
What is IGMP?
Internet Group Management Protocol (IGMP) is a TCP/IP standard defined in RFC 1112 "Internet Group Management Protocol (IGMP)." In addition to defining address and host extensions for how IP hosts support multicasting, this RFC also defines the Internet Group Management Protocol (IGMP) version 1. RFC 2236, "Internet Group Management Protocol (IGMP), version 2" defines IGMP version 2. Both versions of IGMP provide a protocol to exchange and update information about host membership in specific multicast groups. Additionally, the Windows Server 2003 family supports IGMP version 3, described in the Internet Draft titled "Internet Group Management Protocol, version 3." With IGMP version 3, hosts can specify interest in receiving multicast traffic from specified sources or from all but a specific set of sources. For more information about IGMP, visit the Microsoft Tech Net Web site.
Who could exploit the vulnerability?
Any anonymous user who could deliver a specially crafted message to the affected system could try to exploit this vulnerability.
How could an attacker exploit the vulnerability?
An attacker could try to exploit the vulnerability by creating a specially crafted message and sending the message to an affected system. The message could then cause the affected system to stop responding.
What systems are primarily at risk from the vulnerability?
Workstations and Servers are both potentially at risk from this vulnerability.
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. Microsoft has provided information about how you can help protect your PC. End users can visit the Protect Your PC Web site. IT professionals can visit the Security Guidance Center Web site.
What does the update do?
The update removes the vulnerability by modifying the way that the affected operating systems validate IGMP requests.
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.
Security Update Information
Affected Software:
For information about the specific security update for your affected software, click the appropriate link:
Windows Server 2003 (all versions)
Prerequisites
This security update requires Windows Server 2003 or Windows Server 2003 Service Pack 1.
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.
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.
Deployment Information
To install the security update without any user intervention, use the following command at a command prompt for Windows Server 2003:
Windowsserver2003-kb913446-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 KB913446.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 Server 2003:
Windowsserver2003-kb913446-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. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.
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%\$NTUninstallKB913446$\Spuninst folder.
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 |
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 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 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:
File Name | Version | Date | Time | Size | Folder |
---|---|---|---|---|---|
Tcpip.sys | 5.2.3790.468 | 13-Jan-2006 | 01:21 | 317,440 | RTMGDR |
Tcpip.sys | 5.2.3790.468 | 13-Jan-2006 | 01:47 | 318,464 | RTMQFE |
Tcpip.sys | 5.2.3790.2617 | 13-Jan-2006 | 02:15 | 333,312 | SP1GDR |
Tcpip.sys | 5.2.3790.2617 | 13-Jan-2006 | 02:36 | 333,312 | SP1QFE |
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; and Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems:
File Name | Version | Date | Time | Size | Folder |
---|---|---|---|---|---|
Tcpip.sys | 5.2.3790.468 | 13-Jan-2006 | 04:06 | 973,824 | RTMGDR |
Tcpip.sys | 5.2.3790.468 | 13-Jan-2006 | 04:06 | 977,920 | RTMQFE |
Tcpip.sys | 5.2.3790.2617 | 13-Jan-2006 | 04:13 | 1,116,160 | SP1GDR |
Tcpip.sys | 5.2.3790.2617 | 13-Jan-2006 | 04:06 | 1,116,672 | SP1QFE |
Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition; Windows Server 2003 R2, Standard x64 Edition; Windows Server 2003 R2, Enterprise x64 Edition; and Windows Server 2003 R2, Datacenter x64 Edition:
File Name | Version | Date | Time | Size | Folder |
---|---|---|---|---|---|
Tcpip.sys | 5.2.3790.2617 | 13-Jan-2006 | 04:13 | 702,976 | SP1GDR |
Tcpip.sys | 5.2.3790.2617 | 13-Jan-2006 | 04:06 | 702,976 | SP1QFE |
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 or SP1QFE files to your system. Otherwise, the installer copies the RTMGDR or SP1GDR 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
To verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
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.- 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 version of the operating system or programs installed, 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 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, 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 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, 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; and Windows Server 2003, Datacenter x64 Edition; Windows Server 2003 R2, Standard x64 Edition; Windows Server 2003 R2, Enterprise x64 Edition; and Windows Server 2003 R2, Datacenter x64 Edition:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP2\KB913446\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 913446 security update into the Windows installation source files.
Windows XP (all versions)
Prerequisites
This security update requires Microsoft Windows XP Service Pack 1 or a later version. For more information, see Microsoft Knowledge Base Article 322389.
Inclusion in Future Service Packs:
The update for this issue will be included in a future Service Pack or Update Rollup.
Installation Information
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 | 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 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 Microsoft Windows XP:
Windowsxp-kb913446-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 KB913446.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 XP:
Windowsxp-kb913446-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. For more information about the reasons why you may be prompted to restart your computer, see Microsoft Knowledge Base Article 887012.
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%\$NTUninstallKB913446$\Spuninst folder.
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 |
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 XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:
File Name | Version | Date | Time | Size | Folder |
---|---|---|---|---|---|
Tcpip.sys | 5.1.2600.1792 | 13-Jan-2006 | 01:13 | 340,480 | SP1QFE |
Tcpip.sys | 5.1.2600.2827 | 13-Jan-2006 | 02:28 | 359,808 | SP2GDR |
Tcpip.sys | 5.1.2600.2827 | 13-Jan-2006 | 17:07 | 360,448 | SP2QFE |
Windows XP Professional x64:
File Name | Version | Date | Time | Size | Folder |
---|---|---|---|---|---|
Tcpip.sys | 5.2.3790.2617 | 13-Jan-2006 | 04:13 | 702,976 | SP1GDR |
Tcpip.sys | 5.2.3790.2617 | 13-Jan-2006 | 04:06 | 702,976 | SP1QFE |
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 SP1QFE or SP2QFE files to your system. Otherwise, the installer copies the 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 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
To verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
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.- 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 version of the operating system or programs installed, 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 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.For Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB913446\Filelist
For Windows XP Professional x64 Edition:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP2\KB913446\Filelist
Note These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly if an administrator or an OEM integrates or slipstreams the 913446 security update into the Windows installation source files.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Douglas Nascimento of Datacom for reporting the IGMP v3 DoS Vulnerability (CAN-2006-0021).
Obtaining Other Security Updates:
Updates for other security issues are available at the following locations:
- Security updates are available in 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.
- 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.
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 Scanning 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 (February 14, 2006): Bulletin published.
- V1.1 (February 14, 2006): Security Update FAQ Section updated to reflect an issue, now resolved, that affected the deployment of this update through Automatic Update, Windows Update, Microsoft Update, Windows Servier Update Services and Systems Management Server 2003 when using the Inventory Tool for Microsoft Updates.
- V1.2 (March 17, 2006): Executive Summary Section updated to reflect that this security update does not supersede Microsoft Security update MS05-019 on Windows Server 2003 Service Pack 1.
Built at 2014-04-18T13:49:36Z-07:00