Security Bulletin

Microsoft Security Bulletin MS10-021 - Important

Vulnerabilities in Windows Kernel Could Allow Elevation of Privilege (979683)

Published: April 13, 2010 | Updated: July 13, 2010

Version: 1.1

General Information

Executive Summary

This security update resolves several privately reported vulnerabilities in Microsoft Windows. The most severe of these 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 editions of Microsoft Windows 2000, Windows XP, Windows Server 2003, and the original release version of Windows Vista. This security update is rated Moderate for all supported versions of Windows Vista Service Pack 1 and Windows Vista Service Pack 2, Windows Server 2008, Windows 7, and Windows Server 2008 R2. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerabilities by correcting validations, the creation of symbolic links, the resolution of virtual registry key paths, and exceptions handling. 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. Microsoft Knowledge Base Article 979683 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues.

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 System Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by this Update
Microsoft Windows 2000 Service Pack 4 Elevation of Privilege Important MS10-015
Windows XP Service Pack 2 and Windows XP Service Pack 3 Elevation of Privilege Important MS10-015
Windows XP Professional x64 Edition Service Pack 2 Elevation of Privilege Important MS10-015
Windows Server 2003 Service Pack 2 Elevation of Privilege Important MS10-015
Windows Server 2003 x64 Edition Service Pack 2 Elevation of Privilege Important MS10-015
Windows Server 2003 with SP2 for Itanium-based Systems Elevation of Privilege Important MS10-015
Windows Vista Elevation of Privilege Important MS10-015
Windows Vista Service Pack 1 and Windows Vista Service Pack 2 Denial of Service Moderate MS10-015
Windows Vista x64 Edition Elevation of Privilege Important MS10-015
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2 Denial of Service Moderate MS10-015
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2* Denial of Service Moderate MS10-015
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2* Denial of Service Moderate MS10-015
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 Denial of Service Moderate MS10-015
Windows 7 for 32-bit Systems Denial of Service Moderate None
Windows 7 for x64-based Systems Denial of Service Moderate None
Windows Server 2008 R2 for x64-based Systems* Denial of Service Moderate None
Windows Server 2008 R2 for Itanium-based Systems Denial of Service Moderate None

*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 MSDN articles, Server Core and Server Core for Windows Server 2008 R2. 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.

Why was this security bulletin revised on July 13, 2010?
Microsoft revised this security bulletin to announce a detection change. The corrected detection no longer lists the MS10-015 update as replaced by the MS10-021 update for Windows 7 for 32-bit Systems. This is a detection change only. There were no changes to the security update files in this bulletin. Customers who have already installed the update successfully do not need to reinstall the update.

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.

Does this update contain the same package installation logic that was included in the security update for MS10-015?
Yes. This security update includes package detection logic that prevents the installation of the security update if certain abnormal conditions exist on 32-bit systems. These abnormal conditions on a system could be the result of an infection with a computer virus that modifies some operating system files, which renders the infected computer incompatible with the kernel update. For more information about this issue, see the Microsoft Security page, Get help with Microsoft Security Bulletin MS10-015 incompatibility message.

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

Severity Ratings and Vulnerability Identifiers

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

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software Windows Kernel Null Pointer Vulnerability - CVE-2010-0234 Windows Kernel Symbolic Link Value Vulnerability - CVE-2010-0235 Windows Kernel Memory Allocation Vulnerability - CVE-2010-0236 Windows Kernel Symbolic Link Creation Vulnerability - CVE-2010-0237 Windows Kernel Registry Key Vulnerability - CVE-2010-0238 Windows Virtual Path Parsing Vulnerability - CVE-2010-0481 Windows Kernel Malformed Image Vulnerability - CVE-2010-0482 Windows Kernel Exception Handler Vulnerability - CVE-2010-0810 Aggregate Severity Rating
Microsoft Windows 2000 Service Pack 4 Moderate
Denial of Service
Moderate
Denial of Service
Important
Elevation of Privilege
Important
Elevation of Privilege
Moderate
Denial of Service
Not applicable Not applicable Not applicable Important
Windows XP Service Pack 2 and Windows XP Service Pack 3 Moderate
Denial of Service
Moderate
Denial of Service
Important
Elevation of Privilege
Important
Elevation of Privilege
Moderate
Denial of Service
Not applicable Not applicable Not applicable Important
Windows XP Professional x64 Edition Service Pack 2 Moderate
Denial of Service
Moderate
Denial of Service
Important
Elevation of Privilege
Not applicable Moderate
Denial of Service
Not applicable Not applicable Not applicable Important
Windows Server 2003 Service Pack 2 Moderate
Denial of Service
Moderate
Denial of Service
Important
Elevation of Privilege
Not applicable Moderate
Denial of Service
Not applicable Not applicable Not applicable Important
Windows Server 2003 x64 Edition Service Pack 2 Moderate
Denial of Service
Moderate
Denial of Service
Important
Elevation of Privilege
Not applicable Moderate
Denial of Service
Not applicable Not applicable Not applicable Important
Windows Server 2003 with SP2 for Itanium-based Systems Moderate
Denial of Service
Moderate
Denial of Service
Important
Elevation of Privilege
Not applicable Moderate
Denial of Service
Not applicable Not applicable Not applicable Important
Windows Vista Moderate
Denial of Service
Moderate
Denial of Service
Important
Elevation of Privilege
Not applicable Moderate
Denial of Service
Moderate
Denial of Service
Not applicable Moderate
Denial of Service
Important
Windows Vista Service Pack 1 and Windows Vista Service Pack 2 Moderate
Denial of Service
Not applicable Not applicable Not applicable Not applicable Moderate
Denial of Service
Not applicable Moderate
Denial of Service
Moderate
Windows Vista x64 Edition Moderate
Denial of Service
Moderate
Denial of Service
Important
Elevation of Privilege
Not applicable Moderate
Denial of Service
Moderate
Denial of Service
Not applicable Moderate
Denial of Service
Important
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2 Moderate
Denial of Service
Not applicable Not applicable Not applicable Not applicable Moderate
Denial of Service
Not applicable Moderate
Denial of Service
Moderate
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2* Moderate
Denial of Service
Not applicable Not applicable Not applicable Not applicable Moderate
Denial of Service
Not applicable Moderate
Denial of Service
Moderate
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2* Moderate
Denial of Service
Not applicable Not applicable Not applicable Not applicable Moderate
Denial of Service
Not applicable Moderate
Denial of Service
Moderate
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 Moderate
Denial of Service
Not applicable Not applicable Not applicable Not applicable Moderate
Denial of Service
Not applicable Moderate
Denial of Service
Moderate
Windows 7 for 32-bit Systems Not applicable Not applicable Not applicable Not applicable Not applicable Moderate
Denial of Service
Moderate
Denial of Service
Not applicable Moderate
Windows 7 for x64-based Systems Not applicable Not applicable Not applicable Not applicable Not applicable Moderate
Denial of Service
Moderate
Denial of Service
Not applicable Moderate
Windows Server 2008 R2 for x64-based Systems* Not applicable Not applicable Not applicable Not applicable Not applicable Moderate
Denial of Service
Moderate
Denial of Service
Not applicable Moderate
Windows Server 2008 R2 for Itanium-based Systems Not applicable Not applicable Not applicable Not applicable Not applicable Moderate
Denial of Service
Moderate
Denial of Service
Not applicable Moderate
**\*Server Core installation affected.** This update applies, with the same severity rating, to supported editions of Windows Server 2008 and Windows Server 2008 R2, whether or not installed using the Server Core installation option. For more information on this installation option, see the MSDN articles, [Server Core](http://msdn.microsoft.com/en-us/library/ms723891(vs.85).aspx) and [Server Core for Windows Server 2008 R2](http://msdn.microsoft.com/en-us/library/ee391631(vs.85).aspx). 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](http://www.microsoft.com/windowsserver2008/en/us/compare-core-installation.aspx). Windows Kernel Null Pointer Vulnerability - CVE-2010-0234 --------------------------------------------------------- A denial of service vulnerability exists in the Windows kernel due to the insufficient validation of registry keys passed to a Windows kernel system call. An attacker could exploit the vulnerability by running a specially crafted application, causing the system to become unresponsive and automatically restart. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2010-0234](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-0234). #### Mitigating Factors for Windows Kernel Null Pointer Vulnerability - CVE-2010-0234 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 Windows Kernel Null Pointer Vulnerability - CVE-2010-0234 Microsoft has not identified any workarounds for this vulnerability. #### FAQ for Windows Kernel Null Pointer Vulnerability - CVE-2010-0234 **What is the scope of the vulnerability?** This is a denial of service vulnerability. An attacker who exploited this vulnerability could cause the affected system to stop responding and automatically restart. Note that the denial of service vulnerability would not allow an attacker to run code or to elevate the attacker's user rights, but it could cause the affected system to stop accepting requests. **What causes the vulnerability?** The Windows kernel does not properly validate an argument passed to a system call. **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 cause the affected system to stop responding. **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 cause the system to stop responding and automatically restart. **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 method used for validating the argument passed to the system call. **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. Windows Kernel Symbolic Link Value Vulnerability - CVE-2010-0235 ---------------------------------------------------------------- A denial of service vulnerability exists in the Windows kernel due to the manner in which the kernel processes the values of symbolic links. An attacker could exploit the vulnerability by running a specially crafted application causing the system to become unresponsive and automatically restart. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2010-0235](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-0235). #### Mitigating Factors for Windows Kernel Symbolic Link Value Vulnerability - CVE-2010-0235 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 Windows Kernel Symbolic Link Value Vulnerability - CVE-2010-0235 Microsoft has not identified any workarounds for this vulnerability. #### FAQ for Windows Kernel Symbolic Link Value Vulnerability - CVE-2010-0235 **What is the scope of the vulnerability?** This is a denial of service vulnerability. An attacker who exploited this vulnerability could cause the affected system to stop responding and automatically restart. Note that the denial of service vulnerability would not allow an attacker to run code or to elevate the attacker's user rights, but it could cause the affected system to stop accepting requests. **What causes the vulnerability?** The Windows kernel does not properly handle certain specially crafted symbolic links. **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 cause the affected system to stop responding. **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 cause the system to stop responding and restart. **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 ensuring that the Windows kernel properly validates the symbolic link values before the symbolic link can be created. **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. Windows Kernel Memory Allocation Vulnerability - CVE-2010-0236 -------------------------------------------------------------- An elevation of privilege vulnerability exists in the Windows kernel due to the manner in which memory is allocated when extracting a symbolic link from a registry key. 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-0236](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-0236). #### Mitigating Factors for Windows Kernel Memory Allocation Vulnerability - CVE-2010-0236 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 Windows Kernel Memory Allocation Vulnerability - CVE-2010-0236 Microsoft has not identified any workarounds for this vulnerability. #### FAQ for Windows Kernel Memory Allocation Vulnerability - CVE-2010-0236 **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 Windows kernel does not correctly allocate memory when extracting the destination key from a symbolic-link type registry key. **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 the 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 ensuring that the Windows kernel properly validates the symbolic link value before the symbolic link can be created. **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. Windows Kernel Symbolic Link Creation Vulnerability - CVE-2010-0237 ------------------------------------------------------------------- An elevation of privilege vulnerability exists when the Windows kernel does not properly restrict symbolic link creation between untrusted and trusted registry hives. 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-0237](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-0237). #### Mitigating Factors for Windows Kernel Symbolic Link Creation Vulnerability - CVE-2010-0237 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 allows an unprivileged user on a computer to run arbitrary code in the context of a user who later logs in to the same computer. The attacker cannot choose which user to impersonate. - 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 Windows Kernel Symbolic Link Creation Vulnerability - CVE-2010-0237 Microsoft has not identified any workarounds for this vulnerability. #### FAQ for Windows Kernel Symbolic Link Creation Vulnerability - CVE-2010-0237 **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 Windows kernel does not properly restrict symbolic link creation between untrusted and trusted registry hives. **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 the 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 correctly blocking the traversal of symbolic links from untrusted to trusted hives. **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. Windows Kernel Registry Key Vulnerability - CVE-2010-0238 --------------------------------------------------------- A denial of service vulnerability exists in the way that the Windows kernel validates registry keys. An attacker could exploit the vulnerability by running a specially crafted application causing the system to become unresponsive and automatically restart. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2010-0238](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-0238). #### Mitigating Factors for Windows Kernel Registry Key Vulnerability - CVE-2010-0238 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 Windows Kernel Registry Key Vulnerability - CVE-2010-0238 Microsoft has not identified any workarounds for this vulnerability. #### FAQ for Windows Kernel Registry Key Vulnerability - CVE-2010-0238 **What is the scope of the vulnerability?** This is a denial of service vulnerability. An attacker who exploited this vulnerability could cause the affected system to stop responding and automatically restart. Note that the denial of service vulnerability would not allow an attacker to run code or to elevate the attacker's user rights, but it could cause the affected system to stop accepting requests. **What causes the vulnerability?** The Windows kernel does not properly validate registry keys. **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 cause the affected system to stop responding. **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 cause the system to stop responding. **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 manner in which the Windows kernel validates registry keys. **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. Windows Virtual Path Parsing Vulnerability - CVE-2010-0481 ---------------------------------------------------------- A denial of service vulnerability exists in the Windows kernel due to the way that the kernel resolves the real path for a registry key from its virtual path. An attacker could exploit the vulnerability by running a specially crafted application, causing the system to become unresponsive and automatically restart. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2010-0481](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-0481). #### Mitigating Factors for Windows Virtual Path Parsing Vulnerability - CVE-2010-0481 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 Windows Virtual Path Parsing Vulnerability - CVE-2010-0481 Microsoft has not identified any workarounds for this vulnerability. #### FAQ for Windows Virtual Path Parsing Vulnerability - CVE-2010-0481 **What is the scope of the vulnerability?** This is a denial of service vulnerability. An attacker who exploited this vulnerability could cause the affected system to stop responding and automatically restart. Note that the denial of service vulnerability would not allow an attacker to run code or to elevate the attacker's user rights, but it could cause the affected system to stop accepting requests. **What causes the vulnerability?** The Windows kernel does not sufficiently validate a virtual path to ensure that it is valid. **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 cause the affected system to stop responding. **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 cause the system to stop responding and restart. **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 manner in which the Windows kernel resolves virtual registry key paths. **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. Windows Kernel Malformed Image Vulnerability - CVE-2010-0482 ------------------------------------------------------------ A denial of service vulnerability exists in the Windows kernel due to the improper validation of specially crafted image files. An attacker could exploit the vulnerability by running a specially crafted application causing the system to become unresponsive and automatically restart. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2010-0482](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-0482). #### Mitigating Factors for Windows Kernel Malformed Image Vulnerability - CVE-2010-0482 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 Windows Kernel Malformed Image Vulnerability - CVE-2010-0482 Microsoft has not identified any workarounds for this vulnerability. #### FAQ for Windows Kernel Malformed Image Vulnerability - CVE-2010-0482 **What is the scope of the vulnerability?** This is a denial of service vulnerability. An attacker who exploited this vulnerability could cause the affected system to stop responding and automatically restart. Note that the denial of service vulnerability would not allow an attacker to run code or to elevate the attacker's user rights, but it could cause the affected system to stop accepting requests. **What causes the vulnerability?** The Windows kernel does not properly validate the relocation section of specially crafted image files. **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 cause the affected system to stop responding. **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 cause the system to stop responding and restart. **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 manner in which the Windows kernel validates the relocation section of specially crafted image files. **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. Windows Kernel Exception Handler Vulnerability - CVE-2010-0810 -------------------------------------------------------------- A denial of service vulnerability exists in the Windows kernel due to the way that the kernel handles certain exceptions. An attacker could exploit the vulnerability by running a specially crafted application, causing the system to become unresponsive and automatically restart. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2010-0810](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-0810). #### Mitigating Factors for Windows Kernel Exception Handler Vulnerability - CVE-2010-0810 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 Windows Kernel Exception Handler Vulnerability - CVE-2010-0810 Microsoft has not identified any workarounds for this vulnerability. #### FAQ for Windows Kernel Exception Handler Vulnerability - CVE-2010-0810 **What is the scope of the vulnerability?** This is a denial of service vulnerability. An attacker who exploited this vulnerability could cause the affected system to stop responding and automatically restart. Note that the denial of service vulnerability would not allow an attacker to run code or to elevate the attacker's user rights, but it could cause the affected system to stop accepting requests. **What causes the vulnerability?** The Windows kernel does not properly handle certain exceptions. **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 cause the affected system to stop responding. **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 cause the system to stop responding and restart. **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 ensuring that the Windows Kernel handles the exception properly. **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 Detection and Deployment Tools and Guidance ------------------------------------------- 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](http://go.microsoft.com/fwlink/?linkid=69903). The [Microsoft TechNet Security Web site](http://go.microsoft.com/fwlink/?linkid=21132) provides additional information about security in Microsoft products. Security updates are available from [Microsoft Update](http://go.microsoft.com/fwlink/?linkid=40747) and [Windows Update](http://go.microsoft.com/fwlink/?linkid=21130). Security updates are also available from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?linkid=21129). 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](http://go.microsoft.com/fwlink/?linkid=96155). 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](http://go.microsoft.com/fwlink/?linkid=97900). **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](http://go.microsoft.com/fwlink/?linkid=40747). For more information, see [About Microsoft Office Update: Frequently Asked Questions](http://office.microsoft.com/en-us/downloads/fx010402221033.aspx). **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](http://support.microsoft.com/kb/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](http://www.microsoft.com/technet/security/tools/mbsahome.mspx). The following table provides the MBSA detection summary for this security update. | Software | MBSA 2.1.1 | |-------------------------------------------------------------------------------------------------------------------|------------| | Microsoft Windows 2000 Service Pack 4 | Yes | | Windows XP Service Pack 2 and Windows XP Service Pack 3 | Yes | | Windows XP Professional x64 Edition Service Pack 2 | Yes | | Windows Server 2003 Service Pack 2 | Yes | | Windows Server 2003 x64 Edition Service Pack 2 | Yes | | Windows Server 2003 with SP2 for Itanium-based Systems | Yes | | Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 | Yes | | Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 | Yes | | Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 | Yes | | Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 | Yes | | Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 | Yes | | Windows 7 for 32-bit Systems | Yes | | Windows 7 for x64-based Systems | Yes | | Windows Server 2008 R2 for x64-based Systems | Yes | | Windows Server 2008 R2 for Itanium-based Systems | Yes | The latest version of MBSA has been released: [Microsoft Baseline Security Analyzer 2.1.1](http://www.microsoft.com/downloads/details.aspx?familyid=b1e76bbe-71df-41e8-8b52-c871d012ba78&displaylang=en). For more information, see [Microsoft Baseline Security Analyzer 2.1](http://technet.microsoft.com/en-us/security/cc184923.aspx). **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](http://go.microsoft.com/fwlink/?linkid=50120). **Systems Management Server** The following table provides the SMS detection and deployment summary for this security update. | Software | SMS 2.0 | SMS 2003 with SUIT | SMS 2003 with ITMU | Configuration Manager 2007 | |-------------------------------------------------------------------------------------------------------------------|---------|--------------------|--------------------|----------------------------| | Microsoft Windows 2000 Service Pack 4 | Yes | Yes | Yes | Yes | | Windows XP Service Pack 2 and Windows XP Service Pack 3 | Yes | Yes | Yes | Yes | | Windows XP Professional x64 Edition Service Pack 2 | No | No | Yes | Yes | | Windows Server 2003 Service Pack 2 | Yes | Yes | Yes | Yes | | Windows Server 2003 x64 Edition Service Pack 2 | No | No | Yes | Yes | | Windows Server 2003 with SP2 for Itanium-based Systems | No | No | Yes | Yes | | Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 | No | No | Yes | Yes | | Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 | No | No | Yes | Yes | | Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 | No | No | Yes | Yes | | Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 | No | No | Yes | Yes | | Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 | No | No | Yes | Yes | | Windows 7 for 32-bit Systems | No | No | Yes | Yes | | Windows 7 for x64-based Systems | No | No | Yes | Yes | | Windows Server 2008 R2 for x64-based Systems | No | No | Yes | Yes | | Windows Server 2008 R2 for Itanium-based Systems | No | No | Yes | Yes | 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](http://technet.microsoft.com/en-us/sms/bb676799.aspx). 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](http://update.microsoft.com/microsoftupdate) and that are supported by [Windows Server Update Services](http://go.microsoft.com/fwlink/?linkid=50120). For more information about the SMS 2003 ITMU, see [SMS 2003 Inventory Tool for Microsoft Updates](http://technet.microsoft.com/en-us/sms/bb676783.aspx). For more information about SMS scanning tools, see [SMS 2003 Software Update Scanning Tools](http://technet.microsoft.com/en-us/sms/bb676786.aspx). See also [Downloads for Systems Management Server 2003](http://technet.microsoft.com/en-us/sms/bb676766.aspx). 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](http://technet.microsoft.com/en-us/library/bb735860.aspx). For more information about SMS, visit the [SMS Web site](http://go.microsoft.com/fwlink/?linkid=21158). For more detailed information, see [Microsoft Knowledge Base Article 910723](http://support.microsoft.com/kb/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](http://technet2.microsoft.com/windowsvista/en/library/4279e239-37a4-44aa-aec5-4e70fe39f9de1033.mspx?mfr=true) components included with [Application Compatibility Toolkit](http://www.microsoft.com/downloads/details.aspx?familyid=24da89e9-b581-47b0-b45e-492dd6da2971&displaylang=en). 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. Security Update Deployment -------------------------- **Affected Software** For information about the specific security update for your affected software, click the appropriate link: #### Windows 2000 (all editions) **Reference Table** The following table contains the security update information for this software. You can find additional information in the subsection, **Deployment Information**, in this section. | | | |---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| | **Inclusion in Future Service Packs** | The update for this issue may be included in a future update rollup | | **Deployment** | | | Installing without user intervention | Windows2000-KB979683-x86-enu /quiet | | Installing without restarting | Windows2000-KB979683-x86-enu /norestart | | Update log file | KB979683.log | | Further information | See the subsection, **Detection and Deployment Tools and Guidance** | | **Restart Requirement** | | | Restart required? | Yes, you must restart your system after you apply this security update. | | HotPatching | Not applicable | | **Removal Information** | Use **Add or Remove Programs** tool in Control Panel or the Spuninst.exe utility located in the %Windir%\\$NTUninstallKB979683$\\Spuninst folder | | **File Information** | See [Microsoft Knowledge Base Article 979683](http://support.microsoft.com/kb/979683) | | **Registry Key Verification** | HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Updates\\Windows 2000\\SP5\\KB979683\\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](http://support.microsoft.com/kb/824994). For more information about the installer, visit the [Microsoft TechNet Web site](http://go.microsoft.com/fwlink/?linkid=38951). For more information about the terminology that appears in this bulletin, such as *hotfix*, see [Microsoft Knowledge Base Article 824684](http://support.microsoft.com/kb/824684). This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch Description
**/help** Displays the command-line options.
Setup Modes
**/passive** Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
**/quiet** Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
**/norestart** Does not restart when installation has completed.
**/forcerestart** Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
**/warnrestart\[:x\]** Presents a dialog box with a timer warning the user that the computer will restart in *x* seconds. (The default setting is 30 seconds.) Intended for use with the **/quiet** switch or the **/passive** switch.
**/promptrestart** Displays a dialog box prompting the local user to allow a restart.
Special Options
**/overwriteoem** Overwrites OEM files without prompting.
**/nobackup** Does not back up files needed for uninstall.
**/forceappsclose** Forces other programs to close when the computer shuts down.
**/log:path** Allows the redirection of installation log files.
**/extract\[:path\]** Extracts files without starting the Setup program.
**/ER** Enables extended error reporting.
**/verbose** Enables verbose logging. During installation, creates %Windir%\\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.
**Note** You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see [Microsoft Knowledge Base Article 262841](http://support.microsoft.com/kb/262841).

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
Switch Description
**/help** Displays the command-line options.
Setup Modes
**/passive** Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
**/quiet** Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
**/norestart** Does not restart when installation has completed.
**/forcerestart** Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
**/warnrestart\[:x\]** Presents a dialog box with a timer warning the user that the computer will restart in *x* seconds. (The default setting is 30 seconds.) Intended for use with the **/quiet** switch or the **/passive** switch.
**/promptrestart** Displays a dialog box prompting the local user to allow a restart.
Special Options
**/forceappsclose** Forces other programs to close when the computer shuts down.
**/log:path** Allows the redirection of installation log files.
**Verifying That the Update Has Been Applied**
  • Microsoft Baseline Security Analyzer
    To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification
    Because there are several 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 XP (all editions)

Reference Table

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

Inclusion in Future Service Packs The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention For Windows XP Service Pack 2 and Windows XP Service Pack 3:
WindowsXP-KB979683-x86-enu /quiet
For Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB979683-x64-enu /quiet
Installing without restarting For Windows XP Service Pack 2 and Windows XP Service Pack 3:
WindowsXP-KB979683-x86-enu /norestart
For Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB979683-x64-enu /norestart
Update log file KB979683.log
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required? Yes, you must restart your system after you apply this security update.
HotPatching Not applicable
Removal Information Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB979683$\Spuninst folder
File Information See Microsoft Knowledge Base Article 979683
Registry Key Verification For all supported 32-bit editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB979683\Filelist
For all supported x64-based editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB979683\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, visit the Microsoft TechNet Web site.

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

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch Description
**/help** Displays the command-line options.
Setup Modes
**/passive** Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
**/quiet** Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
**/norestart** Does not restart when installation has completed.
**/forcerestart** Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
**/warnrestart\[:x\]** Presents a dialog box with a timer warning the user that the computer will restart in *x* seconds. (The default setting is 30 seconds.) Intended for use with the **/quiet** switch or the **/passive** switch.
**/promptrestart** Displays a dialog box prompting the local user to allow a restart.
Special Options
**/overwriteoem** Overwrites OEM files without prompting.
**/nobackup** Does not back up files needed for uninstall.
**/forceappsclose** Forces other programs to close when the computer shuts down.
**/log:path** Allows the redirection of installation log files.
**/integrate:path** Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
**/extract\[:path\]** Extracts files without starting the Setup program.
**/ER** Enables extended error reporting.
**/verbose** Enables verbose logging. During installation, creates %Windir%\\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.
**Note** You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see [Microsoft Knowledge Base Article 262841](http://support.microsoft.com/kb/262841).

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
Switch Description
**/help** Displays the command-line options.
Setup Modes
**/passive** Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
**/quiet** Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
**/norestart** Does not restart when installation has completed
**/forcerestart** Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
**/warnrestart\[:x\]** Presents a dialog box with a timer warning the user that the computer will restart in *x* seconds. (The default setting is 30 seconds.) Intended for use with the **/quiet** switch or the **/passive** switch.
**/promptrestart** Displays a dialog box prompting the local user to allow a restart.
Special Options
**/forceappsclose** Forces other programs to close when the computer shuts down.
**/log:path** Allows the redirection of installation log files.
**Verifying That the Update Has Been Applied**
  • Microsoft Baseline Security Analyzer
    To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification
    Because there are several 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 Packs The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention For all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB979683-x86-enu /quiet
For all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB979683-x64-enu /quiet
For all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB979683-ia64-enu /quiet
Installing without restarting For all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB979683-x86-enu /norestart
For all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB979683-x64-enu /norestart
For all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB979683-ia64-enu /norestart
Update log file KB979683.log
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required? Yes, you must restart your system after you apply this security update.
HotPatching This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.
Removal Information Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB979683$\Spuninst folder
File Information See Microsoft Knowledge Base Article 979683
Registry Key Verification HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB979683\Filelist
#### Deployment Information **Installing the Update** When you install this security update, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix. 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](http://support.microsoft.com/kb/824994). For more information about the installer, visit the [Microsoft TechNet Web site](http://go.microsoft.com/fwlink/?linkid=38951). For more information about the terminology that appears in this bulletin, such as *hotfix*, see [Microsoft Knowledge Base Article 824684](http://support.microsoft.com/kb/824684). This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch Description
**/help** Displays the command-line options.
Setup Modes
**/passive** Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
**/quiet** Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
**/norestart** Does not restart when installation has completed.
**/forcerestart** Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
**/warnrestart\[:x\]** Presents a dialog box with a timer warning the user that the computer will restart in *x* seconds. (The default setting is 30 seconds.) Intended for use with the **/quiet** switch or the **/passive** switch.
**/promptrestart** Displays a dialog box prompting the local user to allow a restart.
Special Options
**/overwriteoem** Overwrites OEM files without prompting.
**/nobackup** Does not back up files needed for uninstall.
**/forceappsclose** Forces other programs to close when the computer shuts down.
**/log:path** Allows the redirection of installation log files.
**/integrate:path** Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
**/extract\[:path\]** Extracts files without starting the Setup program.
**/ER** Enables extended error reporting.
**/verbose** Enables verbose logging. During installation, creates %Windir%\\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.
**Note** You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see [Microsoft Knowledge Base Article 262841](http://support.microsoft.com/kb/262841).

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
Switch Description
**/help** Displays the command-line options.
Setup Modes
**/passive** Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
**/quiet** Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
**/norestart** Does not restart when installation has completed.
**/forcerestart** Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
**/warnrestart\[:x\]** Presents a dialog box with a timer warning the user that the computer will restart in *x* seconds. (The default setting is 30 seconds.) Intended for use with the **/quiet** switch or the **/passive** switch.
**/promptrestart** Displays a dialog box prompting the local user to allow a restart.
Special Options
**/forceappsclose** Forces other programs to close when the computer shuts down.
**/log:path** Allows the redirection of installation log files.
**Verifying that the Update Has Been Applied**
  • Microsoft Baseline Security Analyzer
    To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

  • File Version Verification
    Because there are several 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 Packs The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention For all supported 32-bit editions of Windows Vista:
Windows6.0-KB979683-x86 /quiet
For all supported x64-based editions of Windows Vista:
Windows6.0-KB979683-x64 /quiet
Installing without restarting For all supported 32-bit editions of Windows Vista:
Windows6.0-KB979683-x86 /quiet /norestart
For all supported x64-based editions of Windows Vista:
Windows6.0-KB979683-x64 /quiet /norestart
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required? Yes, you must restart your system after you apply this security update.
HotPatching Not applicable.
Removal Information 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 979683
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](http://support.microsoft.com/kb/824684). This security update supports the following setup switches. | Switch | Description | |-------------------|--------------------------------------------------------------------------------------------------------------------------------------------| | **/?, /h, /help** | Displays help on supported switches. | | **/quiet** | Suppresses the display of status or error messages. | | **/norestart** | When combined with **/quiet**, the system will not be restarted after installation even if a restart is required to complete installation. | **Note** For more information about the wusa.exe installer, see [Microsoft Knowledge Base Article 934307](http://support.microsoft.com/kb/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 intervention For all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB979683-x86 /quiet
For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB979683-x64 /quiet
For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB979683-ia64 /quiet
Installing without restarting For all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB979683-x86 /quiet /norestart
For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB979683-x64 /quiet /norestart
For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB979683-ia64 /quiet /norestart
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required? Yes, you must restart your system after you apply this security update.
HotPatching Not applicable.
Removal Information 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 979683
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](http://support.microsoft.com/kb/824684). This security update supports the following setup switches. | Switch | Description | |-------------------|--------------------------------------------------------------------------------------------------------------------------------------------| | **/?, /h, /help** | Displays help on supported switches. | | **/quiet** | Suppresses the display of status or error messages. | | **/norestart** | When combined with **/quiet**, the system will not be restarted after installation even if a restart is required to complete installation. | **Note** For more information about the wusa.exe installer, see [Microsoft Knowledge Base Article 934307](http://support.microsoft.com/kb/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 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 Packs The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention For all supported 32-bit editions of Windows 7:
Windows6.1-KB979683-x86 /quiet
For all supported x64-based editions of Windows 7:
Windows6.1-KB979683-x64 /quiet
Installing without restarting For all supported 32-bit editions of Windows 7:
Windows6.1-KB979683-x86 /quiet /norestart
For all supported x64-based editions of Windows 7:
Windows6.1-KB979683-x64 /quiet /norestart
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required? Yes, you must restart your system after you apply this security update.
HotPatching Not applicable.
Removal Information 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 979683
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](http://support.microsoft.com/kb/824684). This security update supports the following setup switches. | Switch | Description | |-------------------|--------------------------------------------------------------------------------------------------------------------------------------------| | **/?, /h, /help** | Displays help on supported switches. | | **/quiet** | Suppresses the display of status or error messages. | | **/norestart** | When combined with **/quiet**, the system will not be restarted after installation even if a restart is required to complete installation. | **Note** For more information about the wusa.exe installer, see [Microsoft Knowledge Base Article 934307](http://support.microsoft.com/kb/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 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 Packs The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention For all supported x64-based editions of Windows Server 2008 R2:
Windows6.1-KB979683-x64 /quiet
For all supported Itanium-based editions of Windows Server 2008 R2:
Windows6.1-KB979683-ia64 /quiet
Installing without restarting For all supported x64-based editions of Windows Server 2008 R2:
Windows6.1-KB979683-x64 /quiet /norestart
For all supported Itanium-based editions of Windows Server 2008 R2:
Windows6.1-KB979683-ia64 /quiet /norestart
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required? Yes, you must restart your system after you apply this security update.
HotPatching Not applicable.
Removal Information 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 979683
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](http://support.microsoft.com/kb/824684). This security update supports the following setup switches. | Switch | Description | |-------------------|--------------------------------------------------------------------------------------------------------------------------------------------| | **/?, /h, /help** | Displays help on supported switches. | | **/quiet** | Suppresses the display of status or error messages. | | **/norestart** | When combined with **/quiet**, the system will not be restarted after installation even if a restart is required to complete installation. | **Note** For more information about the wusa.exe installer, see [Microsoft Knowledge Base Article 934307](http://support.microsoft.com/kb/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](http://go.microsoft.com/fwlink/?linkid=21127) the following for working with us to help protect customers: - [Mateusz "j00ru" Jurczyk](http://j00ru.vexillium.org/) and Gynvael Coldwind of [Hispasec](http://www.hispasec.com/) [Virustotal](http://www.virustotal.com/) for reporting the Windows Kernel Null Pointer Vulnerability(CVE-2010-0234) - [Mateusz "j00ru" Jurczyk](http://j00ru.vexillium.org/) and Gynvael Coldwind of [Hispasec](http://www.hispasec.com/) [Virustotal](http://www.virustotal.com/) for reporting the Windows Kernel Symbolic Link Value Vulnerability (CVE-2010-0235) - [Mateusz "j00ru" Jurczyk](http://j00ru.vexillium.org/) and Gynvael Coldwind of [Hispasec](http://www.hispasec.com/) [Virustotal](http://www.virustotal.com/) for reporting the Windows Kernel Memory Allocation Vulnerability (CVE-2010-0236) - Gynvael Coldwind and [Mateusz "j00ru" Jurczyk](http://j00ru.vexillium.org/) of [Hispasec](http://www.hispasec.com/)[Virustotal](http://www.virustotal.com/) for reporting the Windows Kernel Symbolic Link Creation Vulnerability (CVE-2010-0237) - [Mateusz "j00ru" Jurczyk](http://j00ru.vexillium.org/) and Gynvael Coldwind of [Hispasec](http://www.hispasec.com/) [Virustotal](http://www.virustotal.com/) for reporting the Windows Kernel Registry Key Vulnerability (CVE-2010-0238) - Tavis Ormandy of [Google, Inc.](http://www.google.com/) for reporting the Windows Virtual Path Parsing Vulnerability (CVE-2010-0481) - Martin Tofall of [Obsidium Software](http://www.obsidium.de/) for reporting the Windows Kernel Malformed Image Vulnerability (CVE-2010-0482) - Tavis Ormandy of [Google, Inc.](http://www.google.com/) for reporting the Windows Kernel Exception Handler Vulnerability (CVE-2010-0810) #### 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](http://www.microsoft.com/security/msrc/mapp/partners.mspx). #### Support - Customers in the U.S. and Canada can receive technical support from [Security Support](http://go.microsoft.com/fwlink/?linkid=21131) 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](http://support.microsoft.com/). - 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](http://go.microsoft.com/fwlink/?linkid=21155). #### 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 (April 13, 2010): Bulletin published. - V1.1 (July 13, 2010): Added an entry in the Update FAQ to announce a detection change to the update for Windows 7 for 32-bit Systems. This is a detection change only. There were no changes to the security update files in this bulletin. Customers who have already installed the update successfully do not need to reinstall. *Built at 2014-04-18T13:49:36Z-07:00*