Date Discovered January 9, 2007
Description Microsoft Excel is prone to a remote code-execution vulnerability.
An attacker can exploit this issue to execute arbitrary code with the privileges of the user running the affected application, which can result in the compromise of affected computers.
- Microsoft Excel
- Microsoft Excel 2000
- Microsoft Excel 2000 SP2
- Microsoft Excel 2000 SP3
- 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 2004 for Mac
- Microsoft Excel Viewer 2003
- Microsoft Excel x for Mac
- Microsoft Office 2000
- Microsoft Office 2000 SP1
- Microsoft Office 2000 SP2
- Microsoft Office 2000 SP3
- Microsoft Office 2003
- Microsoft Office 2003 SP1
- Microsoft Office 2003 SP2
- Microsoft Office XP
- Microsoft Office XP SP1
- Microsoft Office XP SP2
- Microsoft Office XP SP3
- Microsoft Works Suite 2004
- Microsoft Works Suite 2005
- Microsoft Works Suite 2006
Run all software as a nonprivileged user with minimal access rights. To reduce the impact of latent vulnerabilities, always run non-administrative software as an unprivileged user with minimal access rights.
Do not accept or execute files from untrusted or unknown sources.
Users should not accept or execute files from unknown or untrusted sources.
Microsoft has released a fix to address this issue. Please see the references for more information.
Update: Microsoft has re-released MS07-002 to resolve a regression with the original Excel 2000 fixes when dealing with files created when in Korean, Chinese, or Japanese executable modes. Please see the knowledge base article (KB931183) for more information.
Credits Greg MacManus of IDefense Labs discovered this issue.
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.