May 8, 2007
Microsoft Excel is prone to a remote code-execution vulnerability.
An attacker can exploit this issue to execute arbitrary code in the context of a victim user running the application. A successful exploit will result in the compromise of the application and may aid in further attacks.
- Avaya CIE 1.0
- 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 2003 SP3
- Microsoft Excel 2004 for Mac
- Microsoft Excel 2007
- Microsoft Excel Viewer 2003
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 anomalous or suspicious activity. This may indicate exploit attempts or activity that results from successful exploits.
Do not accept or execute files from untrusted or unknown sources.
To reduce the likelihood of successful attacks, users should never accept or execute files provided by untrusted and unknown individuals.
Microsoft has released a security advisory and fixes to address this issue. Please see the references for more information.
KB934233 has been updated to inform users of a potential problem with the installation of fixes. Fixes may not have been successfully installed if either Microsoft Update or Microsoft Windows Server Update Services were used to install fixes on Microsoft Vista computers running Office 2007. Please see the references for more information about this issue.
The vendor disclosed 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 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.