Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Microsoft Security Bulletin MS06-064 - Important

Vulnerabilities in TCP/IP IPv6 Could Allow Denial of Service (922819)

Published: October 10, 2006

Version: 1.0

Summary

Who Should Read this Document: Customers who use Microsoft Windows.

Impact of Vulnerability: Denial of Service

Maximum Severity Rating: Low

Recommendation: Customers should evaluate whether to apply the security update to the affected systems.

Security Update Replacement: 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

Non-Affected Software:

  • Microsoft Windows 2000 Service Pack 4

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.

Note The security updates for Microsoft Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 x64 Edition also apply to Windows Server 2003 R2.

General Information

Executive Summary:

This update resolves a publicly disclosed vulnerability as well as additional issues discovered through internal investigations.

An attacker who successfully exploited the most severe of these vulnerabilities against an affected system could cause the system to stop responding or automatically reboot.

We recommend that customers evaluate whether to apply the security update to the affected systems.

Severity Ratings and Vulnerability Identifiers:

Vulnerability IdentifiersImpact of VulnerabilityWindows XP Service Pack 1Windows XP Service Pack 2Windows Server 2003Windows Server 2003 Service Pack 1
ICMP Connection Reset Vulnerability - CVE-2004-0790Denial of ServiceLowLowLowLow
TCP Connection Reset Vulnerability - CVE-2004-0230Denial of ServiceLowLowLowLow
Spoofed Connection Request Vulnerability - CVE-2005-0688Denial of ServiceLowLowLowLow
Aggregate Severity of All Vulnerabilities Low Low Low Low

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 security updates for Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 x64 Edition also apply to Windows Server 2003 R2.

Note The severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows:

  • The Windows XP Professional x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1.
  • The Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.
  • The 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 Windows Server 2003 x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.

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 can install only this update.

Does this security update contain any non-security changes to functionality?
Yes. In addition to the changes that are listed in the "Vulnerability Details" section, this update includes the Teredo Interoperability update for Windows XP Service Pack 2. Windows Server 2003 does not support Teredo and is not receiving the Teredo functionality change.

What is the Teredo interoperability update?
IANA has allocated a new Teredo prefix 2001:0/32 for Teredo. In order to establish connectivity over Teredo between Windows XP Service Pack 2 IPv6 capable hosts and Windows Vista, the Teredo prefix is being revised on all Windows XP machines. To learn more about Teredo please visit the following Microsoft TechNet documentation. To learn more about the new Teredo prefix, please visit the following RFC documentation.

Does this security update make any changes to the IPv4 implementation of TCP/IP?
No. The security issues addressed by this bulletin have already been resolved in the corresponding IPv4 implementation of TCP/IP with the release of the MS05-019.

Extended security update support for Microsoft Windows 98, Windows 98 Second Edition, or Windows Millennium Edition ended on July 11, 2006. I am still using one of these operating systems; what should I do?
Windows 98, Windows 98 Second Edition, and Windows Millennium Edition have reached the end of their support life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.

Extended security update support for Microsoft Windows NT Workstation 4.0 Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. Extended security update support for Microsoft Windows NT Server 4.0 Service Pack 6a ended on December 31, 2004. Extended security update support for Microsoft Windows 2000 Service Pack 3 ended on June 30, 2005. I am still using one of these operating systems; what should I do?
Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, Windows 2000 Service Pack 2, and Windows 2000 Service Pack 3 have reached the end of their support life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.

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

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

ProductMBSA 1.2.1MBSA 2.0
Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2YesYes
Microsoft Windows XP Professional x64 EditionNoYes
Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1YesYes
Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based SystemsNoYes
Microsoft Windows Server 2003 x64 Edition familyNoYes

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

For more detailed information, see Microsoft Knowledge Base Article 910723.

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

ProductSMS 2.0SMS 2003
Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2YesYes
Microsoft Windows XP Professional x64 EditionNoYes
Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1YesYes
Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based SystemsNoYes
Microsoft Windows Server 2003 x64 Edition familyNoYes

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

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

For more detailed information, see Microsoft Knowledge Base Article 910723.

ICMP Connection Reset Vulnerability - CVE-2004-0790:

A denial of service vulnerability exists in the IPv6 Windows implementation of the Internet Control Message Protocol (ICMP). An attacker who successfully exploited this vulnerability could cause the affected system to drop an existing TCP connection.

