Microsoft Security Bulletin MS08-001 - Critical
Vulnerabilities in Windows TCP/IP Could Allow Remote Code Execution (941644)
Published: | Updated:
Version: 3.0
General Information
Executive Summary
This critical security update resolves two privately reported vulnerabilities in Transmission Control Protocol/Internet Protocol (TCP/IP) processing. 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.
This is a critical security update for all supported editions of Windows XP and Windows Vista, an important security update for all supported editions of Windows Server 2003, and a moderate security update for all supported editions of Microsoft Windows 2000. For more information, see the subsection, Affected and Non-Affected Software, in this section.
This security update addresses the vulnerability by modifying the way that the Windows kernel processes TCP/IP structures that contain multicast and ICMP requests. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. Microsoft recommends that customers apply the update immediately
Known Issues. None
Affected and Non-Affected Software
The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.
Affected Software
Note: Supported editions of Windows Small Business Server 2003 and Windows Home Server contain the same affected code as Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2. However, for the Windows Kernel TCP/IP/IGMPv3 and MLDv2 Vulnerability (CVE-2007-0069), default configurations of Windows Small Business Server 2003 and Windows Home Server have a greater exposure to the same vulnerability and therefore merit a severity rating of Critical.
For additional details about the default configuration of Windows Server 2003 Service Pack 1, Windows Server 2003 Service Pack 2, Windows Small Business Server 2003 Service Pack 1, Windows Small Business Server 2003 R2, Windows Small Business Server 2003 R2 Service Pack 2, and Windows Home Server, see the FAQ in the Vulnerability Information section.
Frequently Asked Questions (FAQ) Related to This Security Update
Why was this bulletin revised on January 25, 2008?
This bulletin was revised to clarify the impact of Windows Kernel TCP/IP/IGMPv3 and MLDv2 Vulnerability (CVE-2007-0069) on supported editions of Windows Small Business Server 2003 and Windows Home Server. Microsoft Update, Windows Update, the Microsoft Baseline Security Analyzer (MBSA), and Microsoft Systems Management Server (SMS) already correctly offer this update to systems running Windows Small Business Server 2003 and Windows Home Server. Customers with supported editions of Windows Small Business Server 2003 and Windows Home Server should apply the update to remain secure.
Why does this update address several reported security vulnerabilities?
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers need to install this update only.
I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.
It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services.
Customers who require custom support for older releases must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit Microsoft Worldwide Information, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.
Vulnerability Information
Severity Ratings and Vulnerability Identifiers
| Affected Software | Windows Kernel TCP/IP/IGMPv3 and MLDv2 Vulnerability CVE-2007-0069 | Windows Kernel TCP/IP/ICMP Vulnerability CVE-2007-0066 | Aggregate Severity Rating |
|---|---|---|---|
| Microsoft Windows 2000 Service Pack 4 | None | Moderate Denial of Service | Moderate |
| Windows XP Service Pack 2 | Critical Remote Code Execution | Moderate Denial of Service | Critical |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Critical Remote Code Execution | Moderate Denial of Service | Critical |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Important Remote Code Execution | Moderate Denial of Service | Important |
| Windows Server 2003 x64 Edition and Windows 2003 Service Pack 2 | Important Remote Code Execution | Moderate Denial of Service | Important |
| Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Important Remote Code Execution | Moderate Denial of Service | Important |
| Windows Small Business Server 2003 Service Pack 1, Windows Small Business Server 2003 R2, Windows Small Business Server 2003 R2 Service Pack 2, and Windows Home Server | Critical Remote Code Execution | Moderate Denial of Service | Critical |
| Windows Vista | Critical Remote Code Execution | None | Critical |
| Windows Vista x64 Edition | Critical Remote Code Execution | None | 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 Windows Small Business Server and Windows Home Server configurations have IGMP enabled by default and will result in a greater exposure to the same vulnerability. Therefore, while Windows Server 2003 is rated as having a severity rating of Important, Windows Small Business Server 2003 and Windows Home Server merit a severity rating of Critical.
Windows Kernel TCP/IP/IGMPv3 and MLDv2 Vulnerability - CVE-2007-0069
A remote code execution vulnerability exists in the Windows kernel due to the way that the Windows kernel handles TCP/IP structures storing the state of IGMPv3 and MLDv2 queries. Supported editions of Microsoft Windows XP, Windows Server 2003, and Windows Vista all support IGMPv3. In addition to IGMPv3, Windows Vista supports MDLv2, which adds multicast support for IPv6 networks. An anonymous attacker could exploit the vulnerability by sending specially crafted IGMPv3 and MLDv2 packets to a computer over the network. 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.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2007-0069.
Mitigating Factors for Windows Kernel TCP/IP/IGMPv3 and MLDv2 Vulnerability - CVE-2007-0069
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:
- 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. Perimeter firewalls that block multicast traffic (IGMPv3 and MLDv2 specifically) help protect internal network assets from this attack that originate outside of the enterprise perimeter.
- Microsoft Windows 2000 is not affected by this vulnerability.
- Windows Server 2003 by default does not have any multicast addresses active and would not be affected by this vulnerability. However, installing applications that use multicasting could cause the operating system to become vulnerable.
- Attacks attempting to exploit this vulnerability would most likely result in a denial of service condition. However remote code execution could be possible.
Workarounds for Windows Kernel TCP/IP/IGMPv3 and MLDv2 Vulnerability - CVE-2007-0069
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality.
- Disable IGMP and MLD processing
You can help prevent attempts to exploit the IGMP vulnerability by modifying the IGMPLevel control in the registry.
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use the 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.
To disable IGMP and MLD processing, following these steps:
- Click Start, click Run, type regedit and then click OK.
- Expand HKEY_LOCAL_MACHINE.
- Expand SYSTEM, expand CurrentControlSet, and then expand Services.
- Expand TCPIP, expand Parameters, and then expand IGMPLevel.
- Change the DWORD value to 0.
Note You must restart the system for your changes to take effect.
Impact of workaround: IGMPv3 and MLDv2 will be disabled. Applications that depend on this service will no longer function as designed.
How to undo the workaround: Use the steps above to set the registry key setting to its original value or delete this registry key setting. By default this registry key setting is not present.
- Block IGMP and MLD on perimeter firewalls
Firewall best practices and standard default firewall configurations can help protect networks from IGMP and MLD attacks that originate outside the enterprise perimeter.
Impact of workaround: IGMPv3 and MLDv2 will be blocked from outside the enterprise perimeter, and applications that depend on IGMPv3 and MLDv2 from outside the enterprise perimeter will no longer function as designed.
- Block IGMP and MLD inbound on Vista Firewall
Click Control Panel, click Administrative Tools, and then double-click Windows Firewall with Advanced Security.
To Block IGMP:
- Select inbound rules.
- Select Core Networking - Internet Group Management Protocol (IGMP-In).
- Right-click select properties.
- Select Block the connections.
To Block MLD:
- Select inbound rules.
- Select Core Networking - Multicast Listener Query (ICMPv6-In).
- Right-click select properties.
- Select Block the connections.
- Impact of workaround: IGMP/MLD will be blocked and applications or services that rely on multicast will no longer function.
How to undo the workaround: Use the first three steps above and select Allow the connections.
FAQ for Windows Kernel TCP/IP/IGMPv3 and MLDv2 Vulnerability - CVE-2007-0069
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could run arbitrary code with elevated privileges on vulnerable systems. An attacker could then install programs or view, change, or delete data; or create new accounts with full user rights.
What causes the vulnerability?
The Windows kernel performs insufficient validation when storing the state of IGMP requests processed by TCP/IP.
What is TCP/IP?
TCP/IP is the suite of communications protocols used for transmitting data over networks.
Why is the vulnerability rating different for Windows Small Business Server and Windows Home Server than Windows Server 2003?
Windows Server 2003 by default does not have IGMP active and therefore is less exposed to this vulnerability. However, Windows Small Business Server 2003 and Windows Home Server have IGMP active by default, resulting in an increased risk to this vulnerability. The increased risk merits a severity rating of Critical for Windows Small Business Server 2003 and Windows Home Server. We recommend that customers with these products install this update immediately.
What is IGMP?
Internet Group Management Protocol (IGMP) is used for IPv4 multicast. A multicast is communication between a single sender and multiple receivers on a network. IGMP is used to exchange membership status data between IPv4 routers that support multicasting and members of multicast groups. See the MSDN site for more information on IGMP.
What is MLD?
Multicast Listener Discovery (MLD) enables you to manage subnet multicast membership for IPv6. MLD is a series of three Internet Control Message Protocols for IPv6 (ICMPv6) messages that replaces the Internet Group Management Protocol (IGMP) that is used for IPv4. See the MSDN site for more information on MLD.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
How could an attacker exploit the vulnerability?
An attacker could try to exploit the vulnerability by creating specially crafted network packets and sending the packets to an affected system.
What systems are primarily at risk from the vulnerability?
Client systems are primarily at risk from this vulnerability. However, any systems that use multicasting could be affected by this vulnerability.
What does the update do?
The update removes the vulnerability by modifying the way that the Windows kernel processes TCP/IP structures that contain IGMP requests.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued. This security bulletin addresses the privately disclosed vulnerability as well as additional issues discovered through internal investigations.
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.
Windows Kernel TCP/IP/ICMP Vulnerability - CVE-2007-0066
A denial of service vulnerability exists in TCP/IP due to the way that Windows Kernel processes fragmented router advertisement ICMP queries. ICMP Router Discovery Protocol (RDP) is not enabled by default and is required in order to exploit this vulnerability. However, on Windows 2003 Server and on Windows XP, RDP can be turned on by a setting in DHCP or by a setting in the registry. On Windows 2000, RDP can be turned on by a setting in the registry. An anonymous attacker could exploit the vulnerability by sending specially crafted ICMP packets to a computer over the network. An attacker who successfully exploited this vulnerability could cause the computer to stop responding and automatically restart.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2007-0066.
Mitigating Factors for Windows Kernel TCP/IP/ICMP Vulnerability - CVE-2007-0066
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:
- Router Discovery Protocol (RDP) is not enabled by default and is required in order to exploit this vulnerability. For more information, see Microsoft Knowledge Base Article 269734, “Router Discovery Protocol Is Disabled by Default.”
- Windows Vista is not affected by this vulnerability.
Workarounds for Windows Kernel TCP/IP/ICMP Vulnerability - CVE-2007-0066
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality.
- Disable Router Discovery Protocol Processing
By default, Router Discovery Protocol is disabled on all affected platforms. If the Router Discovery Protocol is already enabled, the following workaround would disable it. You can help prevent attempts to exploit the ICMP vulnerability by setting the PerformRouterDiscovery value in the registry.
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use the 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.
To disable ICMP processing, following these steps:
- Click Start, click Run, type regedit and then click OK.
- Expand HKEY_LOCAL_MACHINE.
- Expand SYSTEM, expand CurrentControlSet, and then expand Services.
- Expand TCPIP, expand Parameters, and then expand Interfaces.
- Select interface_name and set the PerformRouterDiscovery value to 0.
Note You must restart the system for your changes to take effect.
Impact of workaround: Router Discovery will be disabled.
How to undo the workaround: Use the steps above to set the PerformRouterDiscovery registry key setting to its original value or delete this registry key setting.
FAQ for Windows Kernel TCP/IP/ICMP Vulnerability - CVE-2007-0066
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 and require the system to restart. During that time, the system would be unable to 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 Windows kernel performs insufficient validation when processing fragmented router advertisement ICMP packets.
What is TCP/IP?
TCP/IP is the suite of communications protocols used for transmitting data over networks.
What is ICMP?
The Internet Control Message Protocol (ICMP) is a maintenance protocol that manages connectivity and routing. For more information about the capabilities and implementation of ICMP, see RFC 792: Internet Control Message Protocol DARPA Internet Program Protocol Specification.
What might an attacker use the vulnerability to do?
An attacker could try to exploit the vulnerability by sending specially crafted ICMP packets to an affected system. The message could then cause the affected system to stop responding and automatically restart.
How could an attacker exploit the vulnerability?
An attacker could try to exploit the vulnerability by creating a specially crafted network packet and sending the packet to an affected system.
What systems are primarily at risk from the vulnerability?
All systems that have ICMP Router Discovery Protocol enabled are at risk from this vulnerability.
What does the update do?
The update removes the vulnerability by modifying the way that the Windows kernel processes TCP/IP structures that contain router advertisement ICMP packets.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued. This security bulletin addresses the privately disclosed vulnerability as well as additional issues discovered through internal investigations.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
Update Information
Detection and Deployment Tools and Guidance
Manage the software and security updates you need to deploy to the servers, desktop, and mobile 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.
| Software | MBSA 2.0.1 |
|---|---|
| Microsoft Windows 2000 Service Pack 4 | Yes |
| Windows XP Service Pack 2 | Yes |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Yes |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Yes |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Yes |
| Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Yes |
| Windows Vista | See Note for Windows Vista below |
| Windows Vista x64 Edition | See Note for Windows Vista below |
Note for Windows Vista Microsoft does not support installing MBSA 2.0.1 on computers that run Windows Vista, but you may install MBSA 2.0.1 on a supported operating system and then scan the Windows Vista-based computer remotely. For additional information about MBSA support for Windows Vista, visit the MBSA Web site. See also Microsoft Knowledge Base Article 931943: Microsoft Baseline Security Analyzer (MBSA) support for Windows Vista.
For more information about MBSA 2.0.1, see MBSA 2.0 Frequently Asked Questions.
Windows Server Update Services
By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 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.
| Product | SMS 2.0 | SMS 2003 | SCCM 2007 |
|---|---|---|---|
| Microsoft Windows 2000 Service Pack 4 | Yes | Yes | Yes |
| Windows XP Service Pack 2 | Yes | Yes | Yes |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | No | Yes | Yes |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Yes | Yes | Yes |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | No | Yes | Yes |
| Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | No | Yes | Yes |
| Windows Vista | No | See Note for Windows Vista Below | Yes |
| Windows Vista x64 Edition | No | See Note for Windows Vista Below | Yes |
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.
System Center Configuration Manager (SCCM) 2007 uses WSUS 3.0 for detection of updates. For more information about SCCM 2007 Software Update Management, visit System Center Configuration Manager 2007.
Note for Windows Vista Microsoft Systems Management Server 2003 with Service Pack 3 includes support for Windows Vista manageability.
For more information about SMS, visit the SMS Web site.
For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Windows 2000 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue may be included in a future update rollup |
| Deployment | |
| Installing without user intervention | Windows 2000 Service Pack 4: Windows2000-kb941644-x86-enu /quiet |
| Installing without restarting | Windows 2000 Service Pack 4: Windows2000-kb941644-x86-enu /norestart |
| Update log file | Windows 2000 Service Pack 4: KB941644.og |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required | Yes, you must restart your system after you apply this security update |
| Hotpatching | Not applicable |
| Removal Information | Windows 2000 Service Pack 4: Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB941644$\Spuninst folder |
| File Information | See the next subsection, File Information, for the full file manifest. |
| Registry Key Verification | For Windows 2000 Service Pack 4: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB941644\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 Windows 2000:
| File Name | Version | Date | Time | Size |
|---|---|---|---|---|
| tcpip.sys | 5.0.2195.7147 | 05-Oct-2007 | 06:54 | 320,368 |
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.
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.
| 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. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
Removing the Update
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | 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.
- 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 registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Windows XP (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
| Deployment | |
| Installing without user intervention | Windows XP Service Pack 2: Windowsxp-kb941644-x86-enu /quiet |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2: Windowsserver2003.WindowsXP-kb941644-x86-enu /quiet | |
| Installing without restarting | Windows XP Service Pack 2: Windowsxp-kb941644-x86-enu /norestart |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2: Windowsserver2003.WindowsXP-kb941644-x86-enu /norestart | |
| Update log file | Windows XP Service Pack 2: KB941644.log |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required | Yes, you must restart your system after you apply this security update |
| Hotpatching | Not applicable |
| Removal Information | Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB941644$\Spuninst folder |
| File Information | See the next subsection, File Information for the full file manifest. |
| Registry Key Verification | For all supported 32-bit versions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB941644\Filelist |
| For all supported x64 editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB941644\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 32-bit editions of Windows XP:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| tcpip.sys | 5.1.2600.3244 | 30-Oct-2007 | 04:50 | 360,064 | SP2GDR |
| tcpip.sys | 5.1.2600.3244 | 30-Oct-2007 | 04:23 | 360,832 | SP2QFE |
For all supported editions of Windows XP Professional x64:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| tcpip.sys | 5.2.3790.3036 | 30-Oct-2007 | 22:12 | 702,976 | x64 | SP1GDR |
| tcpip.sys | 5.2.3790.3036 | 30-Oct-2007 | 22:15 | 813,056 | x64 | SP1QFE |
| tcpip.sys | 5.2.3790.4179 | 30-Oct-2007 | 22:34 | 767,488 | x64 | SP2GDR |
| tcpip.sys | 5.2.3790.4179 | 30-Oct-2007 | 22:13 | 767,488 | x64 | SP2QFE |
Note For a complete list of supported editions, 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.
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. 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.
Removing the Update
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | 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.
- 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 registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Windows Server 2003 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue may be included in a future update rollup |
| Deployment | |
| Installing without user intervention | For 32-bit editions of Windows Server 2003: Windowsserver2003-kb941644-x86-enu /quiet |
| For x64-based editions of Windows Server 2003: Windowsserver2003.WindowsXP-kb941644-x64-enu /quiet | |
| For Itanium-based editions of Windows Server 2003: Windowsserver2003-kb941644-ia64-enu /quiet | |
| Installing without restarting | For 32-bit editions of Windows Server 2003: Windowsserver2003-kb941644-x86-enu /norestart |
| For x64-based editions of Windows Server 2003: Windowsserver2003.WindowsXP-kb941644-x64-enu /norestart | |
| For Itanium-based editions of Windows Server 2003: Windowsserver2003-kb941644-ia64-enu /norestart | |
| Update log file | KB941644.log |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required | Yes, you must restart your system after you apply this security update |
| Hotpatching | This security update does not support HotPatching. For more information about HotPatching see Microsoft Knowledge Base Article 897341. |
| Removal Information | For 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 %Windir%\$NTUninstallKB941644$\Spuninst folder |
| File Information | See the next subsection, File Information, for the full file manifest. |
| Registry Key Verification | For all supported 32-bit editions, Itanium-based editions, and x64-based editions of Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2:: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB941644\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 32-bit editions of Windows Server 2003:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| tcpip.sys | 5.2.3790.3036 | 29-Oct-2007 | 22:31 | 333,312 | SP1GDR |
| tcpip.sys | 5.2.3790.3036 | 30-Oct-2007 | 00:42 | 387,072 | SP1QFE |
| tcpip.sys | 5.2.3790.4179 | 30-Oct-2007 | 05:14 | 383,488 | SP2GDR |
| tcpip.sys | 5.2.3790.4179 | 30-Oct-2007 | 05:17 | 384,000 | SP2QFE |
For all supported Itanium-based editions of Windows Server 2003:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| tcpip.sys | 5.2.3790.3036 | 30-Oct-2007 | 22:10 | 1,116,160 | IA-64 | SP1GDR |
| tcpip.sys | 5.2.3790.3036 | 30-Oct-2007 | 22:12 | 1,286,656 | IA-64 | SP1QFE |
| tcpip.sys | 5.2.3790.4179 | 30-Oct-2007 | 22:33 | 1,286,656 | IA-64 | SP1GDR |
| tcpip.sys | 5.2.3790.4179 | 30-Oct-2007 | 22:10 | 1,288,192 | IA-64 | SP2QFE |
For all supported x64-based editions of Windows Server 2003:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| tcpip.sys | 5.2.3790.3036 | 30-Oct-2007 | 22:12 | 702,976 | x64 | SP1GDR |
| tcpip.sys | 5.2.3790.3036 | 30-Oct-2007 | 22:15 | 813,056 | x64 | SP1QFE |
| tcpip.sys | 5.2.3790.4179 | 30-Oct-2007 | 22:34 | 767,488 | x64 | SP2GDR |
| tcpip.sys | 5.2.3790.4179 | 30-Oct-2007 | 22:13 | 767,488 | x64 | SP2QFE |
Note For a complete list of supported editions, 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.
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.
| 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.
| 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.
- 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 registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Windows Vista (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
| Deployment | |
| Installing without user intervention | All supported 32-bit editions of Windows Vista: Windows6.0-KB941644-x86 /quiet All supported x64-based editions of Windows Vista: |
| Installing without restarting | All supported 32-bit editions of Windows Vista: Windows6.0-KB941644-x86 /norestart All supported x64-based editions of Windows Vista: |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required | Yes, you must restart your system after you apply this security update |
| Hotpatching | This security update does not support HotPatching. For more information about HotPatching see Microsoft Knowledge Base Article 897341. |
| Removal Information | WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates. |
| File Information | See the next subsection, File Information, for the full file manifest. |
| Registry Key Verification | Note: A registry key does not exist to validate the presence of this patch. To detect the presence of the patch use Windows Management Instrumentation (WMI). |
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 Vista:
| File Name | Version | Date | Time | Size | Folder |
|---|---|---|---|---|---|
| netio.sys | 6.0.6000.16567 | 27-Sep-2007 | 15:48 | 216,760 | Windows6.0-KB941644-x86\x86_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.0.6000.16567_none_547b4ec7b851524e |
| netio.sys | 6.0.6000.20689 | 27-Sep-2007 | 15:42 | 217,272 | Windows6.0-KB941644-x86\x86_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.0.6000.20689_none_54f14c4ed17d5ca8 |
| netiomig.dll | 6.0.6000.16567 | 27-Sep-2007 | 15:43 | 49,152 | Windows6.0-KB941644-x86\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.16567_none_5f6577ce925d75a7 |
| netiougc.exe | 6.0.6000.16567 | 27-Sep-2007 | 15:41 | 22,016 | Windows6.0-KB941644-x86\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.16567_none_5f6577ce925d75a7 |
| tcpip.sys | 6.0.6000.16567 | 27-Sep-2007 | 14:17 | 802,816 | Windows6.0-KB941644-x86\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.16567_none_5f6577ce925d75a7 |
| tcpipcfg.dll | 6.0.6000.16567 | 27-Sep-2007 | 15:43 | 167,424 | Windows6.0-KB941644-x86\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.16567_none_5f6577ce925d75a7 |
| netiomig.dll | 6.0.6000.20689 | 27-Sep-2007 | 15:37 | 49,152 | Windows6.0-KB941644-x86\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.20689_none_5fdb7555ab898001 |
| netiougc.exe | 6.0.6000.20689 | 27-Sep-2007 | 14:16 | 22,016 | Windows6.0-KB941644-x86\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.20689_none_5fdb7555ab898001 |
| tcpip.sys | 6.0.6000.20689 | 27-Sep-2007 | 14:17 | 804,352 | Windows6.0-KB941644-x86\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.20689_none_5fdb7555ab898001 |
| tcpipcfg.dll | 6.0.6000.20689 | 27-Sep-2007 | 15:38 | 167,424 | Windows6.0-KB941644-x86\x86_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.20689_none_5fdb7555ab898001 |
For all supported x64-based editions of Windows Vista:
| File Name | Version | Date | Time | Size | CPU | Folder |
|---|---|---|---|---|---|---|
| netio.sys | 6.0.6000.16567 | 27-Sep-2007 | 17:21 | 324,280 | X64 | Windows6.0-KB941644-x64\amd64_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.0.6000.16567_none_b099ea4b70aec384 |
| netio.sys | 6.0.6000.20689 | 28-Sep-2007 | 10:43 | 324,792 | X64 | Windows6.0-KB941644-x64\amd64_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.0.6000.20689_none_b10fe7d289dacdde |
| netiomig.dll | 6.0.6000.16567 | 27-Sep-2007 | 16:50 | 59,904 | X64 | Windows6.0-KB941644-x64\amd64_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.16567_none_bb8413524abae6dd |
| netiougc.exe | 6.0.6000.16567 | 27-Sep-2007 | 16:48 | 25,600 | X64 | Windows6.0-KB941644-x64\amd64_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.16567_none_bb8413524abae6dd |
| tcpip.sys | 6.0.6000.16567 | 27-Sep-2007 | 14:47 | 1,193,472 | X64 | Windows6.0-KB941644-x64\amd64_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.16567_none_bb8413524abae6dd |
| tcpipcfg.dll | 6.0.6000.16567 | 27-Sep-2007 | 16:51 | 232,960 | X64 | Windows6.0-KB941644-x64\amd64_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.16567_none_bb8413524abae6dd |
| netiomig.dll | 6.0.6000.20689 | 28-Sep-2007 | 10:28 | 59,904 | X64 | Windows6.0-KB941644-x64\amd64_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.20689_none_bbfa10d963e6f137 |
| netiougc.exe | 6.0.6000.20689 | 28-Sep-2007 | 08:32 | 25,600 | X64 | Windows6.0-KB941644-x64\amd64_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.20689_none_bbfa10d963e6f137 |
| tcpip.sys | 6.0.6000.20689 | 28-Sep-2007 | 08:34 | 1,192,960 | X64 | Windows6.0-KB941644-x64\amd64_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.20689_none_bbfa10d963e6f137 |
| tcpipcfg.dll | 6.0.6000.20689 | 28-Sep-2007 | 10:29 | 232,960 | X64 | Windows6.0-KB941644-x64\amd64_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.20689_none_bbfa10d963e6f137 |
| netiomig.dll | 6.0.6000.16567 | 27-Sep-2007 | 15:43 | 49,152 | X86 | Windows6.0-KB941644-x64\wow64_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.16567_none_c5d8bda47f1ba8d8 |
| netiougc.exe | 6.0.6000.16567 | 27-Sep-2007 | 15:41 | 22,016 | X86 | Windows6.0-KB941644-x64\wow64_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.16567_none_c5d8bda47f1ba8d8 |
| tcpipcfg.dll | 6.0.6000.16567 | 27-Sep-2007 | 15:43 | 167,424 | X86 | Windows6.0-KB941644-x64\wow64_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.16567_none_c5d8bda47f1ba8d8 |
| netiomig.dll | 6.0.6000.20689 | 27-Sep-2007 | 15:37 | 49,152 | X86 | Windows6.0-KB941644-x64\wow64_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.20689_none_c64ebb2b9847b332 |
| netiougc.exe | 6.0.6000.20689 | 27-Sep-2007 | 14:16 | 22,016 | X86 | Windows6.0-KB941644-x64\wow64_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.20689_none_c64ebb2b9847b332 |
| tcpipcfg.dll | 6.0.6000.20689 | 27-Sep-2007 | 15:38 | 167,424 | X86 | Windows6.0-KB941644-x64\wow64_microsoft-windows-tcpip_31bf3856ad364e35_6.0.6000.20689_none_c64ebb2b9847b332 |
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.
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.
| Switch | Description |
|---|---|
| /?, /h, /help | Displays help on supported switches. |
| /quiet | Suppresses the display of status or error messages. |
| /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.
Verifying that the Update Has Been Applied
- Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information
- File Version Verification
Because there are several 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.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- IBM Internet Security Systems X-Force by Alex Wheeler and Ryan Smith for reporting the Windows Remote Kernel TCP/IP IGMP Vulnerability (CVE-2007-0069).
- IBM Internet Security Systems X-Force by Alex Wheeler and Ryan Smith for reporting the Windows Remote Kernel TCP/IP ICMP Vulnerability (CVE-2007-0066).
Support
- Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
- International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.
Disclaimer
The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Revisions
- V1.0 (January 8, 2008): Bulletin published.
- V2.0 (January 23, 2008): Bulletin updated to add Windows Small Business Server 2003 Service Pack 2 as an affected product. Also added an FAQ to clarify that current Microsoft detection and deployment tools already correctly offer the update to Windows Small Business Server 2003 Service Pack 2 customers.
- V3.0 (January 25 2008): This bulletin was revised to clarify the impact of Windows Kernel TCP/IP/IGMPv3 and MLDv2 Vulnerability (CVE-2007-0069) on supported editions of Windows Small Business Server 2003 and Windows Home Server. Also included is an explanation and clarification that current Microsoft detection and deployment tools already correctly offer the update to systems running Windows Small Business Server 2003 and Windows Home Server.