CVE-2017-11882 Microsoft Office Memory Corruption

Exploited in the wild High 7.8 Published Updated

Attackers can execute arbitrary code by exploiting a memory corruption flaw in Microsoft Office applications.

Exploited in the wild
Since 3 Nov 2021
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
A user has to click or open something
Fix
None listed

What is CVE-2017-11882?

CVE-2017-11882 is a high-severity memory corruption vulnerability in Microsoft Office, published on 15 Nov 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

Official description

Microsoft Office 2007 Service Pack 3, Microsoft Office 2010 Service Pack 2, Microsoft Office 2013 Service Pack 1, and Microsoft Office 2016 allow an attacker to run arbitrary code in the context of the current user by failing to properly handle objects in memory, aka "Microsoft Office Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-11884.

Weakness: CWE-119

Which versions are affected by CVE-2017-11882?

It affects 1 product.

Products include Microsoft Office.

How do I fix CVE-2017-11882?

No fix has been published for CVE-2017-11882 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2017-11882 being exploited?

Yes. Attackers have exploited CVE-2017-11882 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

Public exploit code: 1 Metasploit module, 1 Exploit-DB entry and 36 proofs of concept on GitHub.

All Microsoft Office vulnerabilities

Sources

Also known as GHSA-vjph-m3mp-rqj5.

Is CVE-2017-11882 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free