Microsoft Office RTF File Stack Buffer Overflow Vulnerability

2010-11-09T00:00:00
ID SMNTC-44652
Type symantec
Reporter Symantec Security Response
Modified 2010-11-09T00:00:00

Description

Description

Microsoft Office is prone to a remote stack-based buffer-overflow vulnerability because the software fails to perform adequate boundary checks on user-supplied data. An attacker can exploit this issue by enticing a victim to open a malicious RTF file or view an email in RTF format. Successfully exploiting this issue would allow the attacker to corrupt memory and execute arbitrary code in the context of the currently logged-in user. Failed exploit attempts will result in a denial-of-service condition.

Technologies Affected

  • Microsoft Office 2003
  • Microsoft Office 2003 SP1
  • Microsoft Office 2003 SP2
  • Microsoft Office 2004 for Mac
  • Microsoft Office 2007
  • Microsoft Office 2007 SP1
  • Microsoft Office 2007 SP2
  • Microsoft Office 2008 for Mac
  • Microsoft Office 2010 (32-bit edition)
  • Microsoft Office 2010 (64-bit edition)
  • Microsoft Office 2010
  • Microsoft Office 2011 for Mac
  • Microsoft Office XP
  • Microsoft Office XP SP1
  • Microsoft Office XP SP2
  • Microsoft Office XP SP3
  • Microsoft Open XML File Format Converter for Mac

Recommendations

Run all software as a nonprivileged user with minimal access rights.
To mitigate the impact of a successful exploit, run the affected application as a 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.
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 accept communications that originate from unknown or untrusted sources.
Do not accept or preview emails that come from unknown or unsolicited locations.

Implement multiple redundant layers of security.
Since this issue may be leveraged to execute code, we recommend memory-protection schemes, such as nonexecutable stack/heap configurations and randomly mapped memory segments. This tactic may complicate exploit attempts of memory-corruption vulnerabilities.

The vendor has released an advisory and updates. Please see the references for more information.