CVE-2015-1641 vulnerability in Microsoft Products
Published on April 14, 2015

Microsoft Word 2007 SP3, Office 2010 SP2, Word 2010 SP2, Word 2013 SP1, Word 2013 RT SP1, Word for Mac 2011, Office Compatibility Pack SP3, Word Automation Services on SharePoint Server 2010 SP2 and 2013 SP1, and Office Web Apps Server 2010 SP2 and 2013 SP1 allow remote attackers to execute arbitrary code via a crafted RTF document, aka "Microsoft Office Memory Corruption Vulnerability."

Vendor Advisory NVD

Known Exploited Vulnerability

This Microsoft Office Memory Corruption vulnerability is part of CISA's list of Known Exploited Vulnerabilities. Allows remote attackers to execute arbitrary code via a crafted RTF document, aka "Microsoft Office Memory Corruption Vulnerability.".

The following remediation steps are recommended / required by May 3, 2022: Apply updates per vendor instructions.

Vulnerability Analysis

CVE-2015-1641 can be exploited with local system access, requires user interaction. This vulnerability is considered to have a low attack complexity. It has an exploitability score of 1.8 out of four. The potential impact of an exploit of this vulnerability is considered to be very high.

What is a Memory Corruption Vulnerability?

The software writes data past the end, or before the beginning, of the intended buffer. Typically, this can result in corruption of data, a crash, or code execution. The software may modify an index or perform pointer arithmetic that references a memory location that is outside of the boundaries of the buffer. A subsequent write operation then produces undefined or unexpected results.

CVE-2015-1641 has been classified to as a Memory Corruption vulnerability or weakness.

Products Associated with CVE-2015-1641

You can be notified by stack.watch whenever vulnerabilities like CVE-2015-1641 are published in these products:

Microsoft Word

Microsoft Office Web Apps

Microsoft Outlook

Microsoft Office Compatibility Pack

Microsoft Sharepoint Server

Microsoft Office

What versions are vulnerable to CVE-2015-1641?