Microsoft Security Bulletin MS09-035 - Moderate

Why was this bulletin rereleased on January 12, 2010?
Microsoft rereleased this bulletin to add Windows Embedded CE 6.0 to affected software. The update for Windows Embedded CE 6.0 (KB974616) is a cumulative update that is available from the Microsoft Download Center only. Customers using the Windows Embedded CE 6.0 platform should consider applying the cumulative update. No other update packages are affected by this rerelease.

Why was this bulletin revised on September 8, 2009? 
This bulletin was revised to communicate that the Known issues with this security update section in the associated Microsoft Knowledge Base Article 969706 been revised to change the number for known issue KB974223 to KB974479, in order to offer a non-security update to fix the issue. Microsoft Visual Studio 2008 Service Pack 1 users who have not installed the security update described in this bulletin will automatically receive both the security update and the non-security update through Microsoft Update. Microsoft Visual Studio 2008 Service Pack 1 users who have already installed the security update will automatically be offered the non-security update through Windows Update. Microsoft Visual Studio 2008 Service Pack 1 users who have already installed the security update do not need to reinstall the security update, and need only install the non-security update if they are experiencing the issues described in KB974479.

Why was this bulletin rereleased on August 11, 2009?
Microsoft rereleased this bulletin to offer new updates for the following platforms:

• Microsoft Visual Studio 2005 Service Pack 1 (KB973673)
• Microsoft Visual Studio 2008 (KB973674)
• Microsoft Visual Studio 2008 Service Pack 1 (KB973675)

The new security updates are for developers who use Visual Studio to create components and controls for mobile applications using ATL for Smart Devices. All Visual Studio developers should install these new updates so that they can use Visual Studio to create components and controls that are not vulnerable to the reported issues.

For more information on this known issue, see Microsoft Knowledge Base Article 969706.

Why was this bulletin revised on August 4, 2009? 
This bulletin was revised to communicate that the Known issues with this security update section in the associated Microsoft Knowledge Base Article 969706 been revised, and that the update detection logic for KB973923 and KB973924 has been revised to correct a package re-offering issue. The original detection logic determined whether the update needed to be installed by checking to confirm that the update was not already installed. The Visual C++ Redistributable packages (KB973544, KB973551, KB973552), available from the Microsoft Download Center, are a full superset of the corresponding ATL update packages (KB973923, KB973924), available from Microsoft Update only. Customers who have installed the updated version of the Visual C++ Redistributable package do not need to install the corresponding ATL update packages. The detection changes account for this and do not re-offer the ATL Update packages when the corresponding fixed version of the Visual C++ Redistributable update is already installed. A new entry was also added to this Frequently Asked Questions (FAQ) Related to This Security Update section to clarify the difference between the Visual C++ Redistributable packages and the other Visual Studio updates. Enterprises that do not use Microsoft Update for deployment of updates that need to deploy the updates offered by this bulletin by some other means may download and deploy the full Visual C++ Redistributable packages since these are a full superset of the corresponding ATL update packages.

What is the difference between the Visual C++ Redistributable packages and the other Visual Studio updates? 
The Visual C++ Redistributable packages are full versions of this product that can be redistributed by anyone with their applications. Customers who need to ship the Visual C++ Redistributable should pick up these packages and bundle them or chain them into their setups. The other Visual Studio updates are available for customers who have previously installed an older version of the Visual C++ Redistributable product or have installed the Visual Studio product. These update packages are offered to customers through Microsoft Update only and will be applicable only if an earlier version of the Visual C++ Redistributable or Visual Studio is present.

Why do the Microsoft Download Center update KB numbers for Visual C++ Redistributable packages differ from the SMS, SCCM, WSUS and MU update KB numbers? 
The full versions of the fixed Visual C++ 2005 and 2008 redistributable packages (KB973544, KB973551, and KB973552) are listed on the Microsoft Download Center only as these are full new versions of the products. The updates listed on SMS, SCCM, WSUS, and MU (KB973923, KB9739234) are updates only for customers who have previously installed vulnerable versions of the Visual C++ redistributable packages. These updates are not the versions on the download center. Microsoft does not recommend customers redistribute any version other than the full versions that can be downloaded from the Microsoft Download Center (KB973544, KB973551, and KB973552).

Why was this security update released out of band? 
This security update is being released out of band to address issues disclosed in Microsoft Security Advisory (973882), "Vulnerabilities in Microsoft Active Template Library (ATL) Could Allow Remote Code Execution."

How does this bulletin relate to the vulnerabilities described in Microsoft Security Advisory (973882)?
This bulletin addresses vulnerabilities in the public version of the Active Template Library (ATL). Vulnerabilities in the private version of ATL are described in Microsoft Security Advisory (973882).

If these are remote code execution vulnerabilities, why is this bulletin only rated Moderate? 
This bulletin is rated Moderate because Microsoft Visual Studio, by default, is not affected by these vulnerabilities. Controls and components built using the affected ATL are vulnerable, and if affected, would be rated Critical or Moderate depending on the type of vulnerability present in the control or component.

Are Visual Studio users directly affected by these vulnerabilities? 
No. The existence of Visual Studio on your system does not make you vulnerable to this issue.

The update associated with this bulletin is intended for developers who create components and controls so that they can use Visual Studio to create components and controls that are not vulnerable to the reported issues. Only vulnerable components and controls developed with an affected ATL version are affected by this issue. Developers who built or redistributed components and controls built with affected versions of the ATL should install the update provided in this bulletin and follow the steps provided to ensure that their components and controls do not contain the vulnerabilities described in this bulletin.

Which versions of the ActiveTemplate Library are affected by these vulnerabilities?
Versions 7.0, 7.1, 8.0, and 9.0 are affected. All others versions are unsupported.

Which versions of Visual Studio are affected?
Please see Affected and Non-Affected Software, in this Microsoft Security Bulletin.

Is this security update related to MS09-034, also released as an out-of-band update? 
Yes. Microsoft Security Bulletin MS09-034, "Cumulative Security Update for Internet Explorer," includes a mitigation that helps prevent components and controls built using the vulnerable ATL from being exploited in Internet Explorer, as well as addressing multiple unrelated vulnerabilities. The new defense in depth protections offered in MS09-034 include updates to Internet Explorer 5.01, Internet Explorer 6 and Internet Explorer 6 Service Pack 1, Internet Explorer 7, and Internet Explorer 8, that monitor and help prevent the successful exploitation of all known public and private ATL vulnerabilities, including the vulnerabilities that could lead to bypassing ActiveX's kill bit security feature. These protections are designed to help protect customers from Web-based attacks.

If I have installed the MS09-034 update, do I still need to install this update? 
This security update is specifically intended for developers of components and controls. Developers who built or redistributed components and controls built with affected versions of the Active Template Library should install the update provided in this bulletin and follow the steps provided to ensure that their components and controls do not contain the vulnerabilities described in this bulletin.

If I have installed the MS09-034 update, do I still need to install additional components and controlsissued by Microsoft or third parties that address the vulnerabilities described in Microsoft Security Advisory 973882 and Microsoft Security Bulletin MS09-035? 
The MS09-034 Internet Explorer mitigation does not address the underlying vulnerabilities within certain components and controls developed with the Active Template Library. Microsoft recommends that developers follow the guidance provided in this bulletin to modify and rebuild all components and controls affected by vulnerabilities described in this bulletin.

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.

What is ATL?
The Active Template Library (ATL) is a set of template-based C++ classes that let you create small, fast Component Object Model (COM) objects. It has special support for key COM features, including stock implementations, dual interfaces, standard COM enumerator interfaces, connection points, tear-off interfaces, and ActiveX controls. For more information, see the following MSDN article.

Are third-party components and controls affected by this issue?
Some third-party components and controls may be affected by this issue if certain conditions were met during the building of the components and controls. Microsoft recommends that developers follow the guidance provided in this bulletin to modify and rebuild all components and controls affected by vulnerabilities described in this bulletin.

I am a third-party application developer and I use ATL in my components and controls. Are my components and controls vulnerable, and if so, how do I update them? 
For instructions on determining whether your components and controls are vulnerable and how to update them, see the following MSDN Article.

Why does this update address several reported security vulnerabilities? 
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers need to install this update only.

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. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.

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. For more information about the Windows Product Lifecycle, visit Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services.

Customers who require custom support for older releases 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 Microsoft Worldwide Information, select the country, 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 Windows Operating System Product Support Lifecycle FAQ.

I am a developer and I have questions regarding this issue that are not documented in this Microsoft Security Bulletin. What can I do?
As part of our response to this issue, Microsoft is providing specialized developer content and links to forums to get your questions answered by Microsoft resources and the Microsoft developer community. For more information, please see the following MSDN Article.

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 July bulletin summary. For more information, see Microsoft Exploitability Index.

A remote code execution vulnerability exists in the Microsoft Active Template Library (ATL) due to an issue in the ATL headers that could allow an attacker to force VariantClear to be called on a VARIANT that has not been correctly initialized. Because of this, the attacker can control what happens when VariantClear is called during handling of an error by supplying a corrupt stream. This vulnerability only directly affects systems with components and controls installed that were built using Visual Studio ATL. This issue could allow a remote, unauthenticated user to perform remote code execution on an affected system. An attacker could exploit the vulnerability by constructing a specially crafted Web page. When a user views the Web page, the vulnerability could allow remote code execution.

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

A remote code execution vulnerability exists in the Microsoft Active Template Library (ATL) due to issues in the ATL headers that handle instantiation of an object from data streams. This vulnerability only directly affects systems with components and controls installed that were built using Visual Studio ATL. For components and controls built using ATL, unsafe usage of OleLoadFromStream could allow the instantiation of arbitrary objects which can bypass related security policy, such as kill bits within Internet Explorer. This issue could allow a remote, unauthenticated user to perform remote code execution on an affected system. An attacker could exploit the vulnerability by constructing a specially crafted Web page. When a user views the Web page, the vulnerability could allow remote code execution.

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

An information disclosure vulnerability exists in the Microsoft Active Template Library (ATL) that could allow a string to be read without a terminating NULL character. An attacker could manipulate this string to read extra data beyond the end of the string and thus disclose information in memory. This vulnerability only directly affects systems with components and controls installed that were built using Visual Studio ATL. An attacker who successfully exploited this vulnerability could run a malicious component or control that could disclose information, forward user data to a third party, or access any data on the affected systems that was accessible to the logged-on user. Note that this vulnerability would not allow an attacker to execute code or to elevate their user rights directly, but it could be used to produce information that could be used to try to further compromise the affected system.

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

The following Detection and Deployment Guidance provides information on how to ensure the versions of Visual Studio in this Security Bulletin have been updated with ATL headers that address the vulnerabilities discussed above.

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.

Note Starting August 1, 2009, Microsoft will discontinue support for Office Update and the Office Update Inventory Tool. To continue getting the latest updates for Microsoft Office products, use Microsoft Update. For more information, see About Microsoft Office Update: Frequently Asked Questions.

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.

For more information about MBSA 2.1, see MBSA 2.1 Frequently Asked Questions.

Windows Server Update Services

By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.

Systems Management Server

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

For SMS 2.0 and SMS 2003, the SMS SUS Feature Pack (SUSFP), which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0.

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. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about the Office Inventory Tool and other 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 5.0.

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.

Affected Software

For information about the specific security update for your affected software, click the appropriate link: