September 14, 2010
Microsoft Outlook is prone to a remote heap-based buffer-overflow vulnerability because it fails to properly validate user-supplied data.
Attackers can exploit this issue by enticing an unsuspecting user to preview or view a crafted email message.
Successfully exploiting this issue will allow an attacker to execute arbitrary code with the privileges of the currently logged-in user. Failed exploit attempts will result in a denial-of-service condition.
- Microsoft Outlook 2002
- Microsoft Outlook 2002 SP1
- Microsoft Outlook 2002 SP2
- Microsoft Outlook 2002 SP3
- Microsoft Outlook 2003
- Microsoft Outlook 2003 SP2
- Microsoft Outlook 2003 SP3
- Microsoft Outlook 2007
- Microsoft Outlook 2007 SP1
- Microsoft Outlook 2007 SP2
Block external access at the network boundary, unless external parties require service.
Filter access to the affected computer at the network boundary if global access isn't needed. Restricting access to only trusted computers and networks might greatly reduce the likelihood of a successful exploit.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of anomalous or suspicious activity. This may indicate exploit attempts or activity that results from successful exploits.
When possible, limit the privileges granted to users to the least amount required.
To reduce the impact of latent vulnerabilities, limit user privileges to the least amount possible. This can help prevent privileged functions from running.
Do not open email messages from unknown or untrusted individuals.
Do not accept emails from untrusted sources.
Updates are available; please see the references for more information.
Dyon Balding of Secunia
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 firstname.lastname@example.org
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 email@example.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.