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

Microsoft Security Bulletin MS13-006 - Important

Vulnerability in Microsoft Windows Could Allow Security Feature Bypass

Published: January 08, 2013 | Updated: December 16, 2013

Version: 1.3

General Information

Executive Summary

This security update resolves a privately reported vulnerability in the implementation of SSL and TLS in Microsoft Windows. The vulnerability could allow security feature bypass if an attacker intercepts encrypted web traffic handshakes.

This security update is rated Important for all supported editions of Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, and Windows RT. 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 SSL provider component handles encrypted network packets. 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. Most 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 2785220 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, see Microsoft Support Lifecycle.

Affected Software 

Operating SystemMaximum Security ImpactAggregate Severity RatingUpdates Replaced
Windows Vista
Windows Vista Service Pack 2
(KB2785220)
Security Feature BypassImportantNone
Windows Vista x64 Edition Service Pack 2
(KB2785220)
Security Feature BypassImportantNone
Windows Server 2008
Windows Server 2008 for 32-bit Systems Service Pack 2
(KB2785220)
Security Feature BypassImportantNone
Windows Server 2008 for x64-based Systems Service Pack 2
(KB2785220)
Security Feature BypassImportantNone
Windows Server 2008 for Itanium-based Systems Service Pack 2
(KB2785220)
Security Feature BypassImportantNone
Windows 7
Windows 7 for 32-bit Systems
(KB2785220)
Security Feature BypassImportantNone
Windows 7 for 32-bit Systems Service Pack 1
(KB2785220)
Security Feature BypassImportantNone
Windows 7 for x64-based Systems
(KB2785220)
Security Feature BypassImportantNone
Windows 7 for x64-based Systems Service Pack 1
(KB2785220)
Security Feature BypassImportantNone
Windows Server 2008 R2
Windows Server 2008 R2 for x64-based Systems
(KB2785220)
Security Feature BypassImportantNone
Windows Server 2008 R2 for x64-based Systems Service Pack 1
(KB2785220)
Security Feature BypassImportantNone
Windows Server 2008 R2 for Itanium-based Systems
(KB2785220)
Security Feature BypassImportantNone
Windows Server 2008 R2 for Itanium-based Systems Service Pack 1
(KB2785220)
Security Feature BypassImportantNone
Windows 8
Windows 8 for 32-bit Systems
(KB2785220)
Security Feature BypassImportantNone
Windows 8 for 64-bit Systems
(KB2785220)
Security Feature BypassImportantNone
Windows Server 2012
Windows Server 2012
(KB2785220)
Security Feature BypassImportantNone
Windows RT
Windows RT[1]
(KB2785220)
Security Feature BypassImportantNone
Server Core installation option
Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)
(KB2785220)
Security Feature BypassImportantNone
Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)
(KB2785220)
Security Feature BypassImportantNone
Windows Server 2008 R2 for x64-based Systems (Server Core installation)
(KB2785220)
Security Feature BypassImportantNone
Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
(KB2785220)
Security Feature BypassImportantNone
Windows Server 2012 (Server Core installation)
(KB2785220)
Security Feature BypassImportantNone

[1]Windows RT security updates are provided via Windows Update.

 

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.

Where are the hashes of the security updates? 
The SHA1 and SHA2 hashes of the security updates can be used to verify the authenticity of downloaded security update packages. For the hash information pertaining to this update, see Microsoft Knowledge Base Article 2785220.

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, see 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, see 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

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.

Operating SystemMicrosoft SSL Version 3 and TLS Protocol Security Feature Bypass Vulnerability - CVE-2013-0013Aggregate Severity Rating
Windows Vista
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
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
Windows 7 for 32-bit SystemsImportant 
Security Feature Bypass
Important
Windows 7 for 32-bit Systems Service Pack 1 Important 
Security Feature Bypass
Important
Windows 7 for x64-based Systems Important 
Security Feature Bypass
Important
Windows 7 for x64-based Systems Service Pack 1 Important 
Security Feature Bypass
Important
Windows Server 2008 R2
Windows Server 2008 R2 for x64-based Systems Important 
Security Feature Bypass
Important
Windows Server 2008 R2 for x64-based Systems Service Pack 1 Important 
Security Feature Bypass
Important
Windows Server 2008 R2 for Itanium-based Systems Important 
Security Feature Bypass
Important
Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 Important 
Security Feature Bypass
Important
Windows 8
Windows 8 for 32-bit Systems Important 
Security Feature Bypass
Important
Windows 8 for 64-bit Systems Important 
Security Feature Bypass
Important
Windows Server 2012
Windows Server 2012 Important 
Security Feature Bypass
Important
Windows RT
Windows RT Important 
Security Feature Bypass
Important
Server Core installation option
Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)Important 
Security Feature Bypass
Important
Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) Important 
Security Feature Bypass
Important
Windows Server 2008 R2 for x64-based Systems (Server Core installation) Important 
Security Feature Bypass
Important
Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) Important 
Security Feature Bypass
Important
Windows Server 2012 (Server Core installation) Important 
Security Feature Bypass
Important