Mitigating Factors for ICMP Connection Reset Vulnerability - CVE-2004-0790:

  • Firewall best practices and firewall or router configurations that block all ICMP traffic 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.
  • IPv6 support is not installed by default on Windows XP Service Pack 1, Windows XP Service Pack 2, Windows Server 2003 and Windows Server 2003 Service Pack 1.
  • An attacker’s system must belong to the same IPv6 network as the target system.
  • An attacker must first predict or discover the IP address and port information of the source and of the destination of an existing TCP network connection.
  • This attack would have to be performed on each TCP connection that was targeted for reset. Many applications will automatically restore connections that have been reset.

Workarounds for ICMP Connection Reset Vulnerability - CVE-2004-0790:

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.

  • Uninstall IPv6.

    For the IPv6 protocol for Windows XP with SP2, Windows XP with SP1, or Windows Server 2003, do the following:

    1. Log on to the computer with a user account that has privileges to change network configuration.
    2. Click Start, click Control Panel, and then double-click Network Connections.
    3. Click Microsoft TCP/IP version 6 (for Windows XP with SP2 or Windows Server 2003) or Microsoft IPv6 Developer Edition (for Windows XP with SP1), and then click Uninstall.
    4. When prompted to confirm the removal of the Microsoft IPv6 Developer Edition or Microsoft TCP/IP version 6 protocol, click OK.

    Alternately, from the Windows XP or Windows Server 2003 desktop do the following:

    1. Click Start, point to Programs, point to Accessories.
    2. Click Command Prompt.
    3. At the command prompt, type netsh interface ipv6 uninstall.

    Impact of Workaround: Uninstalling IPv6 would result in the system not being able to communicate with other hosts on an IPv6 configured network.

  • Block all ICMP network packets at the firewall or at the router:

    ICMP network packets are used to initiate a connection with the affected components. Blocking them 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.

    Impact of Workaround: This workaround can also negatively impact performance by preventing TCP from optimizing network communication. ICMP network packets can eliminate fragmentation at routers connecting networks with different MTUs. Fragmentation reduces TCP throughput and increases network congestion.

    Note: Windows XP Service Pack 1 Firewall is unable to handle IPv6 network traffic. In order to ensure protection for your Windows XP Service Pack 1 system using the Internet Connection Firewall you should apply the update identified in KB Article 817778 “Overview of the Advanced Networking Pack for Windows XP”.

  • Block ICMP traffic by using IPSec on the affected systems.

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

    Impact of Workaround: This workaround can also negatively impact performance by preventing TCP from optimizing network communication. ICMP network packets can eliminate fragmentation at routers connecting networks with different MTUs. Fragmentation reduces TCP throughput and increases network congestion.

FAQ for ICMP Connection Reset Vulnerability - CVE-2004-0790:

What is the scope of the vulnerability?

A denial of service vulnerability exists in Windows in the IPv6 implementation of the Internet Control Message Protocol (ICMP). An attacker who successfully exploited this vulnerability could cause the affected system to drop an existing TCP connection.

What causes the vulnerability?
Specially crafted ICMP packets are being parsed when they should be dropped which may cause the reset of an existing connection.

What is IPv6?
Internet Protocol version 6 (IPv6), a new suite of standard protocols for the network layer of the Internet, is built into Microsoft Windows XP and later. IPv6 is designed to solve many of the problems of the current version of IP (known as IPv4) such as address depletion, security, autoconfiguration, and extensibility. To learn more about IPv6, please read the following Microsoft FAQ for IPv6.

What is TCP/IP?
TCP/IP is a set of networking protocols. TCP/IP includes standards for how computers communicate and conventions for connecting networks and for routing traffic. For more information about TCP/IP, see the following Microsoft Web site.

What is ICMP?
Internet Control Message Protocol (ICMP) is a required TCP/IP standard. "Internet Control Message Protocol (ICMP)." Hosts and routers that use IP communication can report errors and exchange limited control and status information using ICMP.

ICMP messages are usually sent automatically in one of the following situations:

  • An IP datagram cannot reach its destination.
  • An IP router (gateway) cannot forward datagrams at the current rate of transmission.
  • An IP router redirects the sending host to a better route to the destination.

You can use the ping command to send ICMP echo request messages and to record the receipt of ICMP echo reply messages. By using these messages, you can detect network or host communication failures and troubleshoot common TCP/IP connectivity problems. For more information about ICMP, see the following Microsoft Web site.

What might an attacker use the vulnerability to do?
An attacker who exploited this vulnerability could cause the affected system to reset TCP connections.

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. An attacker’s system must belong to the same IPv6 network as a target system.

How could an attacker exploit the vulnerability?
An attacker could 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 reset TCP network connections.

What systems are primarily at risk from the vulnerability?
All affected operating systems are at risk from this vulnerability. However, servers are at primary risk from this vulnerability because they maintain connections with clients that could be vulnerable to the connection reset.

Could the vulnerability be exploited over the Internet?
Yes. An attacker could try to exploit this vulnerability over the Internet. By default, the Microsoft Internet Connection Firewall (ICF) in Windows XP Service Pack 1 and in Windows Server 2003 allows these kinds of network packets and cannot be used to filter them by default. The firewall component in Windows XP Service Pack 2 and Windows Server 2003 Service Pack 1 called Windows Firewall is able to block this traffic. If you are running IPv6 on a Windows XP Service Pack 1 you should apply update identified in KB Article 817778 “Overview of the Advanced Networking Pack for Windows XP” to get an updated Internet Connection Firewall which is able to handle IPv6 traffic.

What does the update do?
The update removes the vulnerability by modifying the way that the affected operating systems validate ICMP requests.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability has been publicly disclosed as affecting the IPv4 implementation of TCP/IP. It has been assigned Common Vulnerability and Exposure number CVE-2004-0790. There is a variant of this issue that has been assigned Common Vulnerability and Exposure number CVE-2004-0791. The Microsoft security update for CVE-2004-0790 also addresses CVE-2004-0791.

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.

How does this vulnerability relate to the vulnerability that is corrected by MS05-019?
MS05-19 addressed the same vulnerability in the more commonly adopted and deployed IPv4 implementation of TCP/IP. This update addresses the vulnerability in the IPv6 implementation.

TCP Connection Reset Vulnerability - CVE-2004-0230:

A denial of service vulnerability exists in the IPv6 Windows implementation of TCP. An attacker who successfully exploited this vulnerability could cause the affected system to drop an existing TCP connection.

Mitigating Factors for TCP Connection Reset Vulnerability - CVE-2004-0230:

  • An attacker must be able to predict or discover the IP address and port information of the source and of the destination of an existing TCP network connection. An attacker would also have to predict or to learn certain difficult TCP network packet details. Protocols or programs that maintain long sessions and have predictable TCP/IP information are at an increased risk for this issue.
  • IPv6 support is not installed by default on Windows XP Service Pack 1 and Windows XP Service Pack 2, Windows Server 2003 and Windows Server 2003 Service Pack 1.
  • An attacker’s system must belong to the same IPv6 network as the target system.
  • 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. Affected systems that allow any TCP connections to the Internet may be vulnerable to this issue.
  • This attack would have to be performed on each TCP connection that was targeted for reset. Many applications will automatically restore connections that have been reset.

Workarounds for TCP Connection Reset Vulnerability - CVE-2004-0230:

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.

  • Uninstall IPv6.

    For the IPv6 protocol for Windows XP with SP2, Windows XP with SP1, or Windows Server 2003, do the following:

    1. Log on to the computer with a user account that has privileges to change network configuration.
    2. Click Start, click Control Panel, and then double-click Network Connections.
    3. Click Microsoft TCP/IP version 6 (for Windows XP with SP2 or Windows Server 2003) or Microsoft IPv6 Developer Edition (for Windows XP with SP1), and then click Uninstall.
    4. When prompted to confirm the removal of the Microsoft IPv6 Developer Edition or Microsoft TCP/IP version 6 protocol, click OK.

    Alternately, from the Windows XP or Windows Server 2003 desktop do the following:

    1. Click Start, point to Programs, point to Accessories.
    2. Click Command Prompt.
    3. At the command prompt, type netsh interface ipv6 uninstall.

Impact of Workaround: Uninstalling IPv6 would result in the system not being able to communicate with other hosts on an IPv6 configured network.

FAQ for TCP Connection Reset Vulnerability - CVE-2004-0230:

What is the scope of the vulnerability?
A denial of service vulnerability exists in the IPv6 Windows implementation of TCP. An attacker who successfully exploited this vulnerability could cause the affected system to drop an existing TCP connection.

What causes the vulnerability?
Specially crafted TCP packets are being parsed when they should be dropped which may cause the reset of an existing connection.

