February 14, 2007
Microsoft Excel is prone to a remote code-execution vulnerability. Attackers may exploit this issue by enticing victims into opening a maliciously crafted Excel file (.xls). Successful exploits may allow attackers to execute arbitrary code with the privileges of the user running the application. This may facilitate a compromise of vulnerable computers. This issue was previously reported as a denial-of-service vulnerability, but has been updated to reflect new information.
- Avaya CIE 1.0
- Avaya CIE 1.0.2
- Avaya Customer Interaction Express (CIE) User Interface 1.0
- Avaya Customer Interaction Express (CIE) User Interface 1.0.2
- 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 Office 2004 for Mac
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 refrain from accepting and executing files that originate from unknown or untrusted sources.
Implement multiple redundant layers of security.
Since this issue may be leveraged to execute code, we recommend memory-protection schemes, such as non-executable stack/heap configurations and randomly mapped memory segments. This tactic may complicate exploits of memory-corruption vulnerabilities.
Microsoft released an advisory and fixes to address this issue. Please see the references for more information.
SehaTo is credited with the discovery of this vulnerability.
© 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 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.