Security Bulletin
Microsoft Security Bulletin MS12-032 - Important
Published: May 08, 2012 | Updated: May 09, 2012
Version: 1.1
This security update resolves one publicly disclosed and one privately reported vulnerability in Microsoft Windows. The more severe of these vulnerabilities could allow elevation of privilege if an attacker logs on to a system and runs a specially crafted application.
This security update is rated Important for all supported editions of 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 vulnerabilities by modifying the way that Windows Firewall handles outbound broadcast packets and by modifying the way that the Windows TCP/IP stack handles the binding of an IPv6 address to a local interface. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. The majority of customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.
For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update at the earliest opportunity using update management software, or by checking for updates using the Microsoft Update service.
See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.
Known Issues. None
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 Vista | |||
Windows Vista Service Pack 2 (KB2688338) | Security Bypass | Important | KB2588516 in MS11-083 replaced by KB2688338 |
Windows Vista x64 Edition Service Pack 2 (KB2688338) | Security Bypass | Important | KB2588516 in MS11-083 replaced by KB2688338 |
Windows Server 2008 | |||
Windows Server 2008 for 32-bit Systems Service Pack 2 (KB2688338) | Security Bypass | Important | KB2588516 in MS11-083 replaced by KB2688338 |
Windows Server 2008 for x64-based Systems Service Pack 2 (KB2688338) | Security Bypass | Important | KB2588516 in MS11-083 replaced by KB2688338 |
Windows Server 2008 for Itanium-based Systems Service Pack 2 (KB2688338) | Security Bypass | Important | KB2588516 in MS11-083 replaced by KB2688338 |
Windows 7 | |||
Windows 7 for 32-bit Systems (KB2688338) | Elevation of Privilege | Important | KB2588516 in MS11-083 replaced by KB2688338 |
Windows 7 for 32-bit Systems Service Pack 1 (KB2688338) | Elevation of Privilege | Important | KB2588516 in MS11-083 replaced by KB2688338 |
Windows 7 for x64-based Systems (KB2688338) | Elevation of Privilege | Important | KB2588516 in MS11-083 replaced by KB2688338 |
Windows 7 for x64-based Systems Service Pack 1 (KB2688338) | Elevation of Privilege | Important | KB2588516 in MS11-083 replaced by KB2688338 |
Windows Server 2008 R2 | |||
Windows Server 2008 R2 for x64-based Systems (KB2688338) | Elevation of Privilege | Important | KB2588516 in MS11-083 replaced by KB2688338 |
Windows Server 2008 R2 for x64-based Systems Service Pack 1 (KB2688338) | Elevation of Privilege | Important | KB2588516 in MS11-083 replaced by KB2688338 |
Windows Server 2008 R2 for Itanium-based Systems (KB2688338) | Elevation of Privilege | Important | KB2588516 in MS11-083 replaced by KB2688338 |
Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 (KB2688338) | Elevation of Privilege | Important | KB2588516 in MS11-083 replaced by KB2688338 |
Server Core installation option | |||
Windows Server 2008 for 32-bit Systems Service Pack 2 (KB2688338) | Security Bypass | Important | KB2588516 in MS11-083 replaced by KB2688338 |
Windows Server 2008 for x64-based Systems Service Pack 2 (KB2688338) | Security Bypass | Important | KB2588516 in MS11-083 replaced by KB2688338 |
Windows Server 2008 R2 for x64-based Systems (KB2688338) | Elevation of Privilege | Important | KB2588516 in MS11-083 replaced by KB2688338 |
Windows Server 2008 R2 for x64-based Systems Service Pack 1 (KB2688338) | Elevation of Privilege | Important | KB2588516 in MS11-083 replaced by KB2688338 |
Non-Affected Software
Operating System |
---|
Windows XP Service Pack 3 |
Windows XP Professional x64 Edition Service Pack 2 |
Windows Server 2003 Service Pack 2 |
Windows Server 2003 x64 Edition Service Pack 2 |
Windows Server 2003 with SP2 for Itanium-based Systems |
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 lifecycle, 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 lifecycle 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.
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 May bulletin summary. For more information, see Microsoft Exploitability Index.
Affected Software | Windows Firewall Bypass Vulnerability - CVE-2012-0174 | TCP/IP Double Free Vulnerability - CVE-2012-0179 | Aggregate Severity Rating |
---|---|---|---|
Windows Vista Service Pack 2 | Important Security Bypass | Not applicable | Important |
Windows Vista x64 Edition Service Pack 2 | Important Security Bypass | Not applicable | Important |
Windows Server 2008 for 32-bit Systems Service Pack 2 | Important Security Bypass | Not applicable | Important |
Windows Server 2008 for x64-based Systems Service Pack 2 | Important Security Bypass | Not applicable | Important |
Windows Server 2008 for Itanium-based Systems Service Pack 2 | Important Security Bypass | Not applicable | Important |
Windows 7 for 32-bit Systems | Important Security Bypass | Important Elevation of Privilege | Important |
Windows 7 for 32-bit Systems Service Pack 1 | Important Security Bypass | Important Elevation of Privilege | Important |
Windows 7 for x64-based Systems | Important Security Bypass | Important Elevation of Privilege | Important |
Windows 7 for x64-based Systems Service Pack 1 | Important Security Bypass | Important Elevation of Privilege | Important |
Windows Server 2008 R2 for x64-based Systems | Important Security Bypass | Important Elevation of Privilege | Important |
Windows Server 2008 R2 for x64-based Systems Service Pack 1 | Important Security Bypass | Important Elevation of Privilege | Important |
Windows Server 2008 R2 for Itanium-based Systems | Important Security Bypass | Important Elevation of Privilege | Important |
Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | Important Security Bypass | Important Elevation of Privilege | Important |
Server Core installation option | |||
Windows Server 2008 for 32-bit Systems Service Pack 2 | Important Security Bypass | Not applicable | Important |
Windows Server 2008 for x64-based Systems Service Pack 2 | Important Security Bypass | Not applicable | Important |
Windows Server 2008 R2 for x64-based Systems | Important Security Bypass | Important Elevation of Privilege | Important |
Windows Server 2008 R2 for x64-based Systems Service Pack 1 | Important Security Bypass | Important Elevation of Privilege | Important |
A security feature bypass vulnerability exists in Windows due to the way that Windows Firewall handles outbound broadcast packets. An attacker who successfully exploited this vulnerability could bypass the Windows Firewall defense-in-depth mechanism to facilitate exploitation of other vulnerabilities.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2012-0174.
Microsoft has not identified any mitigating factors for this vulnerability.
Microsoft has not identified any workarounds for this vulnerability.
What is the scope of the vulnerability?
This is a security feature bypass vulnerability. An attacker who successfully exploited this vulnerability could bypass Windows Firewall to facilitate the exploitation of other vulnerabilities.
What causes the vulnerability?
The vulnerability is caused when Windows Firewall fails to properly filter outbound broadcast packets with an outbound firewall rule applied.
What is the component affected by this vulnerability?
The component affected by this vulnerability is the TCP/IP stack (tcpip.sys).
What is TCP/IP?
TCP/IP is a set of networking protocols that are widely used on the Internet. TCP/IP provides communications across interconnected networks of computers that have diverse hardware architectures and that run various operating systems. TCP/IP includes standards for how computers communicate and conventions for connecting networks and for routing traffic. For more information about TCP/IP, see the TechNet article, Overview of networking and TCP/IP.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could bypass Windows Firewall. An attacker could then use another vulnerability to acquire information about the target system or execute code on the target system.
How could an attacker exploit the vulnerability?
In order to use this vulnerability, an attacker would first have to gain access to the local subnet of the target computer. An attacker could then use another vulnerability to acquire information about the target system or execute code on the target system.
What systems are primarily at risk from the vulnerability?
Workstations and servers are primarily at risk from this vulnerability.
What does the update do?
The update addresses the vulnerability by modifying the way that Windows Firewall handles outbound broadcast packets.
What is the default outbound firewall policy?
The default outbound firewall policy is configured to allow all outbound network traffic from the host. In order to block unwanted outbound network traffic, customers will need to create firewall rules to block traffic. For more information about adding outbound firewall rules, please see the TechNet article Creating Rules that Block Unwanted Outbound Network Traffic.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through coordinated vulnerability disclosure.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.
An elevation of privilege vulnerability exists in the Windows TCP/IP stack that affects Windows 7 and Windows Server 2008 R2. All editions of Microsoft Windows XP, Windows Server 2003, Windows Vista, and Window Server 2008 are not affected. This vulnerability is caused when the Windows TCP/IP stack fails to properly handle the binding of IPv6 addresses.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2012-0179.
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.
Microsoft has not identified any workarounds for this vulnerability.
What is the scope of the vulnerability?
This is an elevation of privilege vulnerability.
What causes the vulnerability?
The vulnerability is caused when the Windows TCP/IP stack fails to properly handle the binding of an IPv6 address to a local interface.
What is the component affected by this vulnerability?
The component affected by this vulnerability is the TCP/IP stack (tcpip.sys).
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code in the context of another process. If this process runs with administrator privileges, 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 servers are affected by this vulnerability.
What does the update do?
The update addresses the vulnerability by modifying the way that the Windows TCP/IP stack handles the binding of an IPv6 address to a local interface.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CVE-2012-0179.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft has not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.
Security Central
Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security website provides additional information about security in Microsoft products.
Security updates are available from Microsoft Update and Windows Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."
Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, "MS07-036"), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.
Detection and Deployment Guidance
Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see Microsoft Knowledge Base Article 961747.
Microsoft Baseline Security Analyzer
Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.
The following table provides the MBSA detection summary for this security update.
Software | MBSA |
---|---|
Windows Vista Service Pack 2 | Yes |
Windows Vista x64 Edition Service Pack 2 | Yes |
Windows Server 2008 for 32-bit Systems Service Pack 2 | Yes |
Windows Server 2008 for x64-based Systems Service Pack 2 | Yes |
Windows Server 2008 for Itanium-based Systems Service Pack 2 | Yes |
Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 | Yes |
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 | Yes |
Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1 | Yes |
Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | Yes |
Note For customers using legacy software not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, please visit Microsoft Baseline Security Analyzer and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools.
Windows Server Update Services
Windows Server Update Services (WSUS) enables information technology administrators to deploy the latest Microsoft product updates to computers that are running the Windows operating system. For more information about how to deploy security updates using Windows Server Update Services, see the TechNet article, Windows Server Update Services.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
Software | SMS 2003 with ITMU | Configuration Manager 2007 |
---|---|---|
Windows Vista Service Pack 2 | Yes | Yes |
Windows Vista x64 Edition Service Pack 2 | Yes | Yes |
Windows Server 2008 for 32-bit Systems Service Pack 2 | Yes | Yes |
Windows Server 2008 for x64-based Systems Service Pack 2 | Yes | Yes |
Windows Server 2008 for Itanium-based Systems Service Pack 2 | Yes | Yes |
Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 | Yes | Yes |
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 | Yes | Yes |
Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1 | Yes | Yes |
Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | Yes | Yes |
Note Microsoft discontinued support for SMS 2.0 on April 12, 2011. For SMS 2003, Microsoft also discontinued support for the Security Update Inventory Tool (SUIT) on April 12, 2011. Customers are encouraged to upgrade to System Center Configuration Manager 2007. For customers remaining on SMS 2003 Service Pack 3, the Inventory Tool for Microsoft Updates (ITMU) is also an option.
For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.
System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007.
For more information about SMS, visit the SMS website.
For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.
Update Compatibility Evaluator and Application Compatibility Toolkit
Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit.
The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
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-KB2688338-x86.msu /quiet |
For all supported x64-based editions of Windows Vista:\ Windows6.0-KB2688338-x64.msu /quiet | |
Installing without restarting | For all supported 32-bit editions of Windows Vista:\ Windows6.0-KB2688338-x86.msu /quiet /norestart |
For all supported x64-based editions of Windows Vista:\ Windows6.0-KB2688338-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 2688338 |
Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
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.
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-KB2688338-x86.msu /quiet |
For all supported x64-based editions of Windows Server 2008:\ Windows6.0-KB2688338-x64.msu /quiet | |
For all supported Itanium-based editions of Windows Server 2008:\ Windows6.0-KB2688338-ia64.msu /quiet | |
Installing without restarting | For all supported 32-bit editions of Windows Server 2008:\ Windows6.0-KB2688338-x86.msu /quiet /norestart |
For all supported x64-based editions of Windows Server 2008:\ Windows6.0-KB2688338-x64.msu /quiet /norestart | |
For all supported Itanium-based editions of Windows Server 2008:\ Windows6.0-KB2688338-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 2688338 |
Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
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.
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-KB2688338-x86.msu /quiet |
For all supported x64-based editions of Windows 7:\ Windows6.1-KB2688338-x64.msu /quiet | |
Installing without restarting | For all supported 32-bit editions of Windows 7:\ Windows6.1-KB2688338-x86.msu /quiet /norestart |
For all supported x64-based editions of Windows 7:\ Windows6.1-KB2688338-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 2688338 |
Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
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.
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-KB2688338-x64.msu /quiet |
For all supported Itanium-based editions of Windows Server 2008 R2:\ Windows6.1-KB2688338-ia64.msu /quiet | |
Installing without restarting | For all supported x64-based editions of Windows Server 2008 R2:\ Windows6.1-KB2688338-x64.msu /quiet /norestart |
For all supported Itanium-based editions of Windows Server 2008 R2:\ Windows6.1-KB2688338-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 2688338 |
Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
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.
Microsoft thanks the following for working with us to help protect customers:
- Bojan Zdrnja of INFIGO IS for reporting the Windows Firewall Bypass Vulnerability (CVE-2012-0174)
- Anatoliy Glagolev of Genesys Telecommunications for working with us on the TCP/IP Double Free Vulnerability (CVE-2012-0179)
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.
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
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.
- V1.0 (May 8, 2012): Bulletin published.
- V1.1 (May 9, 2012): Corrected mitigating factors for CVE-2012-0174 and CVE-2012-0179 in the Vulnerability Information section.
Built at 2014-04-18T13:49:36Z-07:00