What is IPv6?
Internet Protocol version 6 (IPv6), a new suite of standard protocols for the network layer of the Internet, is built into Microsoft Windows XP and later. IPv6 is designed to solve many of the problems of the current version of IP (known as IPv4) such as address depletion, security, autoconfiguration, and extensibility. To learn more about IPv6, please read the following Microsoft FAQ for IPv6.

What is TCP/IP?
TCP/IP is a set of networking protocols. TCP/IP includes standards for how computers communicate and conventions for connecting networks and for routing traffic. For more information about TCP/IP, see the following Microsoft Web site.

What might an attacker use the vulnerability to do?
An attacker who exploited this vulnerability could cause the affected system to reset TCP connections.

Who could exploit the vulnerability?
Any anonymous user who could deliver a specially crafted message to the affected system and learn or predict the required TCP details could try to exploit this vulnerability. An attacker’s system must belong to the same IPv6 network as a target system.

How could an attacker exploit the vulnerability?
An attacker could 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 reset TCP connections.

An attacker must be able to predict or discover the IP address and port information of the source and of the destination of an existing TCP network connection. An attacker would also have to predict or learn certain difficult TCP network packet details.

What systems are primarily at risk from the vulnerability?
All affected operating systems are at risk from this vulnerability. However, servers are at primary risk from this vulnerability because they maintain connections with clients that could be vulnerable to the connection reset. Protocols or programs that maintain long sessions and have predictable TCP/IP information are at an increased risk to this issue.

Could the vulnerability be exploited over the Internet?
Yes. An attacker could try to exploit this vulnerability over the Internet.

What does the update do?
The update removes the vulnerability by modifying the way that the affected operating systems validate TCP requests.

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

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had seen examples of proof of concept code published publicly but had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.

Does applying this security update help protect customers from the code that has been published publicly that attempts to exploit this vulnerability?
Yes. This security update addresses the proof of concept code that has been publicly published. The vulnerability that has been addressed has been assigned the Common Vulnerability and Exposure number CVE-2004-0230.

How does this vulnerability relate to the vulnerability that is corrected by MS05-019?
MS05-19 addressed the same vulnerability in the more commonly adopted and deployed IPv4 implementation of TCP/IP. This update addresses the vulnerability in the IPv6 implementation.

Spoofed Connection Request Vulnerability - CVE-2005-0688:

A denial of service vulnerability exists in Windows in the IPv6 implementation of TCP/IP. An attacker who successfully exploited this vulnerability could cause the affected system to stop responding.

Mitigating Factors for Spoofed Connection Request Vulnerability - CVE-2005-0688:

  • IPv6 support is not installed by default on Windows XP Service Pack 1, Windows XP Service Pack 2 and Windows Server 2003 and Windows Server 2003 Service Pack 1.
  • An attacker’s system must belong to the same IPv6 network as the target system.
  • The affected system return to a normal operational state after the specially crafted packets are finished processing.
  • A typical network deployment scenario would limit the attack to an individual network segment as most routers will not forward these kinds of specially crafted TCP/IP network packets.
  • 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. Affected systems that allow any IP connections to the Internet may be vulnerable to this issue.

Workarounds for Spoofed Connection Request Vulnerability - CVE-2005-0688:

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.

  • Uninstall IPv6.

    For the IPv6 protocol for Windows XP with SP2, Windows XP with SP1, or Windows Server 2003, do the following:

    1. Log on to the computer with a user account that has privileges to change network configuration.
    2. Click Start, click Control Panel, and then double-click Network Connections.
    3. Click Microsoft TCP/IP version 6 (for Windows XP with SP2 or Windows Server 2003) or Microsoft IPv6 Developer Edition (for Windows XP with SP1), and then click Uninstall.
    4. When prompted to confirm the removal of the Microsoft IPv6 Developer Edition or Microsoft TCP/IP version 6 protocol, click OK.

    Alternately, from the Windows XP or Windows Server 2003 desktop do the following:

    1. Click Start, point to Programs, point to Accessories.
    2. Click Command Prompt.
    3. At the command prompt, type netsh interface ipv6 uninstall.

Impact of Workaround: Uninstalling IPv6 would result in the system not being able to communicate with other hosts on an IPv6 configured network.

FAQ for Spoofed Connection Request Vulnerability - CVE-2005-0688:

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 for a limited time as a result of excessive CPU utilization. During that time, affected systems cannot respond to requests. Note that the denial of service vulnerability would not allow an attacker to execute code or elevate their user rights, but it could cause the affected system to stop accepting requests.

What causes the vulnerability?
The affected operating systems perform incomplete validation of TCP/IP network packets. This vulnerability occurs when a Transmission Control Protocol (TCP) SYN packet is received with a spoofed source Internet Protocol (IP) address and port number that is identical to that of the destination IP address and port. The effect of this makes it appear that the host computer has sent a packet to itself. If this attack is successful, a loop is created and extra computer CPU time is used.

What is IPv6?
Internet Protocol version 6 (IPv6), a new suite of standard protocols for the network layer of the Internet, is built into Microsoft Windows XP and later. IPv6 is designed to solve many of the problems of the current version of IP (known as IPv4) such as address depletion, security, autoconfiguration, and extensibility. To learn more about IPv6, please read the following FAQ for IPv6.

What is TCP/IP?
TCP/IP is a set of networking protocols. TCP/IP includes standards for how computers communicate and conventions for connecting networks and for routing traffic. For more information about TCP/IP, see the following. For more information about TCP/IP, see the following Microsoft Web site.

What might an attacker use the vulnerability to do?
An attacker who exploited this vulnerability could cause the affected system to stop responding.

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 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?
All affected operating systems are 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. However, this attack requires that routers forward malformed TCP/IP network packets. Most routers will not forward these kinds of malformed TCP/IP network packets.

What does the update do?
The update removes the vulnerability by modifying the way that the affected operating systems validate TCP/IP requests.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability has been publicly disclosed for the IPv4 implementation of TCP/IP. It has been assigned Common Vulnerability and Exposure number CVE-2005-0688. It also has been named “Land Attack” by the larger security community.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had seen examples of proof of concept code published publicly but had not received any information to indicate that this vulnerability had been publicly used to attack customers using IPv6 when this security bulletin was originally issued.

Does applying this security update help protect customers from the code that has been published publicly that attempts to exploit this vulnerability?
Yes. This security update addresses the vulnerability that is demonstrated by the existing proof of concept code that has been published.

How does this vulnerability relate to the vulnerability that is corrected by MS05-019?
MS05-19 addressed the same vulnerability in the more commonly adopted and deployed IPv4 implementation of TCP/IP. This update addresses the vulnerability in the IPv6 implementation.

Affected Software:

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

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.

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

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

Deployment Information

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

Windowsxp-KB922819-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 KB922819.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-KB922819-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.

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%\$NTUninstallKB922819$\Spuninst folder.

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

File Information

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

Windows 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 NameVersionDateTimeSizeFolder
6to4svc.dll5.1.2600.188616-Aug-200612:1495,232SP1QFE
Inetmib1.dll5.1.2600.188616-Aug-200612:1431,232SP1QFE
Iphlpapi.dll5.1.2600.188616-Aug-200612:1483,456SP1QFE
Ipv6.exe5.1.2600.188616-Aug-200609:2848,640SP1QFE
Ipv6mon.dll5.1.2600.188616-Aug-200612:1454,272SP1QFE
Netsh.exe5.1.2600.188616-Aug-200609:2783,456SP1QFE
Tcpip6.sys5.1.2600.188616-Aug-200609:28205,120SP1QFE
Tunmp.sys5.1.2600.188616-Aug-200609:2711,776SP1QFE
Ws2_32.dll5.1.2600.188616-Aug-200612:1470,656SP1QFE
Wship6.dll5.1.2600.188616-Aug-200612:1413,312SP1QFE
Xpob2res.dll5.1.2600.188616-Aug-200609:42159,232SP1QFE
6to4svc.dll5.1.2600.297516-Aug-200611:58100,352SP2GDR
Tcpip6.sys5.1.2600.297516-Aug-200609:37225,664SP2GDR
6to4svc.dll5.1.2600.297516-Aug-200612:08100,352SP2QFE
Tcpip6.sys5.1.2600.297516-Aug-200610:13225,664SP2QFE

Windows XP Professional x64:

File NameVersionDateTimeSizeCPUFolder
6to4svc.dll5.2.3790.277116-Aug-200614:43124,416x64SP1GDR
Tcpip6.sys5.2.3790.277116-Aug-200614:43362,240x64SP1GDR
W6to4svc.dll5.2.3790.277116-Aug-200614:4399,840x86SP1GDR\WOW
6to4svc.dll5.2.3790.277116-Aug-200614:34124,416x64SP1QFE
Tcpip6.sys5.2.3790.277116-Aug-200614:34362,240x64SP1QFE
W6to4svc.dll5.2.3790.277116-Aug-200614:3499,840x86SP1QFE\WOW

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

If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.

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

  • File Version Verification

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

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
  • Registry Key Verification

    You may also be able to verify the files that this security update has installed by reviewing the following registry 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\KB922819\Filelist

    For Windows XP Professional x64 Edition:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP2\KB922819\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 security update into the Windows installation source files.

Windows Server 2003 (all versions)

Prerequisites
This security update requires Windows Server 2003 or Windows Server 2003 Service Pack 1.

Note The security updates for Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 also apply to Microsoft Windows Server 2003 R2.

Inclusion in Future Service Packs
The update for this issue will be included in future Service Pack or Update Rollup.

Installation Information

This security update supports the following setup switches.

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

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

Deployment Information

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

Windowsserver2003-KB922819-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 KB922819.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-KB922819-x86-enu /norestart

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

Restart Requirement

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

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

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

Removal Information

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

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

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

File Information

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

Windows 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 NameVersionDateTimeSizeFolder
6to4svc.dll5.2.3790.57616-Aug-200613:4364,512RTMGDR
Tcpip6.sys5.2.3790.57616-Aug-200610:01203,904RTMGDR
6to4svc.dll5.2.3790.57616-Aug-200613:3564,512RTMQFE
Tcpip6.sys5.2.3790.57616-Aug-200610:16203,904RTMQFE
6to4svc.dll5.2.3790.277116-Aug-200613:5299,840SP1GDR
Tcpip6.sys5.2.3790.277116-Aug-200610:46225,600SP1GDR
6to4svc.dll5.2.3790.277116-Aug-200614:0199,840SP1QFE
Tcpip6.sys5.2.3790.277116-Aug-200611:52225,600SP1QFE

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 NameVersionDateTimeSizeCPUFolder
6to4svc.dll5.2.3790.57616-Aug-200614:34208,384IA-64RTMGDR
Tcpip6.sys5.2.3790.57616-Aug-200614:34642,560RTMGDR
W6to4svc.dll5.2.3790.57616-Aug-200614:3464,512x86RTMGDR\WOW
6to4svc.dll5.2.3790.57616-Aug-200614:34208,384IA-64RTMQFE
Tcpip6.sys5.2.3790.57616-Aug-200614:34642,560RTMQFE
W6to4svc.dll5.2.3790.57616-Aug-200614:3464,512x86RTMQFE\WOW
6to4svc.dll5.2.3790.277116-Aug-200614:42362,496IA-64SP1GDR
Tcpip6.sys5.2.3790.277116-Aug-200614:42735,872SP1GDR
W6to4svc.dll5.2.3790.277116-Aug-200614:4299,840x86SP1GDR\WOW
6to4svc.dll5.2.3790.277116-Aug-200614:34362,496IA-64SP1QFE
Tcpip6.sys5.2.3790.277116-Aug-200614:34735,872SP1QFE
W6to4svc.dll5.2.3790.277116-Aug-200614:3499,840x86SP1QFE\WOW

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 NameVersionDateTimeSizeCPUFolder
6to4svc.dll5.2.3790.277116-Aug-200614:43124,416x64SP1GDR
Tcpip6.sys5.2.3790.277116-Aug-200614:43362,240x64SP1GDR
W6to4svc.dll5.2.3790.277116-Aug-200614:4399,840x86SP1GDR\WOW
6to4svc.dll5.2.3790.277116-Aug-200614:34124,416x64SP1QFE
Tcpip6.sys5.2.3790.277116-Aug-200614:34362,240x64SP1QFE
W6to4svc.dll5.2.3790.277116-Aug-200614:3499,840x86SP1QFE\WOW

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

If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.

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

  • File Version Verification

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

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
  • Registry Key Verification

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

    Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003; Windows Server 2003, 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, 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:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP2\KB922819\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 security update into the Windows installation source files.

Other Information

Obtaining Other Security Updates:

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

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:

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 Scan Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.

Disclaimer:

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

Revisions:

  • V1.0 (October 10, 2006): Bulletin published.

Built at 2014-04-18T13:49:36Z-07:00

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.