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

Microsoft Security Bulletin MS10-098 - Important

Vulnerabilities in Windows Kernel-Mode Drivers Could Allow Elevation of Privilege (2436673)

Published: December 14, 2010

Version: 1.0

General Information

Executive Summary

This security update resolves one publicly disclosed vulnerability and several privately reported vulnerabilities in Microsoft Windows. The vulnerabilities could allow elevation of privilege if an attacker logged on locally and ran a specially crafted application. An attacker must have valid logon credentials and be able to log on locally to exploit these vulnerabilities. The vulnerabilities could not be exploited remotely or by anonymous users.

This security update is rated Important for all supported versions of Microsoft Windows. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerabilities by correcting the way the Windows kernel-mode drivers allocate memory, free objects that are no longer in use, manage kernel-mode driver objects, and validate input passed from user mode. 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 at the earliest opportunity 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 XP Service Pack 3Elevation of PrivilegeImportantMS10-073
Windows XP Professional x64 Edition Service Pack 2Elevation of PrivilegeImportantMS10-073
Windows Server 2003 Service Pack 2Elevation of PrivilegeImportantMS10-073
Windows Server 2003 x64 Edition Service Pack 2Elevation of PrivilegeImportantMS10-073
Windows Server 2003 with SP2 for Itanium-based SystemsElevation of PrivilegeImportantMS10-073
Windows Vista Service Pack 1 and Windows Vista Service Pack 2Elevation of PrivilegeImportantMS10-073
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2Elevation of PrivilegeImportantMS10-073
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2*Elevation of PrivilegeImportantMS10-073
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2*Elevation of PrivilegeImportantMS10-073
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2Elevation of PrivilegeImportantMS10-073
Windows 7 for 32-bit SystemsElevation of PrivilegeImportantMS10-073
Windows 7 for x64-based SystemsElevation of PrivilegeImportantMS10-073
Windows Server 2008 R2 for x64-based Systems*Elevation of PrivilegeImportantMS10-073
Windows Server 2008 R2 for Itanium-based SystemsElevation of PrivilegeImportantMS10-073

*Server Core installation affected. This update applies, with the same severity rating, to supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, whether or not installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, Managing a Server Core Installation and Servicing a Server Core Installation. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.

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 December bulletin summary. For more information, see Microsoft Exploitability Index.

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareWin32k Buffer Overflow Vulnerability - CVE-2010-3939Win32k PFE Pointer Double Free Vulnerability - CVE-2010-3940Win32k Double Free Vulnerability - CVE-2010-3941Win32k WriteAV Vulnerability - CVE-2010-3942Win32k Cursor Linking Vulnerability- CVE-2010-3943Win32k Memory Corruption Vulnerability - CVE-2010-3944Aggregate Severity Rating
Windows XP Service Pack 3Important 
Elevation of Privilege
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Not applicableImportant
Windows XP Professional x64 Edition Service Pack 2Important 
Elevation of Privilege
Important 
Elevation of Privilege
Moderate 
Defense in Depth
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Not applicableImportant
Windows Server 2003 Service Pack 2Important 
Elevation of Privilege
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Not applicableImportant
Windows Server 2003 x64 Edition Service Pack 2Important 
Elevation of Privilege
Important 
Elevation of Privilege
Moderate 
Defense in Depth
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Not applicableImportant
Windows Server 2003 with SP2 for Itanium-based SystemsImportant 
Elevation of Privilege
Important 
Elevation of Privilege
Moderate 
Defense in Depth
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Not applicableImportant
Windows Vista Service Pack 1 and Windows Vista Service Pack 2Important 
Elevation of Privilege
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Not applicableImportant
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2Important 
Elevation of Privilege
Important 
Elevation of Privilege
Moderate 
Defense in Depth
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Not applicableImportant
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2*Important 
Elevation of Privilege
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Not applicableImportant
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2*Important 
Elevation of Privilege
Important 
Elevation of Privilege
Moderate 
Defense in Depth
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Not applicableImportant
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2Important 
Elevation of Privilege
Important 
Elevation of Privilege
Moderate 
Defense in Depth
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Not applicableImportant
Windows 7 for 32-bit SystemsImportant 
Elevation of Privilege
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Important
Windows 7 for x64-based SystemsImportant 
Elevation of Privilege
Important 
Elevation of Privilege
Not applicableImportant 
Elevation of Privilege
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Important
Windows Server 2008 R2 for x64-based Systems*Important 
Elevation of Privilege
Important 
Elevation of Privilege
Not applicableImportant 
Elevation of Privilege
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Important
Windows Server 2008 R2 for Itanium-based SystemsImportant 
Elevation of Privilege
Important 
Elevation of Privilege
Not applicableImportant 
Elevation of Privilege
Important 
Elevation of Privilege
Important 
Elevation of Privilege
Important

