March 14, 2006
Microsoft Office is prone to a remote buffer-overflow vulnerability. This vulnerability occurs when the application handles a specially crafted document. A successful attack can result in a remote compromise in the context of an affected user. Update: This issue is known to be exploited in the wild by malware. In particular, 'Trojan.PPDropper' is known to exploit this issue.
- Avaya Modular Messaging (MAS) 3.0.0
- Microsoft Office 2000 SP3
- Microsoft Office 2003 SP1
- Microsoft Office 2003 SP2
- Microsoft Office XP SP3
- Microsoft Works Suite 2000
- Microsoft Works Suite 2001
- Microsoft Works Suite 2002
- Microsoft Works Suite 2003
- Microsoft Works Suite 2004
- Microsoft Works Suite 2005
- Microsoft Works Suite 2006
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.
Users should never accept files from untrusted or unknown sources, because they may be malicious in nature. Avoid opening email attachments from unknown or questionable sources.
Do not follow links provided by unknown or untrusted sources.
Users should avoid websites of questionable integrity. Never follow links supplied by 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 exploitation of memory-corruption vulnerabilities.
Microsoft has released fixes to address this vulnerability in supported versions of the affected software. Avaya has released advisory ASA-2006-069 to identify vulnerable Avaya products. Avaya advises customers to apply patches released by Microsoft. Please see references for more information.
Discovered by Ollie Whitehouse, Symantec.
© 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.