Computer Security
[EN] securityvulns.ru no-pyccku


Related information

  Microsoft Data Analyzer ActiveX Control memory corruption

From:MICROSOFT <secure_(at)_microsoft.com>
Date:10.02.2010
Subject:Microsoft Security Bulletin MS10-008 - Critical Cumulative Security Update of ActiveX Kill Bits (978262)

Microsoft Security Bulletin MS10-008 - Critical
Cumulative Security Update of ActiveX Kill Bits (978262)
Published: February 09, 2010

Version: 1.0
General Information
Executive Summary

This security update addresses a privately reported vulnerability for Microsoft software. This security update is rated Critical for all supported editions of Microsoft Windows 2000 and Windows XP, Important for all supported editions of Windows Vista and Windows 7, Moderate for all supported editions of Windows Server 2003, and Low for all supported editions of Windows Server 2008 and Windows Server 2008 R2. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The vulnerability could allow remote code execution if a user views a specially crafted Web page that instantiates an ActiveX control with Internet Explorer. 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 update also includes kill bits for four third-party ActiveX controls.

The security update addresses the vulnerability by setting a kill bit so that the vulnerable control does not run in Internet Explorer. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection 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. None
Top of sectionTop of section
Affected and Non-Affected Software

The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.

Affected Software
Operating System Maximum Security Impact Aggregated Severity Rating Bulletins Replaced by This Update

Microsoft Windows 2000 Service Pack 4


Remote Code Execution


Critical


MS09-055

Windows XP Service Pack 2 and Windows XP Service Pack 3


Remote Code Execution


Critical


MS09-055

Windows XP Professional x64 Edition Service Pack 2


Remote Code Execution


Critical


MS09-055

Windows Server 2003 Service Pack 2


Remote Code Execution


Moderate


MS09-055

Windows Server 2003 x64 Edition Service Pack 2


Remote Code Execution


Moderate


MS09-055

Windows Server 2003 with SP2 for Itanium-based Systems


Remote Code Execution


Moderate


MS09-055

Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2


Remote Code Execution


Important


MS09-055

Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2


Remote Code Execution


Important


MS09-055

Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2**


Remote Code Execution


Low


MS09-055

Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2**


Remote Code Execution


Low


MS09-055

Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2


Remote Code Execution


Low


MS09-055

Windows 7 for 32-bit Systems


Remote Code Execution


Important


MS09-055

Windows 7 for x64-based Systems


Remote Code Execution


Important


MS09-055

Windows Server 2008 R2 for x64-based Systems**


Remote Code Execution


Low


MS09-055

Windows Server 2008 R2 for Itanium-based Systems


Remote Code Execution


Low


MS09-055

**Server Core installation not affected. The vulnerabilities addressed by this update do not affect supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, when installed using the Server Core installation option. For more information on this installation option, see the MSDN articles, Server Core and Server Core for Windows Server 2008 R2. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.
Top of sectionTop of section

Frequently Asked Questions (FAQ) Related to This Security Update

What kill bits does this Cumulative Security Update of ActiveX Kill Bits contain?
This Cumulative Security Update of ActiveX Kill Bits contains new kill bits and all kill bits previously released in MS08-023, Security Update of ActiveX Kill Bits; MS08-032, Cumulative Security Update of ActiveX Kill Bits; MS09-032, Cumulative Security Update of ActiveX Kill Bits; MS09-055, Cumulative Security Update of ActiveX Kill Bits; and advisories entitled Update Rollup for ActiveX Kill Bits, Microsoft Security Advisory 953839, Microsoft Security Advisory 956391, Microsoft Security Advisory 960715, and Microsoft Security Advisory 969898.

What is a kill bit?
A security feature in Microsoft Internet Explorer makes it possible to prevent an ActiveX control from ever being loaded by the Internet Explorer HTML-rendering engine. This is done by making a registry setting and is referred to as setting the kill bit. After the kill bit is set, the control can never be loaded, even when it is fully installed. Setting the kill bit makes sure that even if a vulnerable component is introduced or is re-introduced to a system, it remains inert and harmless.

For more information on kill bits, see Microsoft Knowledge Base Article 240797: How to stop an ActiveX control from running in Internet Explorer.

What is a security update of ActiveX kill bits?
A security update of ActiveX kill bits contains the class IDs (CLSID) of certain ActiveX controls that are the basis of the security update. This security bulletin lists these CLSIDs in the Vulnerability Information section.

Why does this update not contain any binary files?
This update only makes changes to the registry to disable the controls from instantiating in Internet Explorer.

Should I install this update if I do not have the affected component installed or use the affected platform?
Yes. Installing this update will block the vulnerable control from running in Internet Explorer.

Do I need to reapply this update if I install an ActiveX control discussed in this security update at a later date?
No, reapplying this update is not required. The kill bit will block Internet Explorer from running the control even if the control is installed at a later date.

Does this update contain any kill bits that are not Microsoft-specific?
Yes. Microsoft has been requested by organizations to set the kill bit for controls that the organizations own and have found to be vulnerable. See the subsection, "Third-Party Kill Bits," in the Vulnerability Information section.

Does this update contain kill bits that were previously shipped in a Microsoft Security Update?
This update sets the kill bits for the RSClientPrint ActiveX control previously addressed in the Microsoft Security Bulletin MS09-062.

For more information regarding this ActiveX control and how it may be updated, review the Microsoft Bulletin Vulnerabilities in GDI+ Could Allow Remote Code Execution (957488).

Does this update contain kill bits that were previously shipped in an Internet Explorer security update?
No, this update does not include kill bits that were previously shipped in an Internet Explorer security update. We recommend that you install the latest Cumulative Security Update for Internet Explorer.

Why does this security update have different severity levels for different Windows operating systems?
This update has different severity levels because different mitigations apply to the vulnerability depending on the operating system. One such mitigation is that Internet Explorer on Windows Server 2003 and Windows Server 2008 runs in a restricted mode known as Enhanced Security Configuration.

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 the following Microsoft Support Lifecycle. For more information about the extended security update support period for these software releases, visit the Microsoft Product Support Services Web site.

Customers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, 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.
Top of sectionTop of section
Vulnerability Information

Severity Ratings and Vulnerability Identifiers

The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the February bulletin summary. For more information, see Microsoft Exploitability Index.
Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Operating System Microsoft Data Analyzer ActiveX Control Vulnerability - CVE-2010-0252 Aggregate Severity Rating

Microsoft Windows 2000 Service Pack 4


Critical
Remote Code Execution


Critical

Windows XP Service Pack 2 and Windows XP Service Pack 3


Critical
Remote Code Execution


Critical

Windows XP Professional x64 Edition Service Pack 2


Critical
Remote Code Execution


Critical

Windows Server 2003 Service Pack 2


Moderate
Remote Code Execution


Moderate

Windows Server 2003 x64 Edition Service Pack 2


Moderate
Remote Code Execution


Moderate

Windows Server 2003 with SP2 for Itanium-based Systems


Moderate
Remote Code Execution


Moderate

Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2


Important
Remote Code Execution


Important

Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2


Important
Remote Code Execution


Important

Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2**


Low
Remote Code Execution


Low

Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2**


Low
Remote Code Execution


Low

Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2


Low
Remote Code Execution


Low

Windows 7 for 32-bit Systems


Important
Remote Code Execution


Important

Windows 7 x64 Edition


Important
Remote Code Execution


Important

Windows Server 2008 R2 for x64-based Systems**


Low
Remote Code Execution


Low

Windows Server 2008 R2 for Itanium-based Systems


Low
Remote Code Execution


Low

**Server Core installation not affected. The vulnerabilities addressed by this update do not affect supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, when installed using the Server Core installation option. For more information on this installation option, see the MSDN articles, Server Core and Server Core for Windows Server 2008 R2. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.
Top of sectionTop of section

Microsoft Data Analyzer ActiveX Control Vulnerability - CVE-2010-0252

A remote code execution vulnerability exists in the Microsoft Data Analyzer ActiveX Control. 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. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user.

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

Mitigating Factors for Microsoft Data Analyzer ActiveX Control Vulnerability - CVE-2010-0252

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state that could reduce the severity of exploitation of vulnerability. The following mitigating factors may be helpful in your situation:


In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, 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 Instant Messenger message that takes users to the attacker’s Web site.


An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. 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.


A malicious Web site cannot exploit this vulnerability on systems where Microsoft Data Analyzer is not already installed.
Top of sectionTop of section

Workarounds for Microsoft Data Analyzer ActiveX Control Vulnerability - CVE-2010-0252

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:


Prevent COM objects from running in Internet Explorer

You can disable attempts to instantiate a COM object in Internet Explorer by setting the kill bit for the control in the registry.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

For detailed steps that you can use to prevent a control from running in Internet Explorer, see Microsoft Knowledge Base Article 240797. Follow the steps in this article to create a Compatibility Flags value in the registry to prevent a COM object from being instantiated in Internet Explorer.

Note The Class Identifiers and corresponding files where the ActiveX objects are contained are documented under "What does the update do?" in the FAQ for Microsoft Data Analyzer ActiveX Control Vulnerability - CVE-2010-0252 section. Replace {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} below with the Class Identifiers found in that section.

To set the kill bit for a CLSID with a value of {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}, paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension.

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}]
"Compatibility Flags"=dword:00000400

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\ActiveX Compatibility\{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}]
"Compatibility Flags"=dword:00000400

You can apply this .reg file to individual systems by double-clicking it.

You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy. For more information about Group Policy, visit the following Microsoft Web sites:


Group Policy collection


What is Group Policy Object Editor?


Core Group Policy tools and settings

Note You must restart Internet Explorer for your changes to take effect.

Impact of Workaround. There is no impact as long as the object is not intended to be used in Internet Explorer.

How to undo the workaround. Delete the registry keys previously added in implementing this workaround.


Set Internet and Local intranet security zone settings to "High" to prompt before running ActiveX Controls and Active Scripting in these zones

You can help protect against exploitation of this vulnerability by changing your settings for the Internet security zone to prompt before running ActiveX controls and Active Scripting. You can do this by setting your browser security to High.

To raise the browsing security level in Internet Explorer, follow these steps:

1.


On the Internet Explorer Tools menu, click Internet Options.

2.


In the Internet Options dialog box, click the Security tab, and then click the Internet icon.

3.


Under Security level for this zone, move the slider to High. This sets the security level for all Web sites you visit to High.

Note If no slider is visible, click Default Level, and then move the slider to High.

Note Setting the level to High may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly even with the security setting set to High.

Impact of workaround. There are side effects to prompting before running ActiveX Controls and Active Scripting. Many Web sites that are on the Internet or on an intranet use ActiveX or Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX Controls to provide menus, ordering forms, or even account statements. Prompting before running ActiveX Controls or Active Scripting is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run ActiveX Controls or Active Scripting. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone".

How to undo the workaround. In Internet Options, return the slider to your previous setting or click Reset all zones to default level.

Add sites that you trust to the Internet Explorer Trusted sites zone

After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.

To do this, follow these steps:

1.


In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.

2.


In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.

3.


If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.

4.


In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.

5.


Repeat these steps for each site that you want to add to the zone.

6.


Click OK two times to accept the changes and return to Internet Explorer.

Note Add any sites that you trust not to take malicious action on your system. Two in particular that you may want to add are *.windowsupdate.microsoft.com and *.update.microsoft.com. These are the sites that will host the update, and it requires an ActiveX Control to install the update.


Configure Internet Explorer to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone

You can help protect against exploitation of this vulnerability by changing your settings to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone. To do this, follow these steps:

1.


In Internet Explorer, click Internet Options on the Tools menu.

2.


Click the Security tab.

3.


Click Internet, and then click Custom Level.

4.


Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK.

5.


Click Local intranet, and then click Custom Level.

6.


Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK.

7.


Click OK two times to return to Internet Explorer.

Note Disabling Active Scripting in the Internet and Local intranet security zones may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly.

Impact of workaround. There are side effects to prompting before running Active Scripting. Many Web sites that are on the Internet or on an intranet use Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use Active Scripting to provide menus, ordering forms, or even account statements. Prompting before running Active Scripting is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run Active Scripting. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone".

How to undo the workaround. In Security Settings, return to your previous settings or else click Reset.

Add sites that you trust to the Internet Explorer Trusted sites zone

After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.

To do this, follow these steps:

1.


In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.

2.


In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.

3.


If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.

4.


In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.

5.


Repeat these steps for each site that you want to add to the zone.

6.Click OK two times to accept the changes and return to Internet Explorer.

Note Add any sites that you trust not to take malicious action on your system. Two in particular that you may want to add are *.windowsupdate.microsoft.com and *.update.microsoft.com. These are the sites that will host the update, and it requires an ActiveX Control to install the update.
Top of sectionTop of section

FAQ for Microsoft Data Analyzer ActiveX Control Vulnerability - CVE-2010-0252

What is the scope of the vulnerability?
This is a remote code execution vulnerability. 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?
When the ActiveX control is used in Internet Explorer, the control may corrupt the system state in such a way that an attacker could execute arbitrary code.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. 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 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 no way to force users to visit these Web sites. Instead, 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 is the component affected by the vulnerability?
The vulnerability affects the Microsoft Data Analyzer ActiveX control.

What is the Microsoft Data Analyzer ActiveX control?
The Microsoft Data Analyzer ActiveX control allows programmatic control of the Data Analyzer from COM-based development applications such as Microsoft Visual Basic. For more information, see the MSDN article, Exploring Microsoft Data Analyzer Programmability.

What systems are primarily at risk from the vulnerability?
This vulnerability in the Microsoft Data Analyzer ActiveX control requires that a user be logged on and visiting a Web site for any malicious action to occur. Therefore, any systems where the Microsoft Data Analyzer ActiveX control is installed and where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability.

What does the update do?
The update disables the Microsoft ActiveX controls by setting the kill bit for the Class Identifiers hosted in the library files listed below:
Class Identifier File Description

{E0ECA9C3-D669-4EF4-8231-00724ED9288F}


max3activex.dll


Office Excel ActiveX control for Data Analysis

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

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
Top of sectionTop of section
Top of sectionTop of section

Third-Party Kill Bits

This update includes kill bits to prevent the following ActiveX controls from being run in Internet Explorer:


Symantec has requested a kill bit for the ActiveX control for Symantec WinFax Pro 10.3. Please see the post for more information about Symantec's recommendation for customers to set the kill bit for the control. If you have any questions or concerns regarding the kill bit for the Symantec WinFax Pro 10.3 control, please contact Symantec Security at [email protected] The class identifier (CLSID) for this ActiveX control is:


{C05A1FBC-1413-11D1-B05F-00805F4945F6}.


Google has requested a kill bit for the ActiveX control for Google Desktop Gadget v5.8. If you have any questions or concerns regarding Google Desktop Gadget Control v5.8, please contact Google security at [email protected] The class identifier (CLSID) for this ActiveX control is:


{5D80A6D1-B500-47DA-82B8-EB9875F85B4D}.


Facebook has requested a kill bit for the ActiveX control for Facebook Photo Updater 5.5.8. The new control can be found here. If you have any questions or concerns regarding the kill bit for the Facebook Image Uploader ActiveX control, please contact Facebook Security. The class identifier (CLSID) for this ActiveX control is:


{0CCA191D-13A6-4E29-B746-314DEE697D83}.


Panda Security has requested a kill bit for the ActiveX control for PandaActiveScan Installer 2.0. The new control can be found here. If you have any questions or concerns regarding the kill bit for the Panda Security ActiveX control, please contact Panda Security. The class identifier (CLSID) for this ActiveX control is:


{2d8ed06d-3c30-438b-96ae-4d110fdc1fb8}.

Other Information
Acknowledgments

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


Shaun Colley of NGS Software for reporting the Microsoft Data Analyzer ActiveX Control Vulnerability (CVE-2010-0252)
Top of sectionTop of section
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 (February 9, 2010): Bulletin published.

About | Terms of use | Privacy Policy
© SecurityVulns, 3APA3A, Vladimir Dubrovin
Nizhny Novgorod