*Server Core installation affected. This update applies, with the same severity rating, to supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, whether or not installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, Managing a Server Core Installation and Servicing a Server Core Installation. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.

An elevation of privilege vulnerability exists in the way that Windows kernel-mode drivers improperly allocate memory when copying data from user mode. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. 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-3939.

Mitigating factors for Win32k Buffer Overflow Vulnerability - CVE-2010-3939

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:

  • An attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability. The vulnerability could not be exploited remotely or by anonymous users.

Workarounds for Win32k Buffer Overflow Vulnerability - CVE-2010-3939

Microsoft has not identified any workarounds for this vulnerability.

FAQ for Win32k Buffer Overflow Vulnerability - CVE-2010-3939

What is the scope of the vulnerability? 
This is an elevation of privilege vulnerability. An attacker who successfully exploited this vulnerability could execute arbitrary code and 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.

What causes the vulnerability? 
The vulnerability is caused when the Windows kernel-mode drivers do not properly allocate memory when copying data from user mode.

What is the Windows component affected by the vulnerability? 
Win32k.sys is the Windows component affected by the vulnerability.

What is the Windows kernel-mode driver (win32k.sys)? 
Win32k.sys is a kernel-mode device driver and is the kernel part of the Windows subsystem. It contains the window manager, which controls window displays; manages screen output; collects input from the keyboard, mouse, and other devices; and passes user messages to applications. It also contains the graphics device interface (GDI), which is a library of functions for graphics output devices. Finally, it serves as a wrapper for DirectX support that is implemented in another driver (dxgkrnl.sys).

What is the Windows kernel? 
The Windows kernel is the core of the operating system. It provides system-level services such as device management and memory management, allocates processor time to processes, and manages error handling.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. 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? 
To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take complete control over an affected system.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The update addresses the vulnerability by correcting the way the Windows kernel-mode drivers allocate memory.

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-2010-3939.

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.

An elevation of privilege vulnerability exists due to the way that the Windows kernel-mode drivers free objects that are no longer in use. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. 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-3940.

Mitigating Factors for Win32k PFE Pointer Double Free Vulnerability - CVE-2010-3940

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:

  • An attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability. The vulnerability could not be exploited remotely or by anonymous users.

Workarounds for Win32k PFE Pointer Double Free Vulnerability - CVE-2010-3940

Microsoft has not identified any workarounds for this vulnerability.

FAQ for Win32k PFE Pointer Double Free Vulnerability - CVE-2010-3940

What is the scope of the vulnerability? 
This is an elevation of privilege vulnerability. An attacker who successfully exploited this vulnerability could execute arbitrary code and 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.

What causes the vulnerability? 
The vulnerability is caused by a "double free" condition involving a pointer to a kernel-mode driver object.

What is a "double free" condition? 
A double free condition is a condition in which a program is caused to release or free allocated memory more than once. Releasing memory that has already been freed could lead to memory corruption. An attacker could add arbitrary code to memory that is then executed when the corruption occurs. This code could then be executed at a system level of privilege.

What is the Windows component affected by the vulnerability? 
Win32k.sys is the Windows component affected by the vulnerability.

What is the Windows kernel-mode driver (win32k.sys)? 
Win32k.sys is a kernel-mode device driver and is the kernel part of the Windows subsystem. It contains the window manager, which controls window displays; manages screen output; collects input from the keyboard, mouse, and other devices; and passes user messages to applications. It also contains the graphics device interface (GDI), which is a library of functions for graphics output devices. Finally, it serves as a wrapper for DirectX support that is implemented in another driver (dxgkrnl.sys).

What is the Windows kernel? 
The Windows kernel is the core of the operating system. It provides system-level services such as device management and memory management, allocates processor time to processes, and manages error handling.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. 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? 
To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take complete control over an affected system.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The update addresses this vulnerability by correcting the way the kernel-mode drivers free objects that are no longer in use.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through coordinated vulnerability 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.

An elevation of privilege vulnerability exists due to the way that the Windows kernel-mode drivers free objects that are no longer in use. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. 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-3941.

Mitigating Factors for Win32k Double Free Vulnerability - CVE-2010-3941

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:

  • An attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability. The vulnerability could not be exploited remotely or by anonymous users.
  • An affected system must be able to run 16-bit programs for an attacker to be able to exploit this vulnerability. The vulnerability cannot be exploited on 64-bit servers because they cannot run 16-bit programs.

Workarounds for Win32k Double Free Vulnerability - CVE-2010-3941

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 NTVDM subsystem by editing group policy

    Users who do not require NT Virtual DOS Mode (NTVDM), can mitigate exploitation of this vulnerability by disabling the NTVDM subsystem.

    To disable the NTVDM subsystem on Windows XP systems:

    1. While logged on with administrator privileges, click Start, click Run, type gpedit.msc, and then click OK.
    2. In the Group Policy editor's navigation pane, double-click Administrative Templates, double-click Windows Components, and then click Application Compatibility.
    3. In the Application Compatibility pane, double-click Prevent access to 16-bit applications, change the selection on the Setting tab to Enabled, click OK, and then exit the Group Policy editor.

    For Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2 systems, this setting can be deployed by group policy using the same template used for Windows XP systems.

    For Windows NT 4.0 systems, see the Microsoft Knowledge Base article, Disabling the MSDOS and WOWEXEC Subsystems on Terminal Server.

    Impact of workaround.  Access to 16-bit applications will be disabled.

    How to undo the workaround.  

    To re-enable the NTVDM subsystem on Windows XP systems:

    1. While logged on with administrator privileges, click Start, click Run, type gpedit.msc, and then click OK.
    2. In the Group Policy editor's navigation pane, double-click Administrative Templates, double-click Windows Components, and then click Application Compatibility.
    3. In the Application Compatibility pane, double-click Prevent access to 16-bit applications, change the selection on the Setting tab to Not Configured, click OK, and then exit the Group Policy editor.

    For Windows Server 2003, Windows server 2008, and Windows Server 2008 R2 systems, this setting can be deployed by group policy using the same template used for Windows XP systems.

    For Windows NT 4.0 systems, see the Microsoft Knowledge Base article, Disabling the MSDOS and WOWEXEC Subsystems on Terminal Server.

  • Disable the NTVDM subsystem by editing the system registry

    Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use the Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    Note We recommend backing up the registry before you edit it.

    To disable the NTVDM subsystem by editing the system registry, perform the following steps:

    1. Click Start, click Run, type regedit, and then click OK.
    2. Locate the following key in the system registry:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WOW
    3. Add a DWORD entry named DisallowedPolicyDefault and set its value to 1 (this effectively disables NTVDM).
    4. Close Registry Editor.

    Impact of workaround. Access to 16-bit applications will be disabled.

    How to undo the workaround. 

    To re-enable the NTVDM subsystem by editing the system registry, follow these steps:

    1. Click Start, click Run, type regedit, and then click OK.
    2. Locate the following key in the system registry:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WOW
    3. Change the DisallowedPolicyDefault value to 0 (this effectively re-enables NTVDM).
    4. Close Registry Editor.

FAQ for Win32k Double Free Vulnerability - CVE-2010-3941

What is the scope of the vulnerability? 
This is an elevation of privilege vulnerability. An attacker who successfully exploited this vulnerability could execute arbitrary code and 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.

What causes the vulnerability? 
The vulnerability is caused by a "double free" condition involving a pointer to a kernel-mode driver object.

What is a "double free" condition? 
A double free condition is a condition in which a program is caused to release or free allocated memory more than once. Releasing memory that has already been freed could lead to memory corruption. An attacker could add arbitrary code to memory that is then executed when the corruption occurs. This code could then be executed at a system level of privilege.

What is the Windows component affected by the vulnerability? 
Win32k.sys is the Windows component affected by the vulnerability.

What is the Windows kernel-mode driver (win32k.sys)? 
Win32k.sys is a kernel-mode device driver and is the kernel part of the Windows subsystem. It contains the window manager, which controls window displays; manages screen output; collects input from the keyboard, mouse, and other devices; and passes user messages to applications. It also contains the graphics device interface (GDI), which is a library of functions for graphics output devices. Finally, it serves as a wrapper for DirectX support that is implemented in another driver (dxgkrnl.sys).

What is the Windows kernel? 
The Windows kernel is the core of the operating system. It provides system-level services such as device management and memory management, allocates processor time to processes, and manages error handling.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. 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? 
To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take complete control over an affected system.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The update addresses this vulnerability by correcting the way the kernel-mode drivers free objects that are no longer in use.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through coordinated vulnerability 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.

An elevation of privilege vulnerability exists in the way that Windows kernel-mode drivers improperly allocate memory when copying data from user mode. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. 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-3942.

Mitigating Factors for Win32k WriteAV Vulnerability - CVE-2010-3942

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:

  • An attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability. The vulnerability could not be exploited remotely or by anonymous users.

Workarounds for Win32k WriteAV Vulnerability - CVE-2010-3942

Microsoft has not identified any workarounds for this vulnerability.

FAQ for Win32k WriteAV Vulnerability - CVE-2010-3942

What is the scope of the vulnerability? 
This is an elevation of privilege vulnerability. An attacker who successfully exploited this vulnerability could execute arbitrary code and 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.

What causes the vulnerability? 
The vulnerability is caused when the Windows kernel-mode drivers do not properly allocate memory when copying data from user mode.

What is the Windows component affected by the vulnerability? 
Win32k.sys is the Windows component affected by the vulnerability.

What is the Windows kernel-mode driver (win32k.sys)? 
Win32k.sys is a kernel-mode device driver and is the kernel part of the Windows subsystem. It contains the window manager, which controls window displays; manages screen output; collects input from the keyboard, mouse, and other devices; and passes user messages to applications. It also contains the graphics device interface (GDI), which is a library of functions for graphics output devices. Finally, it serves as a wrapper for DirectX support that is implemented in another driver (dxgkrnl.sys).

What is the Windows kernel? 
The Windows kernel is the core of the operating system. It provides system-level services such as device management and memory management, allocates processor time to processes, and manages error handling.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. 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? 
To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take complete control over an affected system.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The update addresses the vulnerability by correcting the way the Windows kernel-mode drivers allocate memory.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through coordinated vulnerability 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.

An elevation of privilege vulnerability exists due to the way that Windows Kernel-mode drivers manage kernel-mode driver objects. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. 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-3943.

Mitigating Factors for Win32k Cursor Linking Vulnerability- CVE-2010-3943

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:

  • An attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability. The vulnerability could not be exploited remotely or by anonymous users.

Workarounds for Win32k Cursor Linking Vulnerability- CVE-2010-3943

Microsoft has not identified any workarounds for this vulnerability.

FAQ for Win32k Cursor Linking Vulnerability- CVE-2010-3943

What is the scope of the vulnerability? 
This is an elevation of privilege vulnerability. An attacker who successfully exploited this vulnerability could execute arbitrary code and 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.

What causes the vulnerability? 
The vulnerability is caused by a logic error that occurs when linking kernel-mode driver objects, leading to a corrupted linked list.

What is the Windows component affected by the vulnerability? 
Win32k.sys is the Windows component affected by the vulnerability.

What is the Windows kernel-mode driver (win32k.sys)? 
Win32k.sys is a kernel-mode device driver and is the kernel part of the Windows subsystem. It contains the window manager, which controls window displays; manages screen output; collects input from the keyboard, mouse, and other devices; and passes user messages to applications. It also contains the graphics device interface (GDI), which is a library of functions for graphics output devices. Finally, it serves as a wrapper for DirectX support that is implemented in another driver (dxgkrnl.sys).

What is the Windows kernel? 
The Windows kernel is the core of the operating system. It provides system-level services such as device management and memory management, allocates processor time to processes, and manages error handling.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. 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? 
To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take complete control over an affected system.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The update addresses this vulnerability by correcting the way the kernel-mode drivers manage kernel-mode driver objects.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through coordinated vulnerability 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.

An elevation of privilege vulnerability exists in the way that the Windows kernel-mode drivers improperly validate input passed from user mode. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. 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-3944.

Mitigating Factors for Win32k Memory Corruption Vulnerability - CVE-2010-3944

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:

  • An attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability. The vulnerability could not be exploited remotely or by anonymous users.

Workarounds for Win32k Memory Corruption Vulnerability - CVE-2010-3944

Microsoft has not identified any workarounds for this vulnerability.

FAQ for Win32k Memory Corruption Vulnerability - CVE-2010-3944

What is the scope of the vulnerability? 
This is an elevation of privilege vulnerability. An attacker who successfully exploited this vulnerability could execute arbitrary code and 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.

What causes the vulnerability? 
The vulnerability is caused by the Windows kernel-mode drivers not properly validating input passed from user mode.

What is the Windows component affected by the vulnerability? 
Win32k.sys is the Windows component affected by the vulnerability.

What is the Windows kernel-mode driver (win32k.sys)? 
Win32k.sys is a kernel-mode device driver and is the kernel part of the Windows subsystem. It contains the window manager, which controls window displays; manages screen output; collects input from the keyboard, mouse, and other devices; and passes user messages to applications. It also contains the graphics device interface (GDI), which is a library of functions for graphics output devices. Finally, it serves as a wrapper for DirectX support that is implemented in another driver (dxgkrnl.sys).

What is the Windows kernel? 
The Windows kernel is the core of the operating system. It provides system-level services such as device management and memory management, allocates processor time to processes, and manages error handling.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. 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? 
To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take complete control over an affected system.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The update addresses the vulnerability by correcting the way the Windows kernel-mode drivers validate input passed from user mode.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through coordinated vulnerability 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

Security Central

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.

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
Windows XP Service Pack 3Yes
Windows XP Professional x64 Edition Service Pack 2Yes
Windows Server 2003 Service Pack 2Yes
Windows Server 2003 x64 Edition Service Pack 2Yes
Windows Server 2003 with SP2 for Itanium-based SystemsYes
Windows Vista Service Pack 1 and Windows Vista Service Pack 2Yes
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
Windows 7 for 32-bit SystemsYes
Windows 7 for x64-based SystemsYes
Windows Server 2008 R2 for x64-based SystemsYes
Windows Server 2008 R2 for Itanium-based SystemsYes

Note For customers using legacy software not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, please visit Microsoft Baseline Security Analyzer and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools.

Windows Server Update Services

