October 10, 2006
Microsoft Word for Mac is prone to a remote code-execution vulnerability when parsing Word files. Exploiting this vulnerability may allow an attacker to execute arbitrary machine code in the context of the user who opened the file. An attacker could leverage this issue to gain the permissions of an unsuspecting user. A successful exploit could result in the remote compromise of the affected system.
- Microsoft Word 2004 for Mac
- Microsoft Word X for Mac
Audit the system and limit, or remove, access to setuid or setgid utilities.
To reduce the impact of vulnerabilities, always run non-administrative 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 includes but is not limited to requests that include NOP sleds and unexplained incoming and outgoing traffic. This may indicate exploit attempts or activity that results from successful exploits.
Do not accept or execute files from untrusted or unknown sources.
Web users should be cautious about files that are provided by unfamiliar or suspicious sources. This can greatly reduce the likelihood of successful exploit attempts.
Do not open email messages from unknown or untrusted individuals.
Users should not open email messages sent from unknown or untrusted sources. This can greatly reduce the likelihood of successful exploit attempts.
Microsoft has released fixes to address this issue. Please see the references for information on how to obtain and apply these fixes.
Microsoft credits Cu Fang 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.