Security Bulletin
Microsoft Security Bulletin MS12-024 - Critical
Vulnerability in Windows Could Allow Remote Code Execution (2653956)
Published: April 10, 2012 | Updated: July 31, 2012
Version: 1.1
General Information
Executive Summary
This security update resolves a privately reported vulnerability in Microsoft Windows. The vulnerability could allow remote code execution if a user or application runs or installs a specially crafted, signed portable executable (PE) file on an affected system.
This security update is rated Critical for all supported releases of Microsoft Windows. 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 Authenticode Signature Verification function performs Windows Authenticode signature verification when verifying portable executable files. 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 immediately using update management software, or by checking for updates using the Microsoft Update service.
See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.
Known Issues. Microsoft Knowledge Base Article 2653956 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 | Updates Replaced |
---|---|---|---|
Windows XP Service Pack 3 (KB2653956) |
Remote Code Execution | Critical | KB978601 in MS10-019 replaced by KB2653956 |
Windows XP Professional x64 Edition Service Pack 2 (KB2653956) |
Remote Code Execution | Critical | KB978601 in MS10-019 replaced by KB2653956 |
Windows Server 2003 Service Pack 2 (KB2653956) |
Remote Code Execution | Critical | KB978601 in MS10-019 replaced by KB2653956 |
Windows Server 2003 x64 Edition Service Pack 2 (KB2653956) |
Remote Code Execution | Critical | KB978601 in MS10-019 replaced by KB2653956 |
Windows Server 2003 with SP2 for Itanium-based Systems (KB2653956) |
Remote Code Execution | Critical | KB978601 in MS10-019 replaced by KB2653956 |
Windows Vista Service Pack 2 (KB2653956) |
Remote Code Execution | Critical | KB978601 in MS10-019 replaced by KB2653956 |
Windows Vista x64 Edition Service Pack 2 (KB2653956) |
Remote Code Execution | Critical | KB978601 in MS10-019 replaced by KB2653956 |
Windows Server 2008 for 32-bit Systems Service Pack 2\* (KB2653956) |
Remote Code Execution | Critical | KB978601 in MS10-019 replaced by KB2653956 |
Windows Server 2008 for x64-based Systems Service Pack 2\* (KB2653956) |
Remote Code Execution | Critical | KB978601 in MS10-019 replaced by KB2653956 |
Windows Server 2008 for Itanium-based Systems Service Pack 2 (KB2653956) |
Remote Code Execution | Critical | KB978601 in MS10-019 replaced by KB2653956 |
Windows 7 for 32-bit Systems (KB2653956) |
Remote Code Execution | Critical | KB978601 in MS10-019 replaced by KB2653956 |
Windows 7 for 32-bit Systems Service Pack 1 (KB2653956) |
Remote Code Execution | Critical | None |
Windows 7 for x64-based Systems (KB2653956) |
Remote Code Execution | Critical | KB978601 in MS10-019 replaced by KB2653956 |
Windows 7 for x64-based Systems Service Pack 1 (KB2653956) |
Remote Code Execution | Critical | None |
Windows Server 2008 R2 for x64-based Systems\* (KB2653956) |
Remote Code Execution | Critical | KB978601 in MS10-019 replaced by KB2653956 |
Windows Server 2008 R2 for x64-based Systems Service Pack 1\* (KB2653956) |
Remote Code Execution | Critical | None |
Windows Server 2008 R2 for Itanium-based Systems (KB2653956) |
Remote Code Execution | Critical | KB978601 in MS10-019 replaced by KB2653956 |
Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 (KB2653956) |
Remote Code Execution | Critical | None |
Affected Software | WinVerifyTrust Signature Validation Vulnerability - CVE-2012-0151 | Aggregate Severity Rating |
---|---|---|
Windows XP Service Pack 3 | Critical Remote Code Execution |
Critical |
Windows XP Professional x64 Edition Service Pack 2 | Critical Remote Code Execution |
Critical |
Windows Server 2003 Service Pack 2 | Critical Remote Code Execution |
Critical |
Windows Server 2003 x64 Edition Service Pack 2 | Critical Remote Code Execution |
Critical |
Windows Server 2003 with SP2 for Itanium-based Systems | Critical Remote Code Execution |
Critical |
Windows Vista Service Pack 2 | Critical Remote Code Execution |
Critical |
Windows Vista x64 Edition Service Pack 2 | Critical Remote Code Execution |
Critical |
Windows Server 2008 for 32-bit Systems Service Pack 2\* | Critical Remote Code Execution |
Critical |
Windows Server 2008 for x64-based Systems Service Pack 2\* | Critical Remote Code Execution |
Critical |
Windows Server 2008 for Itanium-based Systems Service Pack 2 | Critical Remote Code Execution |
Critical |
Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 | Critical Remote Code Execution |
Critical |
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 | Critical Remote Code Execution |
Critical |
Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1* | Critical Remote Code Execution |
Critical |
Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | Critical Remote Code Execution |
Critical |
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 3: WindowsXP-KB2653956-x86-enu.exe /quiet |
For Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB2653956-x64-enu.exe /quiet |
|
Installing without restarting | For Windows XP Service Pack 3: WindowsXP-KB2653956-x86-enu.exe /norestart |
For Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB2653956-x64-enu.exe /norestart |
|
Update log file | KB2653956.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%\$NTUninstallKB2653956$\Spuninst folder |
File Information | See Microsoft Knowledge Base Article 2653956 |
Registry Key Verification | For all supported 32-bit editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2653956\Filelist |
For all supported x64-based editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB2653956\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-KB2653956-x86-enu.exe /quiet | |
For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB2653956-x64-enu.exe /quiet | ||
For all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB2653956-ia64-enu.exe /quiet | ||
Installing without restarting | For all supported 32-bit editions of Windows Server 2003: WindowsServer2003-KB2653956-x86-enu.exe /norestart | |
For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB2653956-x64-enu.exe /norestart | ||
For all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB2653956-ia64-enu.exe /norestart | ||
Update log file | KB2653956.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%\\$NTUninstallKB2653956$\\Spuninst folder | |
**File Information** | See [Microsoft Knowledge Base Article 2653956](http://support.microsoft.com/kb/2653956) | |
**Registry Key Verification** | HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Updates\\Windows Server 2003\\SP3\\KB2653956\\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-KB2653956-x86.msu /quiet |
For all supported x64-based editions of Windows Vista: Windows6.0-KB2653956-x64.msu /quiet |
|
Installing without restarting | For all supported 32-bit editions of Windows Vista: Windows6.0-KB2653956-x86.msu /quiet /norestart |
For all supported x64-based editions of Windows Vista: Windows6.0-KB2653956-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 2653956 |
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-KB2653956-x86.msu /quiet |
For all supported x64-based editions of Windows Server 2008: Windows6.0-KB2653956-x64.msu /quiet |
|
For all supported Itanium-based editions of Windows Server 2008: Windows6.0-KB2653956-ia64.msu /quiet |
|
Installing without restarting | For all supported 32-bit editions of Windows Server 2008: Windows6.0-KB2653956-x86.msu /quiet /norestart |
For all supported x64-based editions of Windows Server 2008: Windows6.0-KB2653956-x64.msu /quiet /norestart |
|
For all supported Itanium-based editions of Windows Server 2008: Windows6.0-KB2653956-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 2653956 |
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-KB2653956-x86.msu /quiet |
For all supported x64-based editions of Windows 7: Windows6.1-KB2653956-x64.msu /quiet |
|
Installing without restarting | For all supported 32-bit editions of Windows 7: Windows6.1-KB2653956-x86.msu /quiet /norestart |
For all supported x64-based editions of Windows 7: Windows6.1-KB2653956-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 2653956 |
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-KB2653956-x64.msu /quiet |
For all supported Itanium-based editions of Windows Server 2008 R2: Windows6.1-KB2653956-ia64.msu /quiet |
|
Installing without restarting | For all supported x64-based editions of Windows Server 2008 R2: Windows6.1-KB2653956-x64.msu /quiet /norestart |
For all supported Itanium-based editions of Windows Server 2008 R2: Windows6.1-KB2653956-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 2653956 |
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:
- Robert Zacek and Igor Glucksmann of Avast Software for reporting the WinVerifyTrust Signature Validation Vulnerability (CVE-2012-0151)
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
How to obtain help and support for this security update
- Help installing updates: Support for Microsoft Update
- Security solutions for IT professionals: TechNet Security Troubleshooting and Support
- Help protect your computer that is running Windows from viruses and malware: Virus Solution and Security Center
- Local support according to your country: International Support
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 10, 2012): Bulletin published.
- V1.1 (July 31, 2012): Bulletin revised to announce a detection change in the Windows Vista packages for KB2653956 to correct a Windows Update reoffering issue. This is a detection change only. Customers who have already successfully updated their systems do not need to take any action.
Built at 2014-04-18T13:49:36Z-07:00