March 24, 2010
Microsoft Data Access Components are prone to a remote memory-corruption vulnerability. An attacker can exploit this issue by enticing an unsuspecting user to view a malicious webpage. Successful exploits will allow the attacker to execute arbitrary code within the context of the application. Failed exploit attempts will result in a denial-of-service condition. NOTE: This issue was originally reported at the 2010 CanSecWest conference as part of the Pwn2Own contest. It was also previously documented in BID 38951 (Microsoft Internet Explorer Unspecified Remote Code Execution Vulnerabilities) but has been moved here to better document it.
- Avaya Aura Conferencing 6.0 Standard
- Avaya CallPilot 4.0
- Avaya CallPilot 5.0
- Avaya Communication Server 1000 Telephony Manager 3.0
- Avaya Communication Server 1000 Telephony Manager 4.0
- Avaya Meeting Exchange - Client Registration Server
- Avaya Meeting Exchange - Recording Server
- Avaya Meeting Exchange - Streaming Server
- Avaya Meeting Exchange - Web Conferencing Server
- Avaya Meeting Exchange - Webportal
- Avaya Meeting Exchange 5.0
- Avaya Meeting Exchange 5.0 SP1
- Avaya Meeting Exchange 5.0 SP2
- Avaya Meeting Exchange 126.96.36.199.52
- Avaya Meeting Exchange 5.1
- Avaya Meeting Exchange 5.1 SP1
- Avaya Meeting Exchange 5.2
- Avaya Meeting Exchange 5.2 SP1
- Avaya Meeting Exchange 5.2 SP2
- Avaya Messaging Application Server 4
- Avaya Messaging Application Server 5
- Avaya Messaging Application Server 5.2
- Microsoft Data Access Components (MDAC) 2.8
- Microsoft Data Access Components (MDAC) 2.8 SP1
- Microsoft Data Access Components (MDAC) 2.8 SP2
- Microsoft Internet Explorer 8
- Microsoft Windows Data Access Components 6.0
Run all software as a nonprivileged user with minimal access rights.
To reduce the impact of latent vulnerabilities, always run nonadministrative software as an unprivileged user with minimal access rights.
Do not follow links provided by unknown or untrusted sources.
Attackers could exploit this vulnerability by enticing a user to visit a malicious website. Do not follow links provided by sources of questionable integrity.
Set web browser security to disable the execution of script code or active content.
Disable support for script code and active content within a client browser to reduce the chances of a successful exploit. Note that this mitigation tactic might adversely affect legitimate websites that rely on the execution of browser-based script code.
Implement multiple redundant layers of security.
Since this issue may be leveraged to execute code, we recommend memory-protection schemes, such as nonexecutable stack/heap configurations and randomly mapped memory segments. This tactic may complicate exploits of memory-corruption vulnerabilities.
Vendor updates are available. Please see the references for more information.
- TechTarget - Apple iPhone, Microsoft IE 8 get hacked in Pwn2Own contest
- cnet - iPhone, Safari, IE 8, Firefox hacked in CanSecWest contest
- Microsoft - Microsoft Homepage
- Peter Vreugdenhil - MS11-002 Pwn2Own heap overflow
- TippingPoint - Pwn2Own 2010
- Peter Vreugdenhil - Pwn2Own 2010 Windows 7 Internet Explorer 8 exploit
Peter Vreugdenhil, working with TippingPoint's Zero Day Initiative
© 1995- Symantec Corporation
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from email@example.com.
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and firstname.lastname@example.org are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.