March 9, 2010
Microsoft Excel is prone to a remote code-execution vulnerability. Attackers can exploit this issue by enticing victims into opening a specially crafted Excel ('.xls') file. Successful exploits can allow attackers to execute arbitrary code with the privileges of the user running the application.
- Microsoft Excel 2002
- Microsoft Excel 2002 SP1
- Microsoft Excel 2002 SP2
- Microsoft Excel 2002 SP3
- Microsoft Excel 2003
- Microsoft Excel 2003 SP1
- Microsoft Excel 2003 SP2
- Microsoft Excel 2003 SP3
- Microsoft Excel 2007
- Microsoft Excel 2007 SP1
- Microsoft Excel 2007 SP2
- Microsoft Excel Viewer
- Microsoft Excel Viewer SP1
- Microsoft Excel Viewer SP2
- Microsoft Office 2004 for Mac
- Microsoft Office 2008 for Mac
- Microsoft Office Compatibility Pack 2007
- Microsoft Office Compatibility Pack 2007 SP1
- Microsoft Office Compatibility Pack 2007 SP2
- Microsoft Open XML File Format Converter for Mac
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.
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 accept or execute files from untrusted or unknown sources.
To reduce the likelihood of successful exploits, never handle files that originate from unfamiliar or untrusted sources.
Do not follow links provided by unknown or untrusted sources.
Web users should be cautious about following links to sites that are provided by unfamiliar or suspicious sources. Filtering HTML from emails may help remove a possible vector for transmitting malicious links to users.
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.
The vendor has released an advisory and updates. Please see the references for details.
Sean Larsson of VeriSign iDefense Labs
© 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.