Date Discovered February 10, 2009
Description Microsoft Visio is prone to a remote code-execution vulnerability because it fails to adequately handle user-supplied data.
Attackers can exploit this issue to execute arbitrary code in the context of the user running the application. Failed exploit attempts will result in a denial-of-service condition.
- Microsoft Visio 2002
- Microsoft Visio 2002 Professional SP2
- Microsoft Visio 2002 SP1
- Microsoft Visio 2002 SP2
- Microsoft Visio 2002 Standard SP2
- Microsoft Visio 2003
- Microsoft Visio 2003 SP1
- Microsoft Visio 2003 Professional
- Microsoft Visio 2003 SP2
- Microsoft Visio 2003 SP3
- Microsoft Visio 2003 Standard
- Microsoft Visio 2007
- Microsoft Visio 2007 SP1
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.
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.
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 exploit attempts of memory-corruption vulnerabilities.
The vendor has released an advisory and fixes. Please see the references for more information.
Credits Bing Liu of Fortinet's FortiGuard Global Security Research Team
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.