Microsoft Office Smart Tag Remote Code Execution Vulnerability

2006-10-10T00:00:00
ID SMNTC-20320
Type symantec
Reporter Symantec Security Response
Modified 2006-10-10T00:00:00

Description

Description

Microsoft Office is prone to a remote code-execution vulnerability. This issue occurs when Office attempts to process malformed files. An attacker could exploit this issue by enticing a victim to load a malicious Office file. If the vulnerability is successfully exploited, this could result in the execution of arbitrary code in the context of the currently logged-in user.

Technologies Affected

  • Microsoft Office 2003 SP1
  • Microsoft Office 2003 SP2
  • Microsoft Office XP SP1
  • Microsoft Office XP SP2
  • Microsoft Office XP SP3
  • Microsoft Project 2002
  • Microsoft Project 2002 SP1
  • Microsoft Project 2002 SP2
  • Microsoft Visio 2002 SP1
  • Microsoft Visio 2002 SP2

Recommendations

Run all software as a nonprivileged user with minimal access rights.
Ensure that all non-administrative tasks are performed 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 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 a security advisory addressing this issue.