[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
iDefense Security Advisory 08.10.10: Microsoft Office RTF Parsing Engine Memory Corruption Vulnerability
iDefense Security Advisory 08.10.10
Aug 10, 2010
Microsoft Word is a word processing application from Microsoft Office.
For more information about Microsoft Word, see the following website:
Rich-Text Format (RTF) is a document file format developed by Microsoft
for cross-platform document interchange.
Remote exploitation of an memory corruption vulnerability in Microsoft's
Office RTF Parsing Engine could allow an attacker to execute arbitrary
code with the privileges of the current user.
During the processing of a RTF document containing certain control
words, the RTF parsing engine may incorrectly read a value from the RTF
file. This value may directly affect the control of execution flow
within the RTF parsing engine.
Exploitation of this vulnerability results in the execution of arbitrary
code with the privileges of the user who opened a malicious RTF document
with Microsoft Office.
To exploit this vulnerability, a targeted user must load a malicious RTF
file created by an attacker, or simply receive an email containing
malicious RTF content. An attacker typically accomplishes this via
social engineering or injecting content into a compromised, trusted
iDefense has confirmed the existence of this vulnerability in Microsoft
Word 2003, Microsoft Word 2007, and Microsoft Outlook 2007. A full list
of vulnerable Microsoft products can be found in Microsoft Security
Microsoft suggested workarounds can be found in Microsoft Security
VI. VENDOR RESPONSE
Microsoft Corp. has released patches which address this issue.
Information about downloadable vendor updates can be found by clicking
on the URLs shown.
VII. CVE INFORMATION
The Common Vulnerabilities and Exposures (CVE) project has assigned the
name CVE-2010-1901 to this issue. This is a candidate for inclusion in
the CVE list (http://cve.mitre.org/), which standardizes names for
VIII. DISCLOSURE TIMELINE
08/11/2009 Initial Vendor Notification
08/11/2009 Initial Vendor Reply
08/10/2010 Coordinated Public Disclosure
This vulnerability was reported to iDefense by wushi of team509.
Get paid for vulnerability research
Free tools, research and upcoming events
X. LEGAL NOTICES
Copyright © 2010 iDefense, Inc.
Permission is granted for the redistribution of this alert
electronically. It may not be edited in any way without the express
written consent of iDefense. If you wish to reprint the whole or any
part of this alert in any other medium other than electronically,
please e-mail customerservice@xxxxxxxxxxxx for permission.
Disclaimer: 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.