April 12, 2005
Microsoft Word is prone to a buffer overflow vulnerability. This issue presents itself when Microsoft Word attempts to parse a malformed document. This could result in execution of arbitrary code in the context of a user who opens the malicious document. Internet Explorer is a likely attack vector as Word may be opened to handle the document when the user clicks a link. This issue was originally described as part of BID 11350.
- Microsoft Word 2000
- Microsoft Word 2000 Chinese Version
- Microsoft Word 2000 Japanese Version
- Microsoft Word 2000 Korean Version
- Microsoft Word 2000 SP2
- Microsoft Word 2000 SP3
- Microsoft Word 2000 SR1
- Microsoft Word 2000 SR1a
- Microsoft Word 2002
- Microsoft Word 2002 SP1
- Microsoft Word 2002 SP2
- Microsoft Word 2002 SP3
- Microsoft Word 2003
- Microsoft Word 2003 Viewer
- Microsoft Works Suite 2001
- Microsoft Works Suite 2002
- Microsoft Works Suite 2003
- Microsoft Works Suite 2004
Do not accept or execute files from untrusted or unknown sources.
Users should be wary of opening any files that originate from an untrusted or unfamiliar source.
Run all software as a nonprivileged user with minimal access rights.
Running the affected application as a user with minimal access rights may greatly prove to help mitigate the impact of successful exploitation.
Microsoft has released updates to address this issue in supported versions of affected software. UPDATE: Fixes are available for Microsoft Word 2003 Viewer.
Discovery is credited to Alex Li.
© 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.