CVE-2017-11882

Microsoft Office Memory Corruption Vulnerability

CVE-2017-11882 is fixed in 7 products on 1 platform, first by KB4011604, released November 21, 2017. It is being exploited: CISA added it to the Known Exploited Vulnerabilities catalog on November 3, 2021, with known ransomware use. Patch Radar priority: Patch now.

Patch nowCISA KEVKnown ransomware use
CVSS
n/a
Important
Exploitation
Exploited
Listed by CISA
CISA KEV
Nov 3, 2021
Federal due date May 3, 2022. Known ransomware use
EPSS
0.9995
99th percentile

<p>A remote code execution vulnerability exists in Microsoft Office software when the software fails to properly handle objects in memory. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.</p> <p>Exploitation of the vulnerability requires that a user open a specially crafted file with an affected version of Microsoft Office or Microsoft WordPad software. In an email attack scenario, an attacker could exploit the vulnerability by sending the specially crafted file to the user and convincing the user to open the file. In a web-based attack scenario, an attacker could host a website (or leverage a compromised website that accepts or hosts user-provided content) containing a specially crafted file designed to exploit the vulnerability. An attacker would have no way to force users to visit the website. Instead, an attacker would have to convince users to click a link, typically by way of an enticement in an email or instant message, and then convince them to open the specially crafted file.</p> <p>The security update addresses the vulnerability by correcting how the affected Office component handles objects in memory.</p>

Where it's fixed

ProductFixed inFixReleased
Microsoft
Microsoft Office 2007 Service Pack 3 KB4011604 Nov 21, 2017
Microsoft Office 2010 Service Pack 2 (32-bit editions) KB4011618 Nov 21, 2017
Microsoft Office 2010 Service Pack 2 (64-bit editions) KB4011618 Nov 21, 2017
Microsoft Office 2013 Service Pack 1 (32-bit editions) KB3162047 Nov 21, 2017
Microsoft Office 2013 Service Pack 1 (64-bit editions) KB3162047 Nov 21, 2017
Microsoft Office 2016 (32-bit edition) KB4011262 Nov 21, 2017
Microsoft Office 2016 (64-bit edition) KB4011262 Nov 21, 2017