Export (0) Print
Expand All

Microsoft Security Bulletin MS09-037 - Critical

Vulnerabilities in Microsoft Active Template Library (ATL) Could Allow Remote Code Execution (973908)

Published: August 11, 2009 | Updated: December 16, 2009

Version: 2.1

General Information

Executive Summary

This security update resolves several privately reported vulnerabilities in Microsoft Active Template Library (ATL). The vulnerabilities could allow remote code execution if a user loaded a specially crafted component or control hosted on a malicious website. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

This security update is rated Critical for all supported editions of Microsoft Windows 2000 Service Pack 4, Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008. For more information on the software affected by this update, see the subsection, Affected and Non-Affected Software, in this section. For more information on the impact of, and workarounds and mitigations for controls and components that may be vulnerable to these issues, please see Microsoft Security Advisory (973882).

The security update addresses the vulnerabilities by modifying the ATL headers so that components and controls built using the headers can safely initialize from a data stream, and by providing updated versions of Windows components and controls built using corrected ATL headers. 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 immediately using update management software, or by checking for updates using the Microsoft Update service.

See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.

Known Issues. Microsoft Knowledge Base Article 973908 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues. When currently known issues and recommended solutions pertain only to specific releases of this software, this article provides links to further articles.

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 SystemComponentMaximum Security ImpactAggregate Severity RatingBulletins Replaced by this Update
Microsoft Windows 2000
Microsoft Windows 2000 Service Pack 4 Microsoft Outlook Express 5.5 Service Pack 2
(KB973354)

Microsoft Outlook Express 6 Service Pack 1
(KB973354)
Remote Code ExecutionCritical MS08-048
Microsoft Windows 2000 Service Pack 4 Windows Media Player 9
(KB973540)
Remote Code ExecutionCritical MS07-047
Microsoft Windows 2000 Service Pack 4 Windows ATL Component
(KB973507)
Remote Code ExecutionCriticalNone
Microsoft Windows 2000 Service Pack 4 DHTML Editing Component ActiveX Control
(KB973869)
Remote Code ExecutionCritical MS05-013
Windows XP
Windows XP Service Pack 2 and Windows XP Service Pack 3 Microsoft Outlook Express 6
(KB973354)
Remote Code ExecutionCriticalNone
Windows XP Service Pack 2 Windows Media Player 9, Windows Media Player 10, and Windows Media Player 11
(KB973540)
Remote Code ExecutionCritical MS07-047
Windows XP Service Pack 3 Windows Media Player 9
(KB973540)
Remote Code ExecutionCriticalNone
Windows XP Service Pack 3 Windows Media Player 10, and Windows Media Player 11
(KB973540)
Remote Code ExecutionCritical MS07-047
Windows XP Service Pack 2 and Windows XP Service Pack 3 Windows ATL Component
(KB973507)
Remote Code ExecutionCriticalNone
Windows XP Service Pack 2 DHTML Editing Component ActiveX Control
(KB973869)
Remote Code ExecutionCritical MS05-013
Windows XP Service Pack 3 DHTML Editing Component ActiveX Control
(KB973869)
Remote Code ExecutionCriticalNone
Windows XP Service Pack 2 and Windows XP Service Pack 3 Microsoft MSWebDVD ActiveX Control
(KB973815)
Remote Code ExecutionCriticalNone
Windows XP Service Pack 2 and Windows XP Service Pack 3 HtmlInput Object ActiveX Control
(KB973768)
(Media Center Edition 2005 only)
Remote Code ExecutionCriticalNone
Windows XP Professional x64 Edition Service Pack 2 Microsoft Outlook Express 6
(KB973354)
Remote Code ExecutionCriticalNone
Windows XP Professional x64 Edition Service Pack 2 Windows Media Player 10
(KB973540)
Remote Code ExecutionCritical MS07-047
Windows XP Professional x64 Edition Service Pack 2 Windows Media Player 11
(KB973540)
Remote Code ExecutionCritical MS07-047
Windows XP Professional x64 Edition Service Pack 2 Windows ATL Component
(KB973507)
Remote Code ExecutionCriticalNone
Windows XP Professional x64 Edition Service Pack 2 DHTML Editing Component ActiveX Control
(KB973869)
Remote Code ExecutionCriticalNone
Windows XP Professional x64 Edition Service Pack 2 Microsoft MSWebDVD ActiveX Control
(KB973815)
Remote Code ExecutionCriticalNone
Windows Server 2003
Windows Server 2003 Service Pack 2 Microsoft Outlook Express 6
(KB973354)
Remote Code ExecutionCriticalNone
Windows Server 2003 Service Pack 2 Windows Media Player 10
(KB973540)
Remote Code ExecutionCritical MS07-047
Windows Server 2003 Service Pack 2 Windows ATL Component
(KB973507)
Remote Code ExecutionCriticalNone
Windows Server 2003 Service Pack 2 DHTML Editing Component ActiveX Control
(KB973869)
Remote Code ExecutionCriticalNone
Windows Server 2003 Service Pack 2 Microsoft MSWebDVD ActiveX Control
(KB973815)
Remote Code ExecutionCriticalNone
Windows Server 2003 x64 Edition Service Pack 2 Microsoft Outlook Express 6
(KB973354)
Remote Code ExecutionCriticalNone
Windows Server 2003 x64 Edition Service Pack 2 Windows Media Player 10
(KB973540)
Remote Code ExecutionCritical MS07-047
Windows Server 2003 x64 Edition Service Pack 2 Windows ATL Component
(KB973507)
Remote Code ExecutionCriticalNone
Windows Server 2003 x64 Edition Service Pack 2 DHTML Editing Component ActiveX Control
(KB973869)
Remote Code ExecutionCriticalNone
Windows Server 2003 x64 Edition Service Pack 2 Microsoft MSWebDVD ActiveX Control
(KB973815)
Remote Code ExecutionCriticalNone
Windows Server 2003 with SP2 for Itanium-based Systems Microsoft Outlook Express 6
(KB973354)
Remote Code ExecutionCriticalNone
Windows Server 2003 with SP2 for Itanium-based Systems Windows ATL Component
(KB973507)
Remote Code ExecutionCriticalNone
Windows Server 2003 with SP2 for Itanium-based Systems DHTML Editing Component ActiveX Control
(KB973869)
Remote Code ExecutionCriticalNone
Windows Server 2003 with SP2 for Itanium-based Systems Microsoft MSWebDVD ActiveX Control
(KB973815)
Remote Code ExecutionCriticalNone
Windows Vista
Windows Vista Windows Media Player 11
(KB973540)
Remote Code ExecutionCritical MS07-047
Windows Vista Service Pack 1 and Windows Vista Service Pack 2 Windows Media Player 11
(KB973540)
Remote Code ExecutionCriticalNone
Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 Windows ATL Component
(KB973507)
Remote Code ExecutionCriticalNone
Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 HtmlInput Object ActiveX Control
(KB973768)
Remote Code ExecutionCriticalNone
Windows Vista x64 Edition Windows Media Player 11
(KB973540)
Remote Code ExecutionCritical MS07-047
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2 Windows Media Player 11
(KB973540)
Remote Code ExecutionCriticalNone
Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 Windows ATL Component
(KB973507)
Remote Code ExecutionCriticalNone
Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 HtmlInput Object ActiveX Control
(KB973768)
Remote Code ExecutionCriticalNone
Windows Server 2008
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 Windows Media Player 11 **
(KB973540)
Remote Code ExecutionCriticalNone
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 Windows ATL Component*
(KB973507)
Remote Code ExecutionCriticalNone
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 Windows Media Player 11 **
(KB973540)
Remote Code ExecutionCriticalNone
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 Windows ATL Component*
(KB973507)
Remote Code ExecutionCriticalNone
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 Windows ATL Component
(KB973507)
Remote Code ExecutionCriticalNone

*Windows Server 2008 Server Core installation affected. For supported editions of Windows Server 2008, this update applies, with the same severity rating, whether or not Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.

**Windows Server 2008 Server Core installation not affected. The vulnerability addressed by this update does not affect supported editions of Windows Server 2008 if Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.

Non-Affected Software

Operating System
Windows 7 for 32-bit Systems
Windows 7 for x64-based Systems
Windows Server 2008 R2 for x64-based Systems
Windows Server 2008 R2 for Itanium-based Systems

Why was this bulletin rereleased on September 8, 2009? 
Microsoft rereleased this bulletin to offer new updates for the HtmlInput Object ActiveX control on Windows XP Media Center Edition 2005, Windows Vista, Windows Vista Service Pack 1, Windows Vista Service Pack 2, Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2.

What is the HtmlInput Object ActiveX control? 
The HtmlInput Object ActiveX control enables Windows Media Center hosted HTML applications to include instances of the Triple-tap/Soft-keyboard ActiveX control on their HTML pages. The control provides a standard interface for retrieving text input from the user, enabling them to enter text by using the remote control. For more information, see the MSDN article, HtmlInput Object.

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.

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.

How does this bulletin relate to the vulnerabilities described in Microsoft Security Advisory (973882)?
This bulletin addresses Windows components that are affected by the Active Template Library (ATL) vulnerabilities described in Microsoft Security Advisory (973882).

Is this security update related to MS09-034, released as an out-of-band update on July 28, 2009? 
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? 
Yes. This security bulletin update addresses vulnerabilities in Windows components. By installing this update, users ensure that all known issues caused by vulnerable ATL headers and libraries are corrected for core Windows components.

If I have installed the MS09-034 update, do I still need to install additional components and controls issued by third-parties that address the vulnerabilities described in Microsoft Security Advisory 973882 and Microsoft Security Bulletin MS09-035?
Yes, you need to install updated controls from third parties when released. 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.

What is ATL?
The Active Template Library (ATL) is a set of template-based C++ classes that let developers 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.

What is the DHTML Editing Component ActiveX Control?
The DHTML Editing Component ActiveX control provides an HTML editor that developers can use to support dynamic Web site HTML editing in software. For more information about the DHTML Editing Component ActiveX control, see the following MSDN article.

What is the Microsoft MSWebDVD ActiveX Control?
The Microsoft MSWebDVD ActiveX control is used to create script-based DVD applications by exposing the MSWebDVD object to applications. For more information, see the following MSDN article.

What is Outlook Express?
Outlook Express is a feature of the Windows operating system for personal computers. It is used for sending and receiving e-mail.

What is Windows Media Player?
Windows Media Player is a feature of the Windows operating system for personal computers. It is used for playing audio and video.

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 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.

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

Affected Software

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareMicrosoft Video ActiveX Control Vulnerability - CVE-2008-0015ATL Header Memcopy Vulnerability - CVE-2008-0020ATL Uninitialized Object Vulnerability - CVE-2009-0901ATL COM Initialization Vulnerability - CVE-2009-2493ATL Object Type Mismatch Vulnerability - CVE-2009-2494Aggregate Severity Rating
Microsoft Windows 2000 Service Pack 4 Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows XP Media Center Edition 2005 Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows XP Service Pack 2 and Service Pack 3 Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows XP Professional x64 Edition Service Pack 2 Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows Server 2003 Service Pack 2 Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows Server 2003 x64 Edition Service Pack 2 Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows Server 2003 with SP2 for Itanium-based Systems Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2* and ** Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2* and ** Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical 
Remote Code Execution
Critical

*Windows Server 2008 Server Core installation affected. For supported editions of Windows Server 2008, this update applies, with the same severity rating, whether or not Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.

**Windows Server 2008 Server Core installation not affected. The vulnerability addressed by this update does not affect supported editions of Windows Server 2008 if Windows Server 2008 was installed using the Server Core installation option. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.

A remote code execution vulnerability exists in the Microsoft Active Template Library (ATL) due to the function CComVariant::ReadFromStream used in the ATL header. This function does not properly restrict untrusted data read from a stream. This issue leads to reading data directly onto the stack instead of reading it into the area of memory allocated for an array, which 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-2008-0015.

Mitigating Factors for Microsoft Video ActiveX Control Vulnerability - CVE-2008-0015

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:

Workarounds for Microsoft Video ActiveX Control Vulnerability - CVE-2008-0015

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:

FAQ for Microsoft Video ActiveX Control Vulnerability - CVE-2008-0015

What is the scope of the vulnerability? 
This is a remote code execution vulnerability. The vulnerability could allow remote code execution if the user visits a specially crafted Web page with Internet Explorer, instantiating a vulnerable component or control. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user.

If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

What causes the vulnerability? 
The function CComVariant::ReadFromStream used in the ATL header does not properly restrict untrusted data read from a stream. This issue could lead to reading data directly onto the stack instead of reading it into the area of memory allocated for an array.

Is this security update related to MS09-032? 
Yes. Microsoft Security Bulletin MS09-032, "Cumulative Security Update of ActiveX Kill Bits," includes ActiveX kill bits for msvidctl.dll as a part of CVE-2008-0015. This bulletin, MS09-037, also addresses components affected by CVE-2008-0015. In MS09-032, kill bits were provided for msvidctl.dll, since that component was never intended to be instantiated within Internet Explorer. The components addressed in this bulletin may be instantiated, and have been updated to address the core issue covered by CVE-2008-0015.

If I have installed the MS09-032 update, do I still need to install this update? 
Yes. This security update addresses vulnerabilities in Windows components. By installing this update, users ensure that all known issues caused by vulnerable ATL headers and libraries are corrected for core Windows components.

Are third-party ActiveX controls affected by this issue?
Although this vulnerability is in Microsoft ATL, it is not in the ATL version shipped with Visual Studio. The affected ATL headers reside in a private header file that shipped in Windows XP and Windows Server 2003. Most third-party developers use the header file that came with Visual Studio. These applications are not exposed to this vulnerability.

What might an attacker use the vulnerability to do? 
If a user has a vulnerable control on their system and an attacker bypasses the mitigations described in Microsoft Security Advisory (973882), then an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

How could an attacker exploit the vulnerability? 
An attacker could host a specially crafted Web site that is designed to exploit this vulnerability through Internet Explorer by attempting to exploit a vulnerable control, and then convince a user to view the Web site. This can also include compromised Web sites and Web sites that accept or host user-provided content or advertisements. These Web sites could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have to discover a vulnerable control, and force users to visit these Web sites. To do this, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or in an Instant Messenger request that takes users to the attacker's Web site. It could also be possible to display specially crafted Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who should not have sufficient administrative permissions are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The update addresses the vulnerability by correcting the affecting Window components and controls to restrict data read from untrusted streams to ensure it is not copied directly to the memory stack.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 
Yes. When the security bulletin was released, Microsoft had received information that this vulnerability was being exploited.

A remote code execution vulnerability exists in the Microsoft Active Template Library (ATL) due to an error in the Load method of the IPersistStreamInit interface. The Load method could allow calls to memcopy with untrusted data, which 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-2008-0020.

Mitigating Factors for ATL Header Memcopy Vulnerability - CVE-2008-0020

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:

Workarounds for ATL Header Memcopy Vulnerability - CVE-2008-0020

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:

FAQ for ATL Header Memcopy Vulnerability - CVE-2008-0020

What is the scope of the vulnerability? 
This is a remote code execution vulnerability. The vulnerability could allow remote code execution if the user visits a specially crafted Web page with Internet Explorer, instantiating a vulnerable component or control. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user.

If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

What causes the vulnerability? 
The vulnerability is caused by an error in the Load method of the IPersistStreamInit interface. The Load method could allow calls to memcopy with untrusted data.

Are third-party ActiveX controls affected by this issue?
Although this vulnerability is in Microsoft ATL, it is not in the ATL version shipped with Visual Studio. The affected ATL headers reside in a private header file that shipped in Windows XP and Windows Server 2003. Most third-party developers use the header file that came with Visual Studio. These applications are not exposed to this bug.

What might an attacker use the vulnerability to do? 
If a user has a vulnerable control on their system and an attacker bypasses the mitigations described in Microsoft Security Advisory (973882), then an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

How could an attacker exploit the vulnerability? 
An attacker could host a specially crafted Web site that is designed to exploit this vulnerability through Internet Explorer by attempting to exploit a vulnerable control, and then convince a user to view the Web site. This can also include compromised Web sites and Web sites that accept or host user-provided content or advertisements. These Web sites could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have to discover a vulnerable control, and force users to visit these Web sites. To do this, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or in an Instant Messenger request that takes users to the attacker's Web site. It could also be possible to display specially crafted Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who should not have sufficient administrative permissions are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The update addresses the issue by correcting Windows components and control to restrict the Load method of the IPersistStreamInit interface to only allow calls to memcopy with trusted data.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.

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 and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

A remote code execution vulnerability exists in the Microsoft Active Template Library (ATL) due to a bug 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 bug, 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 vulnerability 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.

Mitigating Factors for ATL Uninitialized Object Vulnerability - CVE-2009-0901

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:

Workarounds for ATL Uninitialized Object Vulnerability - CVE-2009-0901

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:

FAQ for ATL Uninitialized Object Vulnerability - CVE-2009-0901

What is the scope of the vulnerability? 
This is a remote code execution vulnerability. The vulnerability could allow remote code execution if the user visits a specially crafted Web page with Internet Explorer that instantiates a vulnerable component or control. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user.

If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

What causes the vulnerability? 
The vulnerability results from an issue in the ATL headers that could allow an attacker to call VariantClear() on a variant that has not been correctly initialized. For developers who created a component or control using ATL in this manner, the resulting component or control could allow remote code execution in the context of the logged on user.

What might an attacker use the vulnerability to do? 
If a user has a vulnerable control on their system and an attacker bypasses the mitigations described in Microsoft Security Advisory (973882), then an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

How could an attacker exploit the vulnerability? 
An attacker could host a specially crafted Web site that is designed to exploit this vulnerability through Internet Explorer by attempting to exploit a vulnerable control, and then convince a user to view the Web site. This can also include compromised Web sites and Web sites that accept or host user-provided content or advertisements. These Web sites could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have to discover a vulnerable control, and force users to visit these Web sites. To do this, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or in an Instant Messenger request that takes users to the attacker's Web site. It could also be possible to display specially crafted Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.

Are third-party ActiveX 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 theMS09-035 Visual Studio 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.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who should not have sufficient administrative permissions are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The update addresses the issue by updating Windows components and controls to ensure VariantClear() can only be called on initialized variants.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.

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 and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

A remote code execution vulnerability exists in the Microsoft Active Template Library (ATL) due to bugs 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 vulnerability 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.

Mitigating Factors for ATL COM Initialization Vulnerability - CVE-2009-2493

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:

Workarounds for ATL COM Initialization Vulnerability - CVE-2009-2493

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:

FAQ for ATL COM Initialization Vulnerability - CVE-2009-2493

What is the scope of the vulnerability? 
This is a remote code execution vulnerability. The vulnerability could allow remote code execution if the user visits a specially crafted Web page with Internet Explorer, instantiating a vulnerable component or control. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user.

If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

What causes the vulnerability? 
The vulnerability results from errors in the ATL headers that handle instantiation of an object from data streams. For components and controls built using ATL, unsafe usage of OleLoadFromStream could allow the instantiation of arbitrary objects which can bypass certain related security policies.

What might an attacker use the vulnerability to do? 
If a user has a vulnerable control on their system, and an attacker bypasses the mitigations described in Microsoft Security Advisory (973882), then if the user is logged on with administrative user rights an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

How could an attacker exploit the vulnerability? 
An attacker could host a specially crafted Web site that is designed to exploit this vulnerability through Internet Explorer by attempting to exploit a vulnerable control, and then convince a user to view the Web site. This can also include compromised Web sites and Web sites that accept or host user-provided content or advertisements. These Web sites could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have to discover a vulnerable control, and force users to visit these Web sites. To do this, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or in an Instant Messenger request that takes users to the attacker's Web site. It could also be possible to display specially crafted Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.

Are third-party ActiveX 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 theMS09-035 Visual Studio 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.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who should not have sufficient administrative permissions are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The update addresses the vulnerability by correcting the manner in which ATL handles the instantiation of objects from data stream and providing updated versions of Windows components and controls built using corrected ATL headers.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.

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 and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

A remote code execution vulnerability exists in the Microsoft Active Template Library (ATL) due to a bug in the ATL header that could allow reading a variant from a stream and leaving the variant type read with an invalid variant. When deleting the variant, it is possible to free unintended areas in memory that could be controlled by an attacker.

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

Mitigating Factors for ATL Object Type Mismatch Vulnerability - CVE-2009-2494

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:

Workarounds for ATL Object Type Mismatch Vulnerability - CVE-2009-2494

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:

FAQ for ATL Object Type Mismatch Vulnerability - CVE-2009-2494

What is the scope of the vulnerability? 
This is a remote code execution vulnerability. The vulnerability could allow remote code execution if the user visits a specially crafted Web page with Internet Explorer, instantiating a vulnerable component or control. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user.

If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

What causes the vulnerability? 
The vulnerability is caused by a bug in the ATL header that could allow reading a variant from a stream and leaving the variant type read with an invalid variant. When deleting the variant, it would be possible to free unintended areas in memory that could be controlled by an attacker, resulting in inconsistent memory contents and execution of malicious code.

Are third-party ActiveX controls affected by this issue?
Although this vulnerability is in Microsoft ATL, it is not in the ATL version shipped with Visual Studio. The affected ATL headers reside in a private header file that shipped in Windows XP and Windows Server 2003. Most third-party developers use the header file that came with Visual Studio. These applications are not exposed to this issue.

What might an attacker use the vulnerability to do? 
If a user has a vulnerable control on their system, and an attacker bypasses the mitigations described in Microsoft Security Advisory (973882), then if the user is logged on with administrative user rights an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

How could an attacker exploit the vulnerability? 
An attacker could host a specially crafted Web site that is designed to exploit this vulnerability through Internet Explorer by attempting to exploit a vulnerable control, and then convince a user to view the Web site. This can also include compromised Web sites and Web sites that accept or host user-provided content or advertisements. These Web sites could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have to discover a vulnerable control, and force users to visit these Web sites. To do this, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or in an Instant Messenger request that takes users to the attacker's Web site. It could also be possible to display specially crafted Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who should not have sufficient administrative permissions are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do? 
The update addresses the issue by properly validating variants read from a stream and providing updated versions of Windows components and controls built using corrected ATL headers.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.

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 and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

Update Information

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.

Software MBSA 2.1
Microsoft Windows 2000 Service Pack 4Yes
Windows XP Service Pack 2 and Windows XP Service Pack 3Yes
Windows XP Professional x64 Edition Service Pack 2Yes
Windows Server 2003 Service Pack 2Yes
Windows Server 2003 x64 Edition Service Pack 2Yes
Windows Server 2003 with SP2 for Itanium-based SystemsYes
Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2Yes
Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2Yes
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2Yes
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2Yes
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2Yes

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.

SoftwareSMS 2.0SMS 2003 with SUITSMS 2003 with ITMUConfiguration Manager 2007
Microsoft Windows 2000 Service Pack 4YesYesYesYes
Windows XP Service Pack 2 and Windows XP Service Pack 3YesYesYesYes
Windows XP Professional x64 Edition Service Pack 2NoNoYesYes
Windows Server 2003 Service Pack 2YesYesYesYes
Windows Server 2003 x64 Edition Service Pack 2NoNoYesYes
Windows Server 2003 with SP2 for Itanium-based SystemsNoNoYesYes
Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2NoNoSee Note for Windows Vista and Windows Server 2008 belowYes
Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2NoNoSee Note for Windows Vista and Windows Server 2008 belowYes
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2NoNoSee Note for Windows Vista and Windows Server 2008 belowYes
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2NoNoSee Note for Windows Vista and Windows Server 2008 belowYes
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2NoNoSee Note for Windows Vista and Windows Server 2008 belowYes

For SMS 2.0 and SMS 2003, 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. 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.

Note for Windows Vista and Windows Server 2008 Microsoft Systems Management Server 2003 with Service Pack 3 includes support for Windows Vista and Windows Server 2008 manageability.

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:

Windows 2000 (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 may be included in a future update rollup
Deployment
Installing without user interventionFor Microsoft Outlook Express 5.5 Service Pack 2 (KB973354):
OE5.5sp2-KB973354-Windows2000-x86-enu /quiet

For Microsoft Outlook Express 6 Service Pack 1 (KB973354):
OE6.0sp1-KB973354-Windows2000-x86-enu /quiet

For Windows Media Player 9 (KB973540):
Windows2000-WindowsMedia9-KB973540-x86-enu /quiet

For Windows ATL Component (KB973507):
Windows2000-KB973507-x86-enu /quiet

For DHTML Editing Component ActiveX Control (KB973869):
Windows2000-KB973869-x86-enu /quiet
Installing without restartingFor Microsoft Outlook Express 5.5 Service Pack 2 (KB973354):
OE5.5sp2-KB973354-Windows2000-x86-enu /norestart

For Microsoft Outlook Express 6 Service Pack 1 (KB973354):
OE6.0sp1-KB973354-Windows2000-x86-enu /norestart

For Windows Media Player 9 (KB973540):
Windows2000-WindowsMedia9-KB973540-x86-enu /norestart

For Windows ATL Component (KB973507):
Windows2000-KB973507-x86-enu /norestart

For DHTML Editing Component ActiveX Control (KB973869):
Windows2000-KB973869-x86-enu /norestart
Update log filekb973354.log, kb973540.log, kb973507.log, or kb973869.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
HotPatchingNot applicable
Removal Information For Microsoft Outlook Express 5.5 Service Pack 2 or Outlook Express 6 Service Pack 1 (KB973354):
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB973354$\Spuninst folder

For Windows Media Player 9 (KB973540):
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %WinDir%\$NTUnInstallKB973540_WM9L$\Spuninst folder

For Windows ATL Component (KB973507):
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB973507$\Spuninst folder

For DHTML Editing Component ActiveX Control (KB973869):
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB973869$\Spuninst folder
File Information For Microsoft Outlook Express 5.5 Service Pack 2 or Outlook Express 6 Service Pack 1 (KB973354):
See Microsoft Knowledge Base Article 973354

For Windows Media Player 9 (KB973540):
See Microsoft Knowledge Base Article 973540

For Windows ATL Component (KB973507):
See Microsoft Knowledge Base Article 973507

For DHTML Editing Component ActiveX Control (KB973869):
See Microsoft Knowledge Base Article 973869
Registry Key Verification For Microsoft Outlook Express 5.5 Service Pack 2 (KB973354):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Outlook Express 5.50\SP2\KB973354-OE55SP2-20090710.120000\Filelist

For Microsoft Outlook Express 6 Service Pack 1 (KB973354):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Outlook Express 6\SP1\KB973354-OE6SP1-20090710.120000\Filelist

For Windows Media Player 9 (KB973540):
HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Updates\Windows Media Player 9\SP0\KB973540_WM9L\Filelist

For Windows ATL Component (KB973507):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB973507

For DHTML Editing Component ActiveX Control (KB973869):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB973869

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, visit the Microsoft TechNet Web site.

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
/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.
/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.

Supported Spuninst.exe Switches
SwitchDescription
/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.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. 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.
    5. On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
  • Registry Key Verification

    You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.

    These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Windows XP (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 interventionFor Microsoft Outlook Express 6 (KB973354) on all supported 32-bit Editions of Windows XP:
Windowsxp-kb973354-x86-enu /quiet

For Microsoft Outlook Express 6 (KB973354) on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB973354-x64-enu /quiet

For Windows Media Player 9, Windows Media Player 10, and Windows Media Player 11 (KB973540) on Windows XP Service Pack 2:
WindowsXP-SP2-WindowsMedia-KB973540-x86-enu /quiet

For Windows Media Player 9, Windows Media Player 10, and Windows Media Player 11 (KB973540) on Windows XP Service Pack 3:
WindowsXP-WindowsMedia-KB973540-x86-enu /quiet

For Windows Media Player 10 (KB973540) on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB973540-x64-enu /quiet

For Windows Media Player 11 (KB973540) on Windows XP Professional x64 Edition Service Pack 2:
WindowsMedia11-KB973540-x64-enu /quiet

For Windows ATL Component (KB973507) on all supported 32-bit Editions of Windows XP:
WindowsXP-KB973507-x86-enu /quiet

For Windows ATL Component (KB973507) on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB973507-x64-enu /quiet

For DHTML Editing Component ActiveX Control (KB973869) on all supported 32-bit Editions of Windows XP:
WindowsXP-KB973869-x86-enu /quiet

For DHTML Editing Component ActiveX Control (KB973869) on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB973869-x64-enu /quiet

For Microsoft MSWebDVD ActiveX Control (KB973815) on all supported 32-bit Editions of Windows XP:
WindowsXP-KB973815-x86-enu /quiet

For Microsoft MSWebDVD ActiveX Control (KB973815) on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB973815-x64-enu /quiet

For HtmlInput Object ActiveX Control (KB973768) on Windows XP Media Center Edition 2005:
WindowsXPMediaCenter2005-KB973768-ENU /quiet
Installing without restartingFor Microsoft Outlook Express 6 (KB973354) on all supported 32-bit Editions of Windows XP:
Windowsxp-kb973354-x86-enu /norestart

For Microsoft Outlook Express 6 (KB973354) on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB973354-x64-enu /norestart

For Windows Media Player 9, Windows Media Player 10, and Windows Media Player 11 (KB973540) on Windows XP Service Pack 2:
WindowsXP-SP2-WindowsMedia-KB973540-x86-enu /norestart

For Windows Media Player 9, Windows Media Player 10, and Windows Media Player 11 (KB973540) on Windows XP Service Pack 3:
WindowsXP-WindowsMedia-KB973540-x86-enu /norestart

For Windows Media Player 10 (KB973540) on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB973540-x64-enu /norestart

For Windows Media Player 11 (KB973540) on Windows XP Professional x64 Edition Service Pack 2:
WindowsMedia11-KB973540-x64-enu /norestart

For Windows ATL Component (KB973507) on all supported 32-bit Editions of Windows XP:
WindowsXP-KB973507-x86-enu /norestart

For Windows ATL Component (KB973507) on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB973507-x64-enu /norestart

For DHTML Editing Component ActiveX Control (KB973869) on all supported 32-bit Editions of Windows XP:
WindowsXP-KB973869-x86-enu /norestart

For DHTML Editing Component ActiveX Control (KB973869) on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB973869-x64-enu /norestart

For Microsoft MSWebDVD ActiveX Control (KB973815) on all supported 32-bit Editions of Windows XP:
WindowsXP-KB973815-x86-enu /norestart

For Microsoft MSWebDVD ActiveX Control (KB973815) on Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB973815-x64-enu /norestart

For HtmlInput Object ActiveX Control (KB973768) on Windows XP Media Center Edition 2005:
WindowsXPMediaCenter2005-KB973768-ENU /norestart
Update log filekb973354.log, kb973540.log, kb973507.log, kb973869.log, kb973815.log, or KB973768.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
HotPatchingNot applicable
Removal Information For Microsoft Outlook Express 6 (KB973354):
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB973354$\Spuninst folder

For Windows Media Player 9, Windows Media Player 10, and Windows Media Player 11 (KB973540) on Windows XP Service pack 2:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %WinDir%\$NTUninstallKB973540_WM9L$\Spuninst folder

For Windows Media Player 9, Windows Media Player 10, and Windows Media Player 11 (KB973540) on Windows XP Service pack 3:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %WinDir%\$NTUninstallKB973540_WM9$\Spuninst folder

For Windows Media Player 10 (KB973540) on Windows XP Professional x64 Edition Service Pack 2:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %windir%\$NTUninstallKB973540$\Spuninst folder

For Windows Media Player 11 (KB973540) on Windows XP Professional x64 Edition Service Pack 2:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %WinDir%\$NTUninstallKB973540_WM11x64\Spuninst folder

For Windows ATL Component (KB973507):
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB973507$\Spuninst folder

For DHTML Editing Component ActiveX Control (KB973869):
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB973869$\Spuninst folder

For Microsoft MSWebDVD ActiveX Control (KB973815):
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB973815$\Spuninst folder

For HtmlInput Object ActiveX Control (KB973768):
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB973768$\Spuninst folder
File Information For Microsoft Outlook Express 6 (KB973354):
See Microsoft Knowledge Base Article 973354

For Windows Media Player 9, Windows Media Player 10, and Windows Media Player 11 (KB973540):
See Microsoft Knowledge Base Article 973540

For Windows ATL Component (KB973507):
See Microsoft Knowledge Base Article 973507

For DHTML Editing Component ActiveX Control (KB973869):
See Microsoft Knowledge Base Article 973869

For Microsoft MSWebDVD ActiveX Control (KB973815):
See Microsoft Knowledge Base Article 973815

For HtmlInput Object ActiveX Control (KB973768):
See Microsoft Knowledge Base Article 973768
Registry Key Verification For Microsoft Outlook Express 6 (KB973354) on Windows XP Service Pack 2 and Windows XP Service Pack 3:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB973354

For Microsoft Outlook Express 6 (KB973354) on Windows XP Professional x64 Edition Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB973354

For Windows Media Player 9, Windows Media Player 10, and Windows Media Player 11 (KB973540) on Windows XP Service Pack 2:
HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Updates\Windows Media Player\SP0\KB973540_WM9L\Filelist

For Windows Media Player 9, Windows Media Player 10, and Windows Media Player 11 (KB973540) on Windows XP Service Pack 3:
HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Updates\Windows Media Player\SP0\KB973540_WM9\Filelist

For Windows Media Player 10 (KB973540) on Windows XP Professional x64 Edition Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB973540\Filelist

For Windows Media Player 11 (KB973540) on Windows XP Professional x64 Edition Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Media Player 11\SP0\KB973540_WM11x64\Filelist

For Windows ATL Component (KB973507) on all supported 32-bit Editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB973507

For Windows ATL Component (KB973507) on Windows XP Professional x64 Edition Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB973507

For DHTML Editing Component ActiveX Control (KB973869) on all supported 32-bit Editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB973869

For DHTML Editing Component ActiveX Control (KB973869) on Windows XP Professional x64 Edition Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB973869

For Microsoft MSWebDVD ActiveX Control (KB973815) on all supported 32-bit Editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB973815
"Installed",0x10001,1

For Microsoft MSWebDVD ActiveX Control (KB973815) on Windows XP Professional x64 Edition Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB973815
"Installed",0x10001,1

For HtmlInput Object ActiveX Control (KB973768) on Windows XP Media Center Edition 2005:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB973768

Note For supported versions of Windows XP Professional x64 Edition, this security update is the same as supported versions of the Windows Server 2003 x64 Edition security 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.

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, visit the Microsoft TechNet Web site.

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
/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.

Supported Spuninst.exe Switches
SwitchDescription
/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.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. 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.
    5. On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
  • Registry Key Verification

    You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.

    These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Windows Server 2003 (all editions)

Reference Table

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

Inclusion in Future Service Packs The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionFor Microsoft Outlook Express 6 (KB973354) on all supported 32-bit editions of Windows Server 2003:
Windowsserver2003-kb973354-x86-enu /quiet
For Microsoft Outlook Express 6 (KB973354) on all supported x64-based editions of Windows Server 2003:
Windowsserver2003.WindowsXP-KB973354-x64-enu /quiet
For Microsoft Outlook Express 6 (KB973354) on all supported Itanium-based editions of Windows Server 2003:
Windowsserver2003-KB973354-ia64-enu /quiet
For Windows Media Player 10 (KB973540) on all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB973540-x86-enu /quiet
For Windows Media Player 10 (KB973540) on all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB973540-x64-enu /quiet
For Windows ATL Component (KB973507) on all supported 32-bit Editions of Windows Server 2003:
WindowsServer2003-KB973507-x86-enu /quiet
For Windows ATL Component (KB973507) on all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB973507-x64-enu /quiet
For Windows ATL Component (KB973507) on all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB973507-ia64-enu /quiet
For DHTML Editing Component ActiveX Control (KB973869) on all supported 32-bit Editions of Windows Server 2003:
WindowsServer2003-KB973869-x86-enu /quiet
For DHTML Editing Component ActiveX Control (KB973869) on all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB973869-x64-enu /quiet
For DHTML Editing Component ActiveX Control (KB973869) on all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB973869-ia64-enu /quiet
For Microsoft MSWebDVD ActiveX Control (KB973815) on all supported 32-bit Editions of Windows Server 2003:
WindowsServer2003-KB973815-x86-enu /quiet
For Microsoft MSWebDVD ActiveX Control (KB973815) on all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB973815-x64-enu /quiet
For Microsoft MSWebDVD ActiveX Control (KB973815) on all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB973815-ia64-enu /quiet
Installing without restartingFor Microsoft Outlook Express 6 (KB973354) on all supported 32-bit editions of Windows Server 2003:
Windowsserver2003-kb973354-x86-enu /norestart
For Microsoft Outlook Express 6 (KB973354) on all supported x64-based editions of Windows Server 2003:
Windowsserver2003.WindowsXP-KB973354-x64-enu /norestart
For Microsoft Outlook Express 6 (KB973354) on all supported Itanium-based editions of Windows Server 2003:
Windowsserver2003-KB973354-ia64-enu /norestart
For Windows Media Player 10 (KB973540) on all supported 32-bit editions of Windows Server 2003:
WindowsServer2003-KB973540-x86-enu /norestart
For Windows Media Player 10 (KB973540) on all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB973540-x64-enu /norestart
For Windows ATL Component (KB973507) on all supported 32-bit Editions of Windows Server 2003:
WindowsServer2003-KB973507-x86-enu /norestart
For Windows ATL Component (KB973507) on all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB973507-x64-enu /norestart
For Windows ATL Component (KB973507) on all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB973507-ia64-enu /norestart
For DHTML Editing Component ActiveX Control (KB973869) on all supported 32-bit Editions of Windows Server 2003:
WindowsServer2003-KB973869-x86-enu /norestart
For DHTML Editing Component ActiveX Control (KB973869) on all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB973869-x64-enu /norestart
For DHTML Editing Component ActiveX Control (KB973869) on all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB973869-ia64-enu /norestart
For Microsoft MSWebDVD ActiveX Control (KB973815) on all supported 32-bit Editions of Windows Server 2003:
WindowsServer2003-KB973815-x86-enu /norestart
For Microsoft MSWebDVD ActiveX Control (KB973815) on all supported x64-based editions of Windows Server 2003:
WindowsServer2003.WindowsXP-KB973815-x64-enu /norestart
For Microsoft MSWebDVD ActiveX Control (KB973815) on all supported Itanium-based editions of Windows Server 2003:
WindowsServer2003-KB973815-ia64-enu /norestart
Update log filekb973354.log, kb973540.log, kb973507.log, kb973869.log, or kb973815.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
HotPatchingThis security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341.
Removal Information For Microsoft Outlook Express 6 (KB973354):
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB973354$\Spuninst folder

For Windows Media Player 10 (KB973540):
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB973540$\Spuninst folder

For Windows ATL Component (KB973507):
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB973507$\Spuninst folder

For DHTML Editing Component ActiveX Control (KB973869):
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB973869$\Spuninst folder

For Microsoft MSWebDVD ActiveX Control (KB973815):
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB973815$\Spuninst folder
File Information For Microsoft Outlook Express 6 (KB973354):
See Microsoft Knowledge Base Article 973354

For Windows Media Player 10 (KB973540):
See Microsoft Knowledge Base Article 973540

For Windows ATL Component (KB973507):
See Microsoft Knowledge Base Article 973507

For DHTML Editing Component ActiveX Control (KB973869):
See Microsoft Knowledge Base Article 973869

For Microsoft MSWebDVD ActiveX Control (KB973815):
See Microsoft Knowledge Base Article 973815
Registry Key Verification For Microsoft Outlook Express 6 (KB973354):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB973354

For Windows Media Player 10 (KB973540):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB973540

For Windows ATL Component (KB973507):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB973507

For DHTML Editing Component ActiveX Control (KB973869):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB973869

For DHTML Editing Component ActiveX Control (KB973815):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB973815
"Installed",0x10001,1

Deployment Information

Installing the Update

When you install this security update, the installer checks to see if 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, visit the Microsoft TechNet Web site.

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
/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 many of 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.

Supported Spuninst.exe Switches
SwitchDescription
/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.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. 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.
    5. On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
  • Registry Key Verification

    You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.

    These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Windows Vista (all editions)

Reference Table

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

Inclusion in Future Service Packs The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionFor Windows Media Player 11 (KB973540) on all supported 32-bit editions of Windows Vista:
Windows6.0-KB973540-x86 /quiet

For Windows Media Player 11 (KB973540) on all supported x64-based editions of Windows Vista:
Windows6.0-KB973540-x64 /quiet
For Windows ATL Component (KB973507) on all supported 32-bit editions of Windows Vista:
Windows6.0-KB973507-x86 /quiet

For Windows ATL Component (KB973507) on all supported x64-based editions of Windows Vista:
Windows6.0-KB973507-x64 /quiet
For HtmlInput Object ActiveX Control (KB973768) on all supported 32-bit editions of Windows Vista:
Windows6.0-KB973768-x86 /quiet

For HtmlInput Object ActiveX Control (KB973768) on all supported x64-based editions of Windows Vista:
Windows6.0-KB973768-x64 /quiet
Installing without restartingFor Windows Media Player 11 (KB973540) on all supported 32-bit editions of Windows Vista:
Windows6.0-KB973540-x86 /quiet /norestart

For Windows Media Player 11 (KB973540) on all supported x64-based editions of Windows Vista:
Windows6.0-KB973540-x64 /quiet /norestart
For Windows ATL Component (KB973507) on all supported 32-bit editions of Windows Vista:
Windows6.0-KB973507-x86 /quiet /norestart

For Windows ATL Component (KB973507) on all supported x64-based editions of Windows Vista:
Windows6.0-KB973507-x64 /quiet /norestart
For HtmlInput Object ActiveX Control (KB973768) on all supported 32-bit editions of Windows Vista:
Windows6.0-KB973768-x86 /quiet /norestart

For HtmlInput Object ActiveX Control (KB973768) on all supported x64-based editions of Windows Vista:
Windows6.0-KB973768-x64 /quiet /norestart
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
HotPatchingNot applicable.
Removal Information WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.
File Information For Windows Media Player 11 (KB973540):
See Microsoft Knowledge Base Article 973540

For Windows ATL Component (KB973507):
See Microsoft Knowledge Base Article 973507

For HtmlInput Object ActiveX Control (KB973768):
See Microsoft Knowledge Base Article 973768
Registry Key Verification Note 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, /help Displays help on supported switches.
/quiet Suppresses the display of status or error messages.
/norestart When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.

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

Verifying That the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

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

  • File Version Verification

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

    1. Click Start and then enter an update file name in Start Search.
    2. When the file appears under Programs, right-click on the file name and click Properties.
    3. Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
    4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
    5. Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Windows Server 2008 (all editions)

Reference Table

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

Inclusion in Future Service Packs The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionFor Windows Media Player 11 (KB973540) on all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB973540-x86 /quiet

For Windows Media Player 11 (KB973540) on all supported x64-based editions of Windows Server 2008:
Windows6.0-KB973540-x64 /quiet
For Windows ATL Component (KB973507) on all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB973507-x86 /quiet

For Windows ATL Component (KB973507) on all supported x64-based editions of Windows Server 2008:
Windows6.0-KB973507-x64 /quiet

For Windows ATL Component (KB973507) on all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB973507-ia64 /quiet
Installing without restartingFor Windows Media Player 11 (KB973540) on all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB973540-x86 /quiet /norestart

For Windows Media Player 11 (KB973540) on all supported x64-based editions of Windows Server 2008:
Windows6.0-KB973540-x64 /quiet /norestart
For Windows ATL Component (KB973507) on all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB973507-x86 /quiet /norestart

For Windows ATL Component (KB973507) on all supported x64-based editions of Windows Server 2008:
Windows6.0-KB973507-x64 /quiet /norestart

For Windows ATL Component (KB973507) on all supported Itanium-based editions of Windows Server 2008:
Windows6.0-KB973507-ia64 /quiet /norestart
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
HotPatchingNot applicable.
Removal Information WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.
File Information For Windows Media Player 11 (KB973540):
See Microsoft Knowledge Base Article 973540

For Windows ATL Component (KB973507):
See Microsoft Knowledge Base Article 973507
Registry Key Verification Note 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, /help Displays help on supported switches.
/quiet Suppresses the display of status or error messages.
/norestart When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.

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

Verifying That the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

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

  • File Version Verification

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

    1. Click Start and then enter an update file name in Start Search.
    2. When the file appears under Programs, right-click on the file name and click Properties.
    3. Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
    4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
    5. Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Other Information

Acknowledgments

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

  • Ryan Smith and Alex Wheeler of IBM ISS X-Force for initially reporting the Microsoft Video ActiveX Control Remote Code Execution Vulnerability (CVE-2008-0015)
  • Robert Freeman of IBM ISS X-Force for reporting the ATL Header Memcopy Vulnerability (CVE-2008-0020)
  • David Dewey of IBM ISS X-Force for reporting the ATL Uninitialized Object Vulnerability (CVE-2009-0901)
  • Ryan Smith of VeriSign iDefense Labs for reporting the ATL COM Initialization Vulnerability (CVE-2009-2493)
  • Ryan Smith of VeriSign iDefense Labs for reporting the ATL Object Type Mismatch Vulnerability (CVE-2009-2494)

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 (August 11, 2009): Bulletin published.
  • V1.1 (August 12, 2009): Removed erroneous reference to known issues from the Frequently Asked Questions (FAQ) Related to This Security Update section; added new entries to the section, FAQ for Microsoft Video ActiveX Control Vulnerability - CVE-2008-0015, describing the relationship between this bulletin and Microsoft Security Bulletin MS09-032; corrected restart requirements throughout the bulletin; and performed miscellaneous edits.
  • V1.2 (August 19, 2009): Revised the Affected Software table to clarify that the DHTML Editing Component ActiveX Control (KB973869) update replaces MS05-013 for Windows XP Service Pack 2, but not for Windows XP Service Pack 3; and that the Windows Media Player 11 (KB973540) update replaces MS07-047 for Windows Vista x64 Edition, but not for Windows Vista x64 Edition Service Pack 1 or Windows Vista x64 Edition Service Pack 2.
  • V2.0 (September 8, 2009): Bulletin rereleased to offer new updates for the HtmlInput Object ActiveX control on Windows XP Media Center Edition 2005 and all supported Windows Vista editions. Also corrected several table entries in the Security Update Deployment section for Windows Media Player on Microsoft Windows 2000, Windows XP, and Windows Server 2003.
  • V2.1 (December 16, 2009): Added a link to Microsoft Knowledge Base Article 973908 under Known Issues in the Executive Summary.

Built at 2014-04-18T13:49:36Z-07:00

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft