Security Bulletin
Microsoft Security Bulletin MS11-082 - Important
Vulnerabilities in Host Integration Server Could Allow Denial of Service (2607670)
Published: October 11, 2011
Version: 1.0
General Information
Executive Summary
This security update resolves two publicly disclosed vulnerabilities in Host Integration Server. The vulnerabilities could allow denial of service if a remote attacker sends specially crafted network packets to a Host Integration Server listening on UDP port 1478 or TCP ports 1477 and 1478. Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems that are connected to the Internet have a minimal number of ports exposed. In this case, the Host Integration Server ports should be blocked from the Internet.
This security update is rated Important for all supported editions of Microsoft Host Integration Server 2004, Microsoft Host Integration Server 2006, Microsoft Host Integration Server 2009, and Microsoft Host Integration Server 2010. 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 Host Integration Server handles specially crafted UDP and TCP packets. 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
Affected and Non-Affected Software
The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.
Affected Software
| Operating System | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by this Update |
|---|---|---|---|
| Microsoft Host Integration Server 2004 Service Pack 1\ (KB2578757) | Denial of Service | Important | None |
| Microsoft Host Integration Server 2006 Service Pack 1\ (KB2579597) | Denial of Service | Important | None |
| Microsoft Host Integration Server 2009\ (KB2579598) | Denial of Service | Important | None |
| Microsoft Host Integration Server 2010\ (KB2579599) | Denial of Service | Important | None |
Non-Affected Software
| Operating System |
|---|
| Microsoft Host Integration Server 2000 Service Pack 2 |
Frequently Asked Questions (FAQ) Related to This Security Update
Where are the file information details?
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.
I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. For more information about the product lifecycle, visit the Microsoft Support Lifecycle Web site.
It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. To determine the support lifecycle for your software release, see Select a Product for Lifecycle Information. For more information about service packs for these software releases, see Lifecycle Supported Service Packs.
Customers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country in the Contact Information list, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Microsoft Support Lifecycle Policy FAQ.
Vulnerability Information
Severity Ratings and Vulnerability Identifiers
The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the October bulletin summary. For more information, see Microsoft Exploitability Index.
| Affected Software | Endless Loop DoS in snabase.exe Vulnerability - CVE-2011-2007 | Access of Unallocated Memory DoS Vulnerability - CVE-2011-2008 | Aggregate Severity Rating |
|---|---|---|---|
| Microsoft Host Integration Server 2004 Service Pack 1 | Important \ Denial of Service | Important \ Denial of Service | Important |
| Microsoft Host Integration Server 2006 Service Pack 1 | Important \ Denial of Service | Important \ Denial of Service | Important |
| Microsoft Host Integration Server 2009 | Important \ Denial of Service | Important \ Denial of Service | Important |
| Microsoft Host Integration Server 2010 | Important \ Denial of Service | Important \ Denial of Service | Important |
Endless Loop DoS in snabase.exe Vulnerability - CVE-2011-2007
An unauthenticated denial of service vulnerability exists in the way that Host Integration Server handles some UDP and TCP network traffic. The vulnerability could allow a remote user to cause snabase.exe, snaserver.exe, snalink.exe, or mngagent.exe to stop responding to new requests.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2011-2007.
Mitigating Factors for Endless Loop DoS in snabase.exe Vulnerability - CVE-2011-2007
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:
- Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems that are connected to the Internet have a minimal number of ports exposed. In this case, the Host Integration Server ports should be blocked from the Internet.
Workarounds for Endless Loop DoS in snabase.exe Vulnerability - CVE-2011-2007
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:
Block TCP ports1477 and 1478and UDP port 1478 at your firewall
These ports are used to initiate a connection with the affected component. Blocking them at the enterprise firewall, both inbound and outbound, will help protect systems that are behind that firewall from attempts to exploit this vulnerability. We recommend that you block all unsolicited inbound communication from the Internet to help prevent attacks that may use other ports. For more information about ports, see TechNet article, TCP and UDP Port Assignments. For more information about the Windows Firewall, see TechNet article, How to Configure Windows Firewall on a Single Computer.
FAQ for Endless Loop DoS in snabase.exe Vulnerability - CVE-2011-2007
What is the scope of the vulnerability?
This is a denial of service vulnerability. A remote, anonymous attacker who exploited this vulnerability could cause the affected SNA Server service and all dependent services to stop responding. Note that this vulnerability would not allow an attacker to execute code or to elevate their user rights.
What causes the vulnerability?
This vulnerability is caused by improper input validation when Host Integration Server processes specially crafted network traffic.
What might an attacker use the vulnerability to do?
A remote, anonymous attacker who exploited this vulnerability could cause the affected system's SNA Server service to stop responding to new requests.
How could an attacker exploit the vulnerability?
A remote attacker could exploit this vulnerability by sending specially crafted network packets to Host Integration Server listening on UDP port 1478 or TCP ports 1477 and 1478.
What systems are primarily at risk from the vulnerability?
Servers running Host Integration Server (HIS).
What does the update do?
This update addresses the vulnerability by modifying the way that Host Integration Server handles specially crafted UDP and TCP packets.
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-2011-2007.
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.
Access of Unallocated Memory DoS Vulnerability - CVE-2011-2008
An unauthenticated denial of service vulnerability exists in the way that Host Integration Server handles some UDP and TCP network traffic. The vulnerability could allow a remote user to cause snabase.exe, snaserver.exe, snalink.exe, or mngagent.exe to stop responding to new requests.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2011-2008.
Mitigating Factors for Access of Unallocated Memory DoS Vulnerability - CVE-2011-2008
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:
- Firewall best practices and standard default firewall configurations can help protect networks from attacks that originate outside the enterprise perimeter. Best practices recommend that systems that are connected to the Internet have a minimal number of ports exposed. In this case, the Host Integration Server ports should be blocked from the Internet.
Workarounds for Access of Unallocated Memory DoS Vulnerability - CVE-2011-2008
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:
Block TCP ports 1477 and 1478 and UDP port 1478 at your firewall
These ports are used to initiate a connection with the affected component. Blocking them at the enterprise firewall, both inbound and outbound, will help protect systems that are behind that firewall from attempts to exploit this vulnerability. We recommend that you block all unsolicited inbound communication from the Internet to help prevent attacks that may use other ports. For more information about ports, see TechNet article, TCP and UDP Port Assignments. For more information about the Windows Firewall, see TechNet article, How to Configure Windows Firewall on a Single Computer.
FAQ for Access of Unallocated Memory DoS Vulnerability - CVE-2011-2008
What is the scope of the vulnerability?
This is a denial of service vulnerability. A remote, anonymous attacker who exploited this vulnerability could cause the affected SNA Server service and all dependent services to stop responding.
What causes the vulnerability?
This vulnerability is caused by improper input validation when Host Integration Server processes specially crafted network traffic.
What might an attacker use the vulnerability to do?
A remote, anonymous attacker who exploited this vulnerability could cause the affected system's SNA Server service to stop responding to new requests.
How could an attacker exploit the vulnerability?
A remote attacker could exploit this vulnerability by sending specially crafted network packets to Host Integration Server listening on UDP port 1478 or TCP ports 1477 and 1478.
What systems are primarily at risk from the vulnerability?
Servers running Host Integration Server (HIS).
What does the update do?
This update addresses the vulnerability by modifying the way that Host Integration Server handles specially crafted UDP and TCP packets.
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-2011-2008.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.
Update Information
Detection and Deployment Tools and Guidance
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 Web site 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 |
|---|---|
| Microsoft Host Integration Server 2004 Service Pack 1 | Yes |
| Microsoft Host Integration Server 2006 Service Pack 1 | Yes |
| Microsoft Host Integration Server 2009 | Yes |
| Microsoft Host Integration Server 2010 | 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 |
|---|---|---|
| Microsoft Host Integration Server 2004 Service Pack 1 | Yes | Yes |
| Microsoft Host Integration Server 2006 Service Pack 1 | Yes | Yes |
| Microsoft Host Integration Server 2009 | Yes | Yes |
| Microsoft Host Integration Server 2010 | 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 Web site.
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 Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Microsoft Host Integration Server (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
|---|---|
| Deployment | |
| Installing without user intervention | For Microsoft Host Integration Server 2004 Service Pack 1:\ HIS2004-SP1-KB2578757-x86-ENU.exe /quiet |
| For Microsoft Host Integration Server 2006 Service Pack 1:\ HIS2006-SP1-KB2579597-ENU.exe /quiet | |
| For Microsoft Host Integration Server 2009:\ HIS2009-RTM-KB2579598-ENU /quiet | |
| For Microsoft Host Integration Server 2010:\ HIS2010-RTM-KB2579599-ENU /quiet | |
| Installing without restarting | For Microsoft Host Integration Server 2004 Service Pack 1:\ HIS2004-SP1-KB2578757-x86-ENU.exe /norestart |
| For Microsoft Host Integration Server 2006 Service Pack 1:\ HIS2006-SP1-KB2579597-ENU.exe /norestart | |
| For Microsoft Host Integration Server 2009:\ HIS2009-RTM-KB2579598-ENU /norestart | |
| For Microsoft Host Integration Server 2010:\ HIS2010-RTM-KB2579599-ENU /norestart | |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
| HotPatching | Not applicable |
| Removal Information | Use Add or Remove Programs tool in Control Panel. |
| File Information | For Microsoft Host Integration Server 2004 Service Pack 1:\ See Microsoft Knowledge Base Article 2578757 |
| For Microsoft Host Integration Server 2006 Service Pack 1:\ See Microsoft Knowledge Base Article 2579597 | |
| For Microsoft Host Integration Server 2009:\ See Microsoft Knowledge Base Article 2579598 | |
| For Microsoft Host Integration Server 2010:\ See Microsoft Knowledge Base Article 2579599 | |
| Registry Key Verification | For Microsoft Host Integration Server 2004 Service Pack 1:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Host Integration Server 2004 SP1 Hotfix [See KB article 2578757 for details]GDR |
| For Microsoft Host Integration Server 2004 Service Pack 1 (Japan only):\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Host Integration Server 2004 SP1 Hotfix [KB 2578757]GDR | |
| For Microsoft Host Integration Server 2006 Service Pack 1 (32-bit systems):\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Host Integration Server 2006 SP1 Hotfix [See KB article 2579597 for details]LDR | |
| For Microsoft Host Integration Server 2006 Service Pack 1 (x64-based systems):\ HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Host Integration Server 2006 SP1 Hotfix [See KB article 2579597 for details]LDR | |
| For Microsoft Host Integration Server 2009 (32-bit systems):\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Host Integration Server 2009 Hotfix [See KB article 2579598 for details]GDR or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Host Integration Server 2009 Hotfix [See KB article 2579598 for details]LDR | |
| For Microsoft Host Integration Server 2009 (x64-based systems):\ HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Host Integration Server 2009 Hotfix [See KB article 2579598 for details]GDR or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Host Integration Server 2009 Hotfix [See KB article 2579598 for details]LDR | |
| For Microsoft Host Integration Server 2010 (32-bit systems):\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Host Integration Server 2010 Hotfix [See KB article 2579599 for detail]GDR or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Host Integration Server 2010 Hotfix [See KB article 2579599 for detail]LDR | |
| For Microsoft Host Integration Server 2010 (x64-based systems):\ HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Host Integration Server 2010 Hotfix [See KB article 2579599 for detail]GDR or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Host Integration Server 2010 Hotfix [See KB article 2579599 for detail]LDR |
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the installer, see Microsoft Knowledge Base Article 832475.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Displays a dialog box prompting the local user to allow a restart. |
| Special Options | |
| /overwriteoem | Overwrites OEM files without prompting. |
| /nobackup | Does not back up files needed for uninstall. |
| /forceappsclose | Forces other programs to close when the computer shuts down. |
| /log:path | Allows the redirection of installation log files. |
| /integrate:path | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. |
| /extract[:path] | Extracts files without starting the Setup program. |
| /ER | Enables extended error reporting. |
| /verbose | Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Displays a dialog box prompting the local user to allow a restart. |
| Special Options | |
| /forceappsclose | Forces other programs to close when the computer shuts down. |
| /log:path | Allows the redirection of installation log files. |
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 click Search.
In the Search Results pane, click All files and folders under Search Companion.
In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Other Information
Microsoft Active Protections Program (MAPP)
To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.
Support
- Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support.
- International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.
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 (October 11, 2011): Bulletin published.
Built at 2014-04-18T13:49:36Z-07:00