Microsoft Office XP HTML Link Processing Remote Buffer Overflow Vulnerability



Date Discovered

February 8, 2005


A remote buffer overflow vulnerability affects Microsoft Office XP. The problem presents itself when an unsuspecting user follows a malicious HTML link that points to a Office document. A boundary condition error is exposed during this operation that may allow attacker-specified data to corrupt process memory. An attacker may leverage this issue to execute arbitrary code with the privileges of an unsuspecting user that follows a malicious embedded link.

Technologies Affected

  • Microsoft Office XP
  • Microsoft Office XP SP1
  • Microsoft Office XP SP2
  • Microsoft Office XP SP3
  • Microsoft PowerPoint 2002 SP1
  • Microsoft PowerPoint 2002
  • Microsoft PowerPoint 2002 SP2
  • Microsoft PowerPoint 2002 SP3
  • Microsoft Project 2002
  • Microsoft Project 2002 SP1
  • Microsoft Visio 2002
  • Microsoft Visio 2002 Professional SP2
  • Microsoft Visio 2002 SP1
  • Microsoft Visio 2002 SP2
  • Microsoft Visio 2002 Standard SP2
  • Microsoft Word 2002
  • Microsoft Word 2002 SP1
  • Microsoft Word 2002 SP2
  • Microsoft Word 2002 SP3
  • Microsoft Works Suite 2002
  • Microsoft Works Suite 2003
  • Microsoft Works Suite 2004


Do not accept or execute files from untrusted or unknown sources.
Refusing to open Office documents originating from potentially malicious sources will greatly reduce exposure to this issue.

Do not follow links provided by unknown or untrusted sources.
As exploitation of this issue requires an unsuspecting user to follow a malicious link, it is advised that users exercise extreme caution when following links provided by individuals or groups of questionable legitimacy.

Run all software as a nonprivileged user with minimal access rights.
Non-administrative software should always be run as an unprivileged user with minimal access rights to reduce the impact of latent vulnerabilities.

Microsoft has released updates to address this issue.



"Rafel Ivgi" <> is credited with the discovery of this issue.

© 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


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 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.