Windows Server Update Services (WSUS) enables information technology administrators to deploy the latest Microsoft product updates to computers that are running the Windows operating system. For more information about how to deploy security updates using Windows Server Update Services, see the TechNet article, Windows Server Update Services.

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 XP Service Pack 3YesYesYesYes
Windows XP Professional x64 Edition Service Pack 2NoNoYesYes
Windows Server 2003 Service Pack 2YesYesYesYes
Windows Server 2003 x64 Edition Service Pack 2NoNoYesYes
Windows Server 2003 with SP2 for Itanium-based SystemsNoNoYesYes
Windows Vista Service Pack 1 and Windows Vista Service Pack 2NoNoYesYes
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
Windows 7 for 32-bit SystemsNoNoYesYes
Windows 7 for x64-based SystemsNoNoYesYes
Windows Server 2008 R2 for x64-based SystemsNoNoYesYes
Windows Server 2008 R2 for Itanium-based SystemsNoNoYesYes

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 XP (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service PacksThe update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionFor Windows XP Service Pack 3:
WindowsXP-KB2436673-x86-enu.exe /quiet
For Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB2436673-x64-enu.exe /quiet
Installing without restartingFor Windows XP Service Pack 3:
WindowsXP-KB2436673-x86-enu.exe /norestart
For Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB2436673-x64-enu.exe /norestart
Update log fileKB2436673.log
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 InformationUse Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB2436673$\Spuninst folder
File InformationSee Microsoft Knowledge Base Article 2436673
Registry Key VerificationFor all supported 32-bit editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2436673\Filelist
For all supported x64-based editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB2436673\Filelist

Note For supported versions of Windows XP Professional x64 Edition, this security update is the same as supported versions of the Windows Server 2003 x64 Edition security 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.

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 installer, see Microsoft Knowledge Base Article 832475.

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
/helpDisplays the command-line options.
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed.
/forcerestartRestarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestartDisplays a dialog box prompting the local user to allow a restart.
Special Options
/overwriteoemOverwrites OEM files without prompting.
/nobackupDoes not back up files needed for uninstall.
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows the redirection of installation log files.
/integrate:pathIntegrates 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.
/EREnables extended error reporting.
/verboseEnables 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.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options.
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestartDisplays a dialog box prompting the local user to allow a restart.
Special Options
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows the redirection of installation log files.

Verifying That the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

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

  • File Version Verification

    Because there are several 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 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 edition of the operating system, or the programs that are installed on your system, 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 system by comparing it to the version that is documented in the appropriate file information table.

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

    You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.

    These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Windows Server 2003 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service PacksThe 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 2003:
WindowsServer2003-KB2436673-x86-enu.exe /quiet
For all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB2436673-x64-enu.exe /quiet
For all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB2436673-ia64-enu.exe /quiet
Installing without restartingFor all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB2436673-x86-enu.exe /norestart
For all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB2436673-x64-enu.exe /norestart
For all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB2436673-ia64-enu.exe /norestart
Update log fileKB2436673.log
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.
HotPatchingThis security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.
Removal InformationUse Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB2436673$\Spuninst folder
File InformationSee Microsoft Knowledge Base Article 2436673
Registry Key VerificationHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2436673\Filelist

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.

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 installer, see Microsoft Knowledge Base Article 832475.

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
/helpDisplays the command-line options.
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed.
/forcerestartRestarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestartDisplays a dialog box prompting the local user to allow a restart.
Special Options
/overwriteoemOverwrites OEM files without prompting.
/nobackupDoes not back up files needed for uninstall.
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows the redirection of installation log files.
/integrate:pathIntegrates 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.
/EREnables extended error reporting.
/verboseEnables 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.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options.
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed.
/forcerestartRestarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestartDisplays a dialog box prompting the local user to allow a restart.
Special Options
/forceappscloseForces other programs to close when the computer shuts down.
/log:pathAllows the redirection of installation log files.

Verifying that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

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

  • File Version Verification

    Because there are several 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 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 edition of the operating system, or the programs that are installed on your system, 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 system by comparing it to the version that is documented in the appropriate file information table.

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

    You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.

    These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Windows Vista (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service PacksThe 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-KB2436673-x86.msu /quiet
For all supported x64-based editions of Windows Vista:
Windows6.0-KB2436673-x64.msu /quiet
Installing without restartingFor all supported 32-bit editions of Windows Vista:
Windows6.0-KB2436673-x86.msu /quiet /norestart
For all supported x64-based editions of Windows Vista:
Windows6.0-KB2436673-x64.msu /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 InformationWUSA.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 InformationSee Microsoft Knowledge Base Article 2436673
Registry Key VerificationNote 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, /helpDisplays help on supported switches.
/quietSuppresses the display of status or error messages.
/norestartWhen 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 the Start Search box.
    2. When the file appears under Programs, right-click the file name and click Properties.
    3. On the General tab, compare the file size with the file information tables provided in the bulletin KB article.

      Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
    4. You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.

      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.
    5. Finally, you can also click 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 PacksThe 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-KB2436673-x86.msu /quiet
For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB2436673-x64.msu /quiet
For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB2436673-ia64.msu /quiet
Installing without restartingFor all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB2436673-x86.msu /quiet /norestart
For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB2436673-x64.msu /quiet /norestart
For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB2436673-ia64.msu /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 InformationWUSA.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 InformationSee Microsoft Knowledge Base Article 2436673
Registry Key VerificationNote 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, /helpDisplays help on supported switches.
/quietSuppresses the display of status or error messages.
/norestartWhen 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 the Start Search box.
    2. When the file appears under Programs, right-click the file name and click Properties.
    3. On the General tab, compare the file size with the file information tables provided in the bulletin KB article.

      Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
    4. You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.

      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.
    5. Finally, you can also click 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 7 (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 PacksThe 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 7:
Windows6.1-KB2436673-x86.msu /quiet
For all supported x64-based editions of Windows 7:
Windows6.1-KB2436673-x64.msu /quiet
Installing without restartingFor all supported 32-bit editions of Windows 7:
Windows6.1-KB2436673-x86.msu /quiet /norestart
For all supported x64-based editions of Windows 7:
Windows6.1-KB2436673-x64.msu /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 InformationTo uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates.
File InformationSee Microsoft Knowledge Base Article 2436673
Registry Key VerificationNote 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, /helpDisplays help on supported switches.
/quietSuppresses the display of status or error messages.
/norestartWhen combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.
/warnrestart:<seconds>When combined with /quiet, the installer will warn the user before initiating restart.
/promptrestartWhen combined with /quiet, the installer will prompt before initiating restart.
/forcerestartWhen combined with /quiet, the installer will forcefully close applications and initiate restart.
/log:<file name>Enables logging to specified file.
/extract:<destination>Extracts the package contents to the destination folder.
/uninstall /kb:<KB Number>Uninstalls the security update.

Note For more information about the wusa.exe installer, see "Windows Update Stand-alone Installer" in the TechNet article, Miscellaneous Changes in Windows 7.

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 the Search box.
    2. When the file appears under Programs, right-click the file name and click Properties.
    3. On the General tab, compare the file size with the file information tables provided in the bulletin KB article.

      Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
    4. You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.

      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.
    5. Finally, you can also click 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 R2 (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 PacksThe update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionFor all supported x64-based editions of Windows Server 2008 R2:
Windows6.1-KB2436673-x64.msu /quiet
For all supported Itanium-based editions of Windows Server 2008 R2:
Windows6.1-KB2436673-ia64.msu /quiet
Installing without restartingFor all supported x64-based editions of Windows Server 2008 R2:
Windows6.1-KB2436673-x64.msu /quiet /norestart
For all supported Itanium-based editions of Windows Server 2008 R2:
Windows6.1-KB2436673-ia64.msu /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 InformationTo uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates.
File InformationSee Microsoft Knowledge Base Article 2436673
Registry Key VerificationNote 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, /helpDisplays help on supported switches.
/quietSuppresses the display of status or error messages.
/norestartWhen combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.
/warnrestart:<seconds>When combined with /quiet, the installer will warn the user before initiating restart.
/promptrestartWhen combined with /quiet, the installer will prompt before initiating restart.
/forcerestartWhen combined with /quiet, the installer will forcefully close applications and initiate restart.
/log:<file name>Enables logging to specified file.
/extract:<destination>Extracts the package contents to the destination folder.
/uninstall /kb:<KB Number>Uninstalls the security update.

Note For more information about the wusa.exe installer, see "Windows Update Stand-alone Installer" in the TechNet article, Miscellaneous Changes in Windows 7.

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 the Start Search box.
    2. When the file appears under Programs, right-click the file name and click Properties.
    3. On the General tab, compare the file size with the file information tables provided in the bulletin KB article.

      Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
    4. You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.

      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.
    5. Finally, you can also click 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:

  • Tarjei Mandt of Norman for reporting the Windows Kernel Double Free Vulnerability (CVE-2010-3941)
  • Tarjei Mandt of Norman for reporting the Windows Kernel WriteAV Vulnerability (CVE-2010-3942)
  • Tarjei Mandt of Norman for reporting the Windows Kernel Cursor Linking Vulnerability (CVE-2010-3943)
  • Tarjei Mandt of Norman for reporting the Windows Kernel Memory Corruption Vulnerability (CVE-2010-3944)
  • Stéfan Le Berre of Sysdream for reporting the Windows Kernel Memory Corruption Vulnerability (CVE-2010-3944)

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 (December 14, 2010): Bulletin published.

Built at 2014-04-16T02:39:51Z-07:00

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