CVE-2017-11882: Microsoft Office Memory Corruption Vulnerability

CVE-2017-11882 · Severity: critical · CVSS 7.8 · Exploited in the wild · Published 2021-11-03

Microsoft Office contains a memory corruption vulnerability (CWE-119) due to improper handling of objects in memory. An attacker can exploit this to execute arbitrary code in the context of the current user, typically requiring a user to open a specially crafted file.

Technologies: Microsoft Office. Vendors: Microsoft.

Quick answers

Is CVE-2017-11882 exploited in the wild?
Yes. CVE-2017-11882 is known to be exploited in the wild, first recorded on 3 November 2021. Treat it as urgent.
How severe is CVE-2017-11882?
Critical severity, with a CVSS score of 7.8, published 3 November 2021.
Which products and versions are affected?
Microsoft Office 2007 Service Pack 3; Microsoft Office 2010 Service Pack 2; Microsoft Office 2013 Service Pack 1; Microsoft Office 2016.
Is there a fix for CVE-2017-11882?
A patch was published on 2017-11-14: Microsoft released security guidance and patches. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2017-11882 attacked?
It is attacked with local access, in a network appliance.
Am I affected by CVE-2017-11882?
Check whether you run Microsoft Office. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

  • Microsoft Office 2007 Service Pack 3
  • Microsoft Office 2010 Service Pack 2
  • Microsoft Office 2013 Service Pack 1
  • Microsoft Office 2016

Timeline

  • 2017-11-14: patched: Microsoft released security guidance and patches.
  • 2017-11-14: disclosed: Initial public disclosure and advisory publication.
  • 2021-11-03: kev added: Added to CISA's Known Exploited Vulnerabilities Catalog.

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.