Security Bulletin
Microsoft Security Bulletin MS12-001 - Important
Vulnerability in Windows Kernel Could Allow Security Feature Bypass (2644615)
Published: January 10, 2012 | Updated: February 22, 2012
Version: 1.1
General Information
Executive Summary
This security update resolves a privately reported vulnerability in Microsoft Windows. The vulnerability could allow an attacker to bypass the SafeSEH security feature in a software application. An attacker could then use other vulnerabilities to leverage the structured exception handler to run arbitrary code. Only software applications that were compiled using Microsoft Visual C++ .NET 2003 can be used to exploit this vulnerability.
This security update is rated Important for supported x64-based editions of Windows XP and all supported editions of Windows Server 2003, Windows Vista, 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 vulnerability by modifying the way that the Windows kernel loads structured exception handling tables. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. 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 2644615 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
*Server Core installation affected. This update applies, with the same severity rating, to supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, whether or not installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, Managing a Server Core Installation and Servicing a Server Core Installation. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.
Non-Affected Software
Operating System |
---|
Windows XP Service Pack 3 |
Frequently Asked Questions (FAQ) Related to This Security 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.
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 life cycle, visit the Microsoft Support Lifecycle website.
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 life cycle for your software release, see Select a Product for Lifecycle Information. For more information about service packs for these software releases, see Service Pack Lifecycle Support Policy.
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 website, 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 January bulletin summary. For more information, see Microsoft Exploitability Index.
Affected Software | Windows Kernel SafeSEH Bypass Vulnerability - CVE-2012-0001 | Aggregate Severity Rating |
---|---|---|
Windows XP Professional x64 Edition Service Pack 2 | Important Security Feature Bypass |
Important |
Windows Server 2003 Service Pack 2 | Important Security Feature Bypass |
Important |
Windows Server 2003 x64 Edition Service Pack 2 | Important Security Feature Bypass |
Important |
Windows Server 2003 with SP2 for Itanium-based Systems | Important Security Feature Bypass |
Important |
Windows Vista Service Pack 2 | Important Security Feature Bypass |
Important |
Windows Vista x64 Edition Service Pack 2 | Important Security Feature Bypass |
Important |
Windows Server 2008 for 32-bit Systems Service Pack 2* | Important Security Feature Bypass |
Important |
Windows Server 2008 for x64-based Systems Service Pack 2* | Important Security Feature Bypass |
Important |
Windows Server 2008 for Itanium-based Systems Service Pack 2 | Important Security Feature Bypass |
Important |
Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 | Important Security Feature Bypass |
Important |
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 | Important Security Feature Bypass |
Important |
Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1* | Important Security Feature Bypass |
Important |
Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | Important Security Feature Bypass |
Important |
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 Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB2644615-x64-enu.exe /quiet |
Installing without restarting | For Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB2644615-x64-enu.exe /norestart |
Update log file | KB2644615.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 item in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB2644615$\Spuninst folder |
File Information | See Microsoft Knowledge Base Article 2644615 |
Registry Key Verification | For all supported x64-based editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB2644615\Filelist |
Note The update for supported versions of Windows XP Professional x64 Edition also applies to supported versions of Windows Server 2003 x64 Edition.
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the installer, see Microsoft Knowledge Base Article 832475.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
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. |
Removing the Update
This security update supports the following setup switches.
Switch | Description |
---|---|
**/help** | Displays the command-line options. |
Setup Modes | |
**/passive** | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
**/quiet** | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
Restart Options | |
**/norestart** | Does not restart when installation has completed |
**/forcerestart** | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
**/warnrestart\[:x\]** | Presents a dialog box with a timer warning the user that the computer will restart in *x* seconds. (The default setting is 30 seconds.) Intended for use with the **/quiet** switch or the **/passive** switch. |
**/promptrestart** | 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. |
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.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the 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. - 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-KB2644615-x86-enu.exe /quiet | |
For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB2644615-x64-enu.exe /quiet | ||
For all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB2644615-ia64-enu.exe /quiet | ||
Installing without restarting | For all supported 32-bit editions of Windows Server 2003: WindowsServer2003-KB2644615-x86-enu.exe /norestart | |
For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB2644615-x64-enu.exe /norestart | ||
For all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB2644615-ia64-enu.exe /norestart | ||
Update log file | KB2644615.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](http://support.microsoft.com/kb/897341). | |
**Removal Information** | Use **Add or Remove Programs** item in Control Panel or the Spuninst.exe utility located in the %Windir%\\$NTUninstallKB2644615$\\Spuninst folder | |
**File Information** | See [Microsoft Knowledge Base Article 2644615](http://support.microsoft.com/kb/2644615) | |
**Registry Key Verification** | HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Updates\\Windows Server 2003\\SP3\\KB2644615\\Filelist |
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the installer, see Microsoft Knowledge Base Article 832475.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
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. |
Removing the Update
This security update supports the following setup switches.
Switch | Description |
---|---|
**/help** | Displays the command-line options. |
**Setup Modes** | |
**/passive** | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
**/quiet** | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
Restart Options | |
**/norestart** | Does not restart when installation has completed. |
**/forcerestart** | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
**/warnrestart\[:x\]** | Presents a dialog box with a timer warning the user that the computer will restart in *x* seconds. (The default setting is 30 seconds.) Intended for use with the **/quiet** switch or the **/passive** switch. |
**/promptrestart** | 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. |
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.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the 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. - 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-KB2644615-x86.msu /quiet |
For all supported x64-based editions of Windows Vista: Windows6.0-KB2644615-x64.msu /quiet |
|
Installing without restarting | For all supported 32-bit editions of Windows Vista: Windows6.0-KB2644615-x86.msu /quiet /norestart |
For all supported x64-based editions of Windows Vista: Windows6.0-KB2644615-x64.msu /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 2644615 |
Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
Supported Security Update Installation Switches
Switch | Description |
---|---|
/?, /h, /help | Displays help on supported switches. |
/quiet | Suppresses the display of status or error messages. |
/norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. - Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Windows Server 2008 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Inclusion in Future Service 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-KB2644615-x86.msu /quiet |
For all supported x64-based editions of Windows Server 2008: Windows6.0-KB2644615-x64.msu /quiet |
|
For all supported Itanium-based editions of Windows Server 2008: Windows6.0-KB2644615-ia64.msu /quiet |
|
Installing without restarting | For all supported 32-bit editions of Windows Server 2008: Windows6.0-KB2644615-x86.msu /quiet /norestart |
For all supported x64-based editions of Windows Server 2008: Windows6.0-KB2644615-x64.msu /quiet /norestart |
|
For all supported Itanium-based editions of Windows Server 2008: Windows6.0-KB2644615-ia64.msu /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 2644615 |
Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
Supported Security Update Installation Switches
Switch | Description |
---|---|
/?, /h, /help | Displays help on supported switches. |
/quiet | Suppresses the display of status or error messages. |
/norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. - Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Windows 7 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Inclusion in Future Service 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-KB2644615-x86.msu /quiet |
For all supported x64-based editions of Windows 7: Windows6.1-KB2644615-x64.msu /quiet |
|
Installing without restarting | For all supported 32-bit editions of Windows 7: Windows6.1-KB2644615-x86.msu /quiet /norestart |
For all supported x64-based editions of Windows 7: Windows6.1-KB2644615-x64.msu /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 | To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates. |
File Information | See Microsoft Knowledge Base Article 2644615 |
Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
Supported Security Update Installation 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. |
/warnrestart:<seconds> | When combined with /quiet, the installer will warn the user before initiating restart. |
/promptrestart | When combined with /quiet, the installer will prompt before initiating restart. |
/forcerestart | When combined with /quiet, the installer will forcefully close applications and initiate restart. |
/log:<file name> | Enables logging to specified file. |
/extract:<destination> | Extracts the package contents to the destination folder. |
/uninstall /kb:<KB Number> | Uninstalls the security update. |
Note For more information about the wusa.exe installer, see "Windows Update Stand-alone Installer" in the TechNet article, Miscellaneous Changes in Windows 7.
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start and then enter an update file name in the Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. - Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Windows Server 2008 R2 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Inclusion in Future Service 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-KB2644615-x64.msu /quiet |
For all supported Itanium-based editions of Windows Server 2008 R2: Windows6.1-KB2644615-ia64.msu /quiet |
|
Installing without restarting | For all supported x64-based editions of Windows Server 2008 R2: Windows6.1-KB2644615-x64.msu /quiet /norestart |
For all supported Itanium-based editions of Windows Server 2008 R2: Windows6.1-KB2644615-ia64.msu /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 | To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates. |
File Information | See Microsoft Knowledge Base Article 2644615 |
Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
Supported Security Update Installation 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. |
/warnrestart:<seconds> | When combined with /quiet, the installer will warn the user before initiating restart. |
/promptrestart | When combined with /quiet, the installer will prompt before initiating restart. |
/forcerestart | When combined with /quiet, the installer will forcefully close applications and initiate restart. |
/log:<file name> | Enables logging to specified file. |
/extract:<destination> | Extracts the package contents to the destination folder. |
/uninstall /kb:<KB Number> | Uninstalls the security update. |
Note For more information about the wusa.exe installer, see "Windows Update Stand-alone Installer" in the TechNet article, Miscellaneous Changes in Windows 7.
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. - Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Joshua J. Drake of Accuvant LABS for reporting the Windows Kernel SafeSEH Bypass Vulnerability (CVE-2012-0001)
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 websites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.
Support
- Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support.
- International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support website.
Disclaimer
The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Revisions
- V1.0 (January 10, 2012): Bulletin published.
- V1.1 (February 22, 2012): Added a link to Microsoft Knowledge Base Article 2644615 under Known Issues in the Executive Summary.
Built at 2014-04-18T13:49:36Z-07:00