CVE-2016-7193: Microsoft Office Memory Corruption Vulnerability

CVE-2016-7193 · Severity: critical · CVSS 7.8 · Exploited in the wild · Published 2022-03-03

A memory corruption vulnerability in Microsoft Office and Word allows remote attackers to execute arbitrary code via a specially crafted RTF document. The flaw stems from improper restriction of operations within the bounds of a memory buffer.

Technologies: Microsoft Office. Vendors: Microsoft.

Quick answers

Is CVE-2016-7193 exploited in the wild?
Yes. CVE-2016-7193 is known to be exploited in the wild, first recorded on 3 March 2022. Treat it as urgent.
How severe is CVE-2016-7193?
Critical severity, with a CVSS score of 7.8, published 3 March 2022.
Which products and versions are affected?
Microsoft Word 2007 SP2; Microsoft Office 2010 SP2; Microsoft Word 2013 SP1; Microsoft Word 2013 RT SP1; and 10 more.
Is there a fix for CVE-2016-7193?
A patch was published on 2016-10-11: Microsoft released security bulletin MS16-121 to address the vulnerability. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2016-7193 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-7193?
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 Word 2007 SP2
  • Microsoft Office 2010 SP2
  • Microsoft Word 2013 SP1
  • Microsoft Word 2013 RT SP1
  • Microsoft Word 2016
  • Microsoft Word for Mac 2011
  • Microsoft Word 2016 for Mac
  • Microsoft Office Compatibility Pack SP3
  • Microsoft Word Viewer
  • Microsoft Word Automation Services on SharePoint Server 2010 SP2
  • Microsoft Word Automation Services on SharePoint Server 2013 SP1
  • Microsoft Office Web Apps 2010 SP2
  • Microsoft Office Web Apps Server 2013 SP1
  • Microsoft Office Online Server

Timeline

  • 2016-10-11: patched: Microsoft released security bulletin MS16-121 to address the vulnerability.
  • 2022-03-03: kev added: CISA added this vulnerability to the Known Exploited Vulnerabilities (KEV) catalog.
  • 2022-03-03: disclosed

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