A security feature bypass vulnerability exists in the way that the Microsoft Windows SSL/TLS (Secure Socket Layer and Transport Layer Security) handle the SSL version 3 (SSLv3) and TLS protocols. The vulnerability could allow security feature bypass if an attacker injects specially crafted content into an SSL/TLS session.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2013-0013.

Mitigating Factors for Microsoft SSL Version 3 and TLS Protocol Security Feature Bypass Vulnerability - CVE-2013-0013

Microsoft has not identified any mitigating factors for this vulnerability.

Workarounds for Microsoft SSL Version 3 and TLS Protocol Security Feature Bypass Vulnerability - CVE-2013-0013

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:

  • Configure Internet Explorer to disable SSLv2

    You can help protect against attempts to exploit this vulnerability through Internet Explorer by changing your settings to disable SSLv2. To do this, perform the following steps:

    1. In Internet Explorer, click Internet Options on the Tools menu.
    2. Click the Advanced tab.
    3. Scroll down to the Security section.
    4. Uncheck the box beside Use SSL 2.0.
    5. Click OK to return to Internet Explorer.

    Impact of workaround. There are side effects to disabling SSLv2. Some websites that are on the Internet or on an intranet may use SSLv2 to provide secure communication. You will be unable to use these websites after disabling SSLv2.

    How to undo the workaround.

    1. In Internet Explorer, click Internet Options on the Tools menu.
    2. Click the Advanced tab.
    3. Scroll down to the Security section.
    4. Check the box beside Use SSL 2.0.
    5. Click OK to return to Internet Explorer.

     

  • Configure Internet Information Services to disable SSLv2

    Warning Modifying the Registry incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from incorrect modification of the Registry can be solved. Modify the Registry at your own risk.

    You can help protect against attempts to exploit this vulnerability through your IIS websites by changing your settings to disable SSLv2. To do this, perform the following steps:

    1. Click Start, click Run, type regedit, and then click OK.
    2. In Registry Editor, locate the following registry key/folder:

      HKey_Local_Machine\System\CurrentControlSet\Control\SecurityProviders \SCHANNEL\Protocols\SSL 2.0

    3. Right-click the SSL 2.0 folder and select New and then click Key. Name the new folder Server.
    4. Inside the Server folder, click the Edit menu, select New, and click DWORD (32-bit) Value.
    5. Enter Enabled as the name and hit Enter.
    6. Ensure that it shows 0x00000000 (0) under the Data column (it should by default). If it doesn't, right-click and select Modify and enter 0 as the Value data.
    7. Restart the computer.

    Impact of workaround. There are side effects to disabling SSLv2. Some web browsers may use SSLv2 to engage in secure communication. These users will be unable to view your websites after disabling SSLv2.

    How to undo the workaround.

    1. Click Start, click Run, type regedit, and then click OK.
    2. In Registry Editor, locate the following registry key/folder:

      HKey_Local_Machine\System\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server

    3. Inside the Server folder, Right-click click the Enabled DWORD and select Delete. Select Yes.
    4. Restart the computer.

 

FAQ for Microsoft SSL Version 3 and TLS Protocol Security Feature Bypass Vulnerability - CVE-2013-0013

What is the scope of the vulnerability? 
This is a security feature bypass vulnerability. An attacker who successfully exploited this vulnerability could bypass security features in SSL version 3 or TLS that mitigate against a connection being downgraded to SSL version 2.

What causes the vulnerability? 
The vulnerability is caused when Windows fails to properly handle SSL/TLS session version negotiation.

What are TLS and SSL? 
The Transport Layer Security (TLS) Handshake Protocol is responsible for the authentication and key exchange necessary to establish or resume secure sessions. The Secure Sockets Layer (SSL) is a predecessor of the Transport Layer Security protocol. Both TLS and SSL perform the same functions and support secure network communications using a combination of public and secret key technology.

For more information, see the TechNet article, How TLS/SSL works.

What might an attacker use the vulnerability to do? 
An attacker monitoring an encrypted communication who successfully exploited this vulnerability could silently downgrade a SSL version 3 or TLS connection to SSL version 2, which supports weak encryption cyphers.

How could an attacker exploit the vulnerability? 
In a man-in-the-middle attack, an attacker could inject malformed traffic into an SSL version 3 or TLS browsing session between Internet Explorer and a third-party server or a third-party client and a Microsoft server, silently downgrading the connection to SSL version 2.

What is a man-in-the-middle attack? 
A man-in-the-middle attack occurs when an attacker reroutes communication between two users through the attacker’s computer without the knowledge of the two communicating users. Each user in the communication unknowingly sends traffic to and receives traffic from the attacker, all the while thinking they are communicating only with the intended user.

What systems are primarily at risk from the vulnerability? 
Any systems that send and receive SSL/TLS encrypted traffic are at the most risk from this vulnerability.

What does the update do? 
The update addresses the vulnerability by modifying the way that the Windows SSL provider component handles encrypted network packets.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through coordinated vulnerability disclosure.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.

Update Information

Security Central

Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security 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, "MS12-001"), you can add all 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) lets administrators scan local and remote systems for missing security updates as well as common security misconfigurations. For more information, see Microsoft Baseline Security Analyzer.

The following table provides the MBSA detection summary for this security update.

Software MBSA
Windows Vista Service Pack 2Yes
Windows Vista x64 Edition Service Pack 2Yes
Windows Server 2008 for 32-bit Systems Service Pack 2Yes
Windows Server 2008 for x64-based Systems Service Pack 2Yes
Windows Server 2008 for Itanium-based Systems Service Pack 2Yes
Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1Yes
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1Yes
Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1Yes
Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1Yes
Windows 8 for 32-bit SystemsNo
Windows 8 for 64-bit SystemsNo
Windows Server 2012No
Windows RTNo

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

Windows Server Update Services

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

Systems Management Server

The following table provides the SMS detection and deployment summary for this security update.

SoftwareSMS 2003 with ITMUSystem Center Configuration Manager (All Supported Versions)
Windows Vista Service Pack 2YesYes
Windows Vista x64 Edition Service Pack 2YesYes
Windows Server 2008 for 32-bit Systems Service Pack 2YesYes
Windows Server 2008 for x64-based Systems Service Pack 2YesYes
Windows Server 2008 for Itanium-based Systems Service Pack 2YesYes
Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1YesYes
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1YesYes
Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1YesYes
Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1YesYes
Windows 8 for 32-bit SystemsYesYes
Windows 8 for 64-bit SystemsYesYes
Windows Server 2012YesYes
Windows RTNoNo

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. 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 uses WSUS 3.0 for detection of updates. For more information, see System Center.

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:

Windows Vista (all editions)

Reference Table

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

Inclusion in Future Service PacksThe update for this issue will be included in a future service pack or update rollup
Deployment 
Installing without user interventionFor all supported 32-bit editions of Windows Vista:
Windows6.0-KB2785220-x86.msu /quiet
For all supported x64-based editions of Windows Vista:
Windows6.0-KB2785220-x64.msu /quiet
Installing without restartingFor all supported 32-bit editions of Windows Vista:
Windows6.0-KB2785220-x86.msu /quiet /norestart
For all supported x64-based editions of Windows Vista:
Windows6.0-KB2785220-x64.msu /quiet /norestart
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement 
Restart required?Yes, you must restart your system after you apply this security update.
HotPatchingNot applicable.
Removal InformationWUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.
File InformationSee Microsoft Knowledge Base Article 2785220
Registry Key VerificationNote A registry key does not exist to validate the presence of this update.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

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

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/?, /h, /helpDisplays help on supported switches.
/quietSuppresses the display of status or error messages.
/norestartWhen combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.

Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.

Verifying That the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

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

  • File Version Verification

    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start and then enter an update file name in the Start Search box.
    2. When the file appears under Programs, right-click the file name and click Properties.
    3. On the General tab, compare the file size with the file information tables provided in the bulletin KB article.

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

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
    5. Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Windows Server 2008 (all editions)

Reference Table

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

Inclusion in Future Service PacksThe update for this issue will be included in a future service pack or update rollup
Deployment 
Installing without user interventionFor all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB2785220-x86.msu /quiet
For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB2785220-x64.msu /quiet
For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB2785220-ia64.msu /quiet
Installing without restartingFor all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB2785220-x86.msu /quiet /norestart
For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB2785220-x64.msu /quiet /norestart
For all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB2785220-ia64.msu /quiet /norestart
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement 
Restart required?Yes, you must restart your system after you apply this security update.
HotPatchingNot applicable.
Removal InformationWUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.
File InformationSee Microsoft Knowledge Base Article 2785220
Registry Key VerificationNote A registry key does not exist to validate the presence of this update.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

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

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/?, /h, /helpDisplays help on supported switches.
/quietSuppresses the display of status or error messages.
/norestartWhen combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.

Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.

Verifying That the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

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

  • File Version Verification

    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start and then enter an update file name in the Start Search box.
    2. When the file appears under Programs, right-click the file name and click Properties.
    3. On the General tab, compare the file size with the file information tables provided in the bulletin KB article.

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

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
    5. Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Windows 7 (all editions)

Reference Table

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

Inclusion in Future Service PacksThe update for this issue will be included in a future service pack or update rollup
Deployment 
Installing without user interventionFor all supported 32-bit editions of Windows 7:
Windows6.1-KB2785220-x86.msu /quiet
For all supported x64-based editions of Windows 7:
Windows6.1-KB2785220-x64.msu /quiet
Installing without restartingFor all supported 32-bit editions of Windows 7:
Windows6.1-KB2785220-x86.msu /quiet /norestart
For all supported x64-based editions of Windows 7:
Windows6.1-KB2785220-x64.msu /quiet /norestart
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement 
Restart required?Yes, you must restart your system after you apply this security update.
HotPatchingNot applicable.
Removal InformationTo uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates.
File InformationSee Microsoft Knowledge Base Article 2785220
Registry Key VerificationNote A registry key does not exist to validate the presence of this update.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

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

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/?, /h, /helpDisplays help on supported switches.
/quietSuppresses the display of status or error messages.
/norestartWhen combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.
/warnrestart:<seconds>When combined with /quiet, the installer will warn the user before initiating restart.
/promptrestartWhen combined with /quiet, the installer will prompt before initiating restart.
/forcerestartWhen combined with /quiet, the installer will forcefully close applications and initiate restart.
/log:<file name>Enables logging to specified file.
/extract:<destination>Extracts the package contents to the destination folder.
/uninstall /kb:<KB Number>Uninstalls the security update.

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

Verifying That the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

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

  • File Version Verification

    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start and then enter an update file name in the Search box.
    2. When the file appears under Programs, right-click the file name and click Properties.
    3. On the General tab, compare the file size with the file information tables provided in the bulletin KB article.

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

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
    5. Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Windows Server 2008 R2 (all editions)

Reference Table

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

Inclusion in Future Service PacksThe update for this issue will be included in a future service pack or update rollup
Deployment 
Installing without user interventionFor all supported x64-based editions of Windows Server 2008 R2:
Windows6.1-KB2785220-x64.msu /quiet
For all supported Itanium-based editions of Windows Server 2008 R2:
Windows6.1-KB2785220-ia64.msu /quiet
Installing without restartingFor all supported x64-based editions of Windows Server 2008 R2:
Windows6.1-KB2785220-x64.msu /quiet /norestart
For all supported Itanium-based editions of Windows Server 2008 R2:
Windows6.1-KB2785220-ia64.msu /quiet /norestart
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement 
Restart required?Yes, you must restart your system after you apply this security update.
HotPatchingNot applicable.
Removal InformationTo uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates.
File InformationSee Microsoft Knowledge Base Article 2785220
Registry Key VerificationNote A registry key does not exist to validate the presence of this update.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

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

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/?, /h, /helpDisplays help on supported switches.
/quietSuppresses the display of status or error messages.
/norestartWhen combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.
/warnrestart:<seconds>When combined with /quiet, the installer will warn the user before initiating restart.
/promptrestartWhen combined with /quiet, the installer will prompt before initiating restart.
/forcerestartWhen combined with /quiet, the installer will forcefully close applications and initiate restart.
/log:<file name>Enables logging to specified file.
/extract:<destination>Extracts the package contents to the destination folder.
/uninstall /kb:<KB Number>Uninstalls the security update.

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

Verifying That the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

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

  • File Version Verification

    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start and then enter an update file name in the Start Search box.
    2. When the file appears under Programs, right-click the file name and click Properties.
    3. On the General tab, compare the file size with the file information tables provided in the bulletin KB article.

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

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
    5. Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Windows 8 (all editions)

Reference Table

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

