Export (0) Print
Expand All

Microsoft Security Bulletin MS10-009 - Critical

Vulnerabilities in Windows TCP/IP Could Allow Remote Code Execution (974145)

Published: February 09, 2010 | Updated: February 10, 2010

Version: 1.1

General Information

Executive Summary

This security update resolves four privately reported vulnerabilities in Microsoft Windows. The most severe of these vulnerabilities could allow remote code execution if specially crafted packets are sent to a computer with IPv6 enabled. An attacker could try to exploit the vulnerability by creating specially crafted ICMPv6 packets and sending the packets to a system with IPv6 enabled. This vulnerability may only be exploited if the attacker is on-link.

This security update is rated Critical for Windows Vista and Windows Server 2008. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerabilities by changing the way Windows TCP/IP performs bounds checking and other packet handling operations. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

Recommendation. The majority of customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.

For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update immediately using update management software, or by checking for updates using the Microsoft Update service.

See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.

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

Operating SystemMaximum Security ImpactAggregate Severity RatingBulletins Replaced by this Update
Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 Remote Code ExecutionCriticalNone
Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 Remote Code ExecutionCriticalNone
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2*Remote Code ExecutionCriticalNone
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2*Remote Code ExecutionCriticalNone
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 Remote Code ExecutionCriticalNone

*Server Core installation affected. This update applies, with the same severity rating, to supported editions of Windows Server 2008, whether or not installed using the Server Core installation option. For more information on this installation option, see the MSDN article, Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.

Non-Affected Software

Operating System
Microsoft Windows 2000 Service Pack 4
Windows XP Service Pack 2 and Windows XP Service Pack 3
Windows XP Professional x64 Edition Service Pack 2
Windows Server 2003 Service Pack 2
Windows Server 2003 x64 Edition Service Pack 2
Windows Server 2003 with SP2 for Itanium-based Systems
Windows 7 for 32-bit Systems
Windows 7 for x64-based Systems
Windows Server 2008 R2 for x64-based Systems
Windows Server 2008 R2 for Itanium-based Systems

Where are the file information details? 
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.

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. For more information about the product lifecycle, visit the Microsoft Support Lifecycle Web site.

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. To determine the support lifecycle for your software release, see Select a Product for Lifecycle Information. For more information about service packs for these software releases, see Lifecycle Supported Service Packs.

Customers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country in the Contact Information list, 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 Microsoft Support Lifecycle Policy FAQ.

Vulnerability Information

The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the February bulletin summary. For more information, see Microsoft Exploitability Index.

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareICMPv6 Router Advertisement Vulnerability - CVE-2010-0239Header MDL Fragmentation Vulnerability – CVE-2010-0240ICMPv6 Route Information Vulnerability - CVE-2010-0241TCP/IP Selective Acknowledgement Vulnerability – CVE-2010-0242Aggregate Severity Rating
Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 Critical 
Remote Code Execution
Important 
Remote Code Execution
Critical 
Remote Code Execution
Important 
Denial of Service
Critical
Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 Critical 
Remote Code Execution
Important 
Remote Code Execution
Critical 
Remote Code Execution
Important 
Denial of Service
Critical
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2* Critical 
Remote Code Execution
Important 
Remote Code Execution
Critical 
Remote Code Execution
Important 
Denial of Service
Critical
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2* Critical 
Remote Code Execution
Important 
Remote Code Execution
Critical 
Remote Code Execution
Important 
Denial of Service
Critical
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 Critical 
Remote Code Execution
Important 
Remote Code Execution
Critical 
Remote Code Execution
Important 
Denial of Service
Critical

*Server Core installation affected. This update applies, with the same severity rating, to supported editions of Windows Server 2008, whether or not installed using the Server Core installation option. For more information on this installation option, see the MSDN article, Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.

A remote code execution vulnerability exists in the Windows TCP/IP stack due to insufficient bounds checking when processing specially crafted ICMPv6 Router Advertisement packets. An anonymous attacker could exploit the vulnerability by sending specially crafted ICMPv6 Router Advertisement packets to a computer with IPv6 enabled. 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-2010-0239.

Mitigating Factors for ICMPv6 Router Advertisement Vulnerability - CVE-2010-0239

Microsoft has not identified any mitigating factors for this vulnerability.

Workarounds for ICMPv6 Router Advertisement Vulnerability - CVE-2010-0239

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 the "Core Networking – Router Advertisement (ICMPv6-In)" inbound firewall rule

    To disable this firewall rule, run the following command from an elevated command prompt:

    netsh advfirewall firewall set rule name="Core Networking – Router Advertisement (ICMPv6-In)" dir=in new enable=No

    Impact of workaround. ICMPv6 router advertisements will be blocked. This could adversely impact IPv6 functionality in common deployment scenarios, where router discovery protocol is used for host configuration.

    How to undo the workaround.

    To re-enable this firewall rule, run the following command from an elevated command prompt:

    netsh advfirewall firewall set rule name="Core Networking – Router Advertisement (ICMPv6-In)" dir=in new enable=Yes

FAQ for ICMPv6 Router Advertisement Vulnerability - CVE-2010-0239

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 vulnerability is caused by the Windows TCP/IP stack not performing the appropriate level of bounds checking on specially crafted ICMPv6 Router Advertisement packets.

What is TCP/IP? 
TCP/IP is a set of networking protocols that are widely used on the Internet. TCP/IP provides communications across interconnected networks of computers that have diverse hardware architectures and that run various operating systems. 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 TechNet article, Overview of networking and TCP/IP.

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 see the TechNet site, FAQ for IPv6.

What are Router Advertisements? 
Router Advertisements allow routers to instruct hosts how to perform Address Autoconfiguration. For example, routers can specify whether hosts should use DHCPv6 and/or autonomous (stateless) address configuration. Routers advertise their presence together with various link and Internet parameters either periodically, or in response to a Router Solicitation message. Router Advertisements contain prefixes that are used for determining whether another address shares the same link (on-link determination) and/or address configuration, a suggested hop limit value, etc. For more information about Router Advertisements and Neighbor Discovery in IPv6, see RFC 4861.

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 ICMPv6 packets and sending the packets to a system with IPv6 enabled. This vulnerability may only be exploited if the attacker is on-link. Tunneling protocols, such as ISATAP, may effectively allow attackers to deliver the corrupted packet to the target machine even if the attacker is not present on the same physical link.

When is an attacker considered "on-link"? 
For purposes of this vulnerability, an attacker is considered on-link if they are on the same physical or virtual link and are able to send a valid neighbor discovery message to the target host. An example of a virtual link is one that occurs via an ISATAP tunnel. For more information about on-link addresses and Neighbor Discovery in IPv6, see RFC 4861.

What systems are primarily at risk from the vulnerability? 
All operating systems with the IPv6 features enabled are at risk from this vulnerability. By default all the supported features for IPv6 are enabled in Windows Vista and Windows Server 2008.

What does the update do? 
The update addresses this vulnerability by changing the manner in which the Windows TCP/IP stack performs bounds checking on specially crafted ICMPv6 Router Advertisement packets.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.

A remote code execution vulnerability exists in the Windows TCP/IP stack due to the manner in which the TCP/IP stack handles specially crafted Encapsulating Security Payloads (ESP) over UDP datagram fragments when running a custom network driver. 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-2010-0240.

Mitigating Factors for Header MDL Fragmentation Vulnerability - CVE-2010-0240

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:

  • This vulnerability only impacts Windows systems if they have installed a custom network driver that splits the UDP header into multiple MDLs. Microsoft is not aware of any driver that takes this action.

Workarounds for Header MDL Fragmentation Vulnerability - CVE-2010-0240

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:

  • Enable advanced TCP/IP filtering on systems that support this feature

    To help protect from network-based attempts to exploit this vulnerability, enable advanced TCP/IP filtering on systems that support this feature. You can enable advanced TCP/IP filtering to block all unsolicited inbound traffic. For more information about how to configure TCP/IP filtering, see Microsoft Knowledge Base Article 309798.

FAQ for Header MDL Fragmentation Vulnerability - CVE-2010-0240

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 vulnerability is caused by the Windows TCP/IP stack not handling specially crafted IP datagram fragments when running a custom network driver.

What is TCP/IP? 
TCP/IP is a set of networking protocols that are widely used on the Internet. TCP/IP provides communications across interconnected networks of computers that have diverse hardware architectures and that run various operating systems. 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 TechNet article, Overview of networking and TCP/IP.

What is an Encapsulating Security Payload (ESP)? 
Encapsulating Security Payload (ESP) provides confidentiality (in addition to authentication, integrity, and anti-replay protection) for the IP payload. ESP in transport mode does not sign the entire packet. Only the IP payload (not the IP header) is protected. ESP can be used alone or in combination with Authentication Header (AH).

What is a Memory Descriptor List (MDL)? 
A memory descriptor list (MDL) is a system-defined structure that describes a buffer by a set of physical addresses. A driver that performs direct I/O receives a pointer to an MDL from the I/O manager, and reads and writes data through the MDL. Some drivers also use MDLs when they perform direct I/O to satisfy a device I/O control request. For more information about MDLs, see the Windows Hardware Developer Central article, What is really in that MDL?

Does this attack require the UDP traffic to be fragmented? 
No. This attack does not rely on fragmented network traffic. Instead, the fragmentation involved requires the network driver on the target system to fragment the UDP header into separate MDLs.

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 IP datagram fragments and sending the packets to a system with a custom network driver installed.

What systems are primarily at risk from the vulnerability? 
All affected operating systems may be at risk from this vulnerability if they have installed a custom network driver that splits the UDP header into multiple MDLs. No network drivers that ship with Windows can take this action. Microsoft is not aware of any network driver that can take this action.

What does the update do? 
The update addresses this vulnerability by changing the manner in which the Windows TCP/IP stack handles specially crafted ESP over UDP datagrams.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.

A remote code execution vulnerability exists in the Windows TCP/IP stack due to insufficient bounds checking when processing specially crafted ICMPv6 Route Information packets. An anonymous attacker could exploit the vulnerability by sending specially crafted ICMPv6 Route Information packets to a computer with IPv6 enabled. 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-2010-0241.

Mitigating Factors for ICMPv6 Route Information Vulnerability - CVE-2010-0241

Microsoft has not identified any mitigating factors for this vulnerability.

Workarounds for ICMPv6 Route Information Vulnerability - CVE-2010-0241

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 the "Core Networking – Router Advertisement (ICMPv6-In)" inbound firewall rule

    To disable this firewall rule, run the following command from an elevated command prompt:

    netsh advfirewall firewall set rule name="Core Networking – Router Advertisement (ICMPv6-In)" dir=in new enable=No

    Impact of workaround. ICMPv6 router advertisements will be blocked. This could adversely impact IPv6 functionality in common deployment scenarios, where router discovery protocol is used for host configuration.

    How to undo the workaround.

    To re-enable this firewall rule, run the following command from an elevated command prompt:

    netsh advfirewall firewall set rule name="Core Networking – Router Advertisement (ICMPv6-In)" dir=in new enable=Yes

FAQ for ICMPv6 Route Information Vulnerability - CVE-2010-0241

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 vulnerability is caused by the Windows TCP/IP stack not performing the appropriate level of bounds checking on specially crafted ICMPv6 Route Information packets.

What is TCP/IP? 
TCP/IP is a set of networking protocols that are widely used on the Internet. TCP/IP provides communications across interconnected networks of computers that have diverse hardware architectures and that run various operating systems. 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 TechNet article, Overview of networking and TCP/IP.

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, auto-configuration, and extensibility. To learn more about IPv6, please see the TechNet site, FAQ for IPv6.

What are Router Advertisements? 
Router Advertisements allow routers to instruct hosts how to perform Address Autoconfiguration. For example, routers can specify whether hosts should use DHCPv6 and/or autonomous (stateless) address configuration. Routers advertise their presence together with various link and Internet parameters either periodically, or in response to a Router Solicitation message. Router Advertisements contain prefixes that are used for determining whether another address shares the same link (on-link determination) and/or address configuration, a suggested hop limit value, etc. For more information about Router Advertisements and Neighbor Discovery in IPv6, see RFC 4861.

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 ICMPv6 packets and sending the packets to a system with IPv6 enabled. This vulnerability may only be exploited if the attacker is on-link. Tunneling protocols, such as ISATAP, may effectively allow attackers to deliver the corrupted packet to the target machine even if the attacker is not present on the same physical link.

When is an attacker considered "on-link"? 
For purposes of this vulnerability, an attacker is considered on-link if they are on the same physical or virtual link and are able to send a valid neighbor discovery message to the target host. An example of a virtual link is one that occurs via an ISATAP tunnel. For more information about on-link addresses and Neighbor Discovery in IPv6, see RFC 4861.

What systems are primarily at risk from the vulnerability? 
All operating systems with the IPv6 features enabled are at risk from this vulnerability. By default all the supported features for IPv6 are enabled in Windows Vista and Windows Server 2008.

What does the update do? 
The update addresses this vulnerability by changing the manner in which the Windows TCP/IP stack performs bounds checking on specially crafted ICMPv6 Router Information packets.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.

A denial of service vulnerability exists in TCP/IP processing in Microsoft Windows due to an error in the processing of specially crafted TCP packets with a malformed selective acknowledgment (SACK) value. An attacker could exploit the vulnerability by sending the target system a small number of specially crafted packets causing the affected system to stop responding and automatically restart.

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

Mitigating Factors for TCP/IP Selective Acknowledgement Vulnerability - CVE-2010-0242

Microsoft has not identified any mitigating factors for this vulnerability.

Workarounds for TCP/IP Selective Acknowledgement Vulnerability - CVE-2010-0242

Microsoft has not identified any workarounds for this vulnerability.

FAQ for TCP/IP Selective Acknowledgement Vulnerability - CVE-2010-0242

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. 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 vulnerability is caused by the Windows TCP/IP stack not properly handling malformed TCP SACK values.

What is TCP/IP? 
TCP/IP is a set of networking protocols that are widely used on the Internet. TCP/IP provides communications across interconnected networks of computers that have diverse hardware architectures and that run various operating systems. 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 TechNet article, Overview of networking and TCP/IP.

What is TCP/IP Selective Acknowledgement (SACK)? 
Selective acknowledgment (SACK) is used for connections with large TCP window sizes. When SACK is enabled, if a packet or series of packets is dropped the receiver can inform the sender of exactly which data has been received and where the holes in the data are. The sender can then selectively retransmit the missing data without needing to retransmit blocks of data that have already been received successfully. Prior to SACK, which was added to the Windows TCP/IP stack in Microsoft Windows 2000, a receiver could only acknowledge the latest sequence number of contiguous data that had been received, or the left edge of the receive window. For more information about SACK, see the MSDN article, Windows TCP Implementation Features.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could cause an affected system to become non-responsive.

How could an attacker exploit the vulnerability? 
An attacker could exploit the vulnerability by sending a system a small number of specially crafted TCP packets with a malformed selective acknowledgment (SACK) value.

What systems are primarily at risk from the vulnerability? 
All affected operating systems are at risk from this vulnerability.

What does the update do? 
The update addresses this vulnerability by correcting the manner in which the Windows TCP/IP stack handles malformed TCP SACK values.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.

Update Information

Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems 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 and Windows 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.

Note Microsoft discontinued support for Office Update and the Office Update Inventory Tool as of August 1, 2009. To continue getting the latest updates for Microsoft Office products, use Microsoft Update. For more information, see About Microsoft Office Update: Frequently Asked Questions.

Detection and Deployment Guidance

Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see Microsoft Knowledge Base Article 961747.

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.1.1
Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2Yes
Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2Yes
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2Yes
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2Yes
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2Yes

The latest version of MBSA has been released: Microsoft Baseline Security Analyzer 2.1.1. For more information, see Microsoft Baseline Security Analyzer 2.1.

Windows Server Update Services

By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Microsoft Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000. 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.

SoftwareSMS 2.0SMS 2003 with SUITSMS 2003 with ITMUConfiguration Manager 2007
Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2NoNoYesYes
Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2NoNoYesYes
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2NoNoYesYes
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2NoNoYesYes
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2NoNoYesYes

For SMS 2.0 and SMS 2003, 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. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.

System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007.

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.

Update Compatibility Evaluator and Application Compatibility Toolkit

Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit.

The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.

Affected Software

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

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 interventionFor all supported 32-bit editions of Windows Vista:
Windows6.0-KB974145-x86 /quiet
For all supported x64-based editions of Windows Vista:
Windows6.0-KB974145-x64 /quiet
Installing without restartingFor all supported 32-bit editions of Windows Vista:
Windows6.0-KB974145-x86 /quiet /norestart
For all supported x64-based editions of Windows Vista:
Windows6.0-KB974145-x64 /quiet /norestart
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?Yes, you must restart your system after you apply this security update.
HotPatchingNot applicable.
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 Microsoft Knowledge Base Article 974145
Registry Key Verification Note A registry key does not exist to validate the presence of this update.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

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

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/?, /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 editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start and then enter an update file name in Start Search.
    2. When the file appears under Programs, right-click on the file name and click Properties.
    3. Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
    4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
    5. Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Windows Server 2008 (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 interventionFor all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB974145-x86 /quiet
For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB974145-x64 /quiet
For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB974145-ia64 /quiet
Installing without restartingFor all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB974145-x86 /quiet /norestart
For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB974145-x64 /quiet /norestart
For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB974145-ia64 /quiet /norestart
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?Yes, you must restart your system after you apply this security update.
HotPatchingNot applicable.
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 Microsoft Knowledge Base Article 974145
Registry Key Verification Note A registry key does not exist to validate the presence of this update.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

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

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/?, /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 editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start and then enter an update file name in Start Search.
    2. When the file appears under Programs, right-click on the file name and click Properties.
    3. Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
    4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
    5. Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Other Information

Acknowledgments

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

  • Sumit Gwalani, Drew Hintz, and Neel Mehta of Google Security Team for reporting the ICMPv6 Router Advertisement Vulnerability (CVE-2010-0239)
  • Sumit Gwalani, Drew Hintz, and Neel Mehta of Google Security Team for reporting the Header MDL Fragmentation Vulnerability (CVE-2010-0240)
  • Sumit Gwalani, Drew Hintz, and Neel Mehta of Google Security Team for reporting the ICMPv6 Route Information Vulnerability (CVE-2010-0241)

Microsoft Active Protections Program (MAPP)

To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.

Support

  • Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support.
  • 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 (February 9, 2010): Bulletin published.
  • V1.1 (February 10, 2010): Corrected the command-line information for the Disable the "Core Networking - Router Advertisement (ICMPv6-In)" inbound firewall rule workaround. This is an informational change only.

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

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft