Risk
High
Date Discovered
July 6, 2009
Description
The Microsoft Active Template Library (ATL) is prone to a remote code-execution vulnerability.
This issue affects a private version of the ATL used internally by Microsoft; components written by other vendors are likely unaffected.
Remote attackers can exploit this issue to execute arbitrary code with the privileges of the user running an application built against the affected library. Failed exploit attempts will result in a denial-of-service condition.
NOTE: This BID was previously titled "Microsoft Windows 'MPEG2TuneRequest' ActiveX Control Remote Code Execution Vulnerability". It has been updated to better reflect the issue.
Recommendations
Run all software as a nonprivileged user with minimal access rights.
To mitigate the impact of a successful exploit, run the affected application as a user with minimal access rights.Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of suspicious or anomalous activity. This may help detect malicious actions that an attacker may take after successfully exploiting vulnerabilities in applications. Review all applicable logs regularly.Do not follow links provided by unknown or untrusted sources.
Never accept files or follow links from untrusted or unknown sources, because they may be malicious in nature.Set web browser security to disable the execution of script code or active content.
To limit exposure to these issues, disable support for client-side scripting and active content. This is especially prudent for untrusted sites in the Internet Zone.
Vendor advisories and updates are available. Please see the references for details.
Credits
This issue was discovered in the wild. This issue was independently discovered by Ryan Smith and Alex Wheeler with IBM ISS X-Force.
Copyright © 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
secure@symantec.com.
Disclaimer
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
secure@symantec.com 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.