Inclusion in Future Service PacksThe update for this issue will be included in a future service pack or update rollup
Deployment 
Installing without user interventionFor all supported 32-bit editions of Windows 8:
Windows8-RT-KB2785220-x86.msu /quiet
For all supported 64-bit editions of Windows 8:
Windows8-RT-KB2785220-x64.msu /quiet
Installing without restartingFor all supported 32-bit editions of Windows 8:
Windows8-RT-KB2785220-x86.msu /quiet /norestart
For all supported x64-bit editions of Windows 8:
Windows8-RT-KB2785220-x64.msu /quiet /norestart
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement 
Restart required?Yes, you must restart your system after you apply this security update.
HotPatchingNot applicable.
Removal InformationTo uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, click Windows Update, and then click Installed updates and select from the list of updates.
File InformationSee Microsoft Knowledge Base Article 2785220
Registry Key VerificationNote A registry key does not exist to validate the presence of this update.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

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

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/?, /h, /helpDisplays help on supported switches.
/quietSuppresses the display of status or error messages.
/norestartWhen combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.
/warnrestart:<seconds>When combined with /quiet, the installer will warn the user before initiating restart.
/promptrestartWhen combined with /quiet, the installer will prompt before initiating restart.
/forcerestartWhen combined with /quiet, the installer will forcefully close applications and initiate restart.
/log:<file name>Enables logging to specified file.
/extract:<destination>Extracts the package contents to the destination folder.
/uninstall /kb:<KB Number>Uninstalls the security update.

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

Verifying That the Update Has Been Applied

  • File Version Verification

    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start and then enter an update file name in the Search box.
    2. When the file appears under Programs, right-click the file name and click Properties.
    3. On the General tab, compare the file size with the file information tables provided in the bulletin KB article.

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

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
    5. Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Windows Server 2012 (all editions)

Reference Table

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

Inclusion in Future Service PacksThe update for this issue will be included in a future service pack or update rollup
Deployment 
Installing without user interventionFor all supported editions of Windows Server 2012:
Windows8-RT-KB2785220-x64.msu /quiet
Installing without restartingFor all supported editions of Windows Server 2012:
Windows8-RT-KB2785220-x64.msu /quiet /norestart
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement 
Restart required?Yes, you must restart your system after you apply this security update.
HotPatchingNot applicable.
Removal InformationTo uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, click Windows Update, and then click Installed updates and select from the list of updates.
File InformationSee Microsoft Knowledge Base Article 2785220
Registry Key VerificationNote A registry key does not exist to validate the presence of this update.

Deployment Information

Installing the Update

When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

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

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
/?, /h, /helpDisplays help on supported switches.
/quietSuppresses the display of status or error messages.
/norestartWhen combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.
/warnrestart:<seconds>When combined with /quiet, the installer will warn the user before initiating restart.
/promptrestartWhen combined with /quiet, the installer will prompt before initiating restart.
/forcerestartWhen combined with /quiet, the installer will forcefully close applications and initiate restart.
/log:<file name>Enables logging to specified file.
/extract:<destination>Extracts the package contents to the destination folder.
/uninstall /kb:<KB Number>Uninstalls the security update.

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

Verifying That the Update Has Been Applied

  • File Version Verification

    Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

    1. Click Start and then enter an update file name in the Start Search box.
    2. When the file appears under Programs, right-click the file name and click Properties.
    3. On the General tab, compare the file size with the file information tables provided in the bulletin KB article.

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

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
    5. Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Windows RT (all editions)

The following table contains the security update information for this software.

Inclusion in Future Service PacksThe update for this issue will be included in a future service pack or update rollup.
Deployment 
This update is available via Windows Update only.
Restart Requirement 
Restart required?Yes, you must restart your system after you apply this security update.
Removal InformationClick Control Panel, click System and Security, and then under Windows Update, click Installed updates and select from the list of updates.
File InformationSee Microsoft Knowledge Base Article 2785220

Other Information

Acknowledgments

Microsoft thanks the following for working with us to help protect customers:

  • Kenichiro Katayama for reporting the Microsoft SSL Version 3 and TLS Protocol Security Feature Bypass Vulnerability (CVE-2013-0013)

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 go to 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

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 8, 2013): Bulletin published.
  • V1.1 (February 12, 2013): Added a link to Microsoft Knowledge Base Article 2785220 under Known Issues in the Executive Summary.
  • V1.2 (July 9, 2013): Bulletin revised to announce a detection change in the Windows Vista packages for the 2785220 update 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.
  • V1.3 (December 16, 2013): Revised bulletin to announce a detection change to correct an offering issue for Windows RT (2785220). This is a detection change only. There were no changes to the update files. Customers who have successfully installed the update do not need to take any action.

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

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