Important 2018-03 archive

Executive Summary

A remote code execution vulnerability exists in Microsoft Office software when the Office 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. Exploitation of the vulnerability requires that a user open a specially crafted file with an affected version of Microsoft Office 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) that contains 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. Note that the Preview Pane is not an attack vector for this vulnerability. The security update addresses the vulnerability by correcting how Office handles objects in memory.

Overview

Important
MS Severity
Not Exploited
MS Exploit Status
N/A
MS Exploit Likelihood
Category Remote Code Execution
Released Mar 13 2018
Last Updated Mar 13 2018
Publicly Disclosed No
CISA KEV Not Listed
Known Exploits None Known

EPSS Score

No EPSS score available for this CVE.

View on FIRST.org

Affected Products

15 affected products
Product KB Article Severity Impact Restart Required
Microsoft Office 2010 Service Pack 2 (32-bit editions) 4011673 (Security Update) Important Remote Code Execution Maybe
Microsoft Office 2010 Service Pack 2 (64-bit editions) 4011673 (Security Update) Important Remote Code Execution Maybe
Microsoft Office Compatibility Pack Service Pack 3 4011720 (Security Update) Important Remote Code Execution Maybe
Microsoft Office Online Server 2016 4011023 (Security Update) Important Remote Code Execution Maybe
Microsoft Office Web Apps 2010 Service Pack 2 4011709 (Security Update) Important Remote Code Execution Maybe
Microsoft Office Web Apps 2013 Service Pack 1 4011692 (Security Update) Important Remote Code Execution Maybe
Microsoft Office Word Viewer 4018309 (Security Update) Important Remote Code Execution Maybe
Microsoft SharePoint Enterprise Server 2013 Service Pack 1 4011688 (Security Update) Important Remote Code Execution Maybe
Microsoft SharePoint Server 2010 Service Pack 2 4011705 (Security Update) Important Remote Code Execution Maybe
Microsoft Word 2007 Service Pack 3 4011721 (Security Update) Important Remote Code Execution Maybe
Microsoft Word 2010 Service Pack 2 (32-bit editions) 4011674 (Security Update) Important Remote Code Execution Maybe
Microsoft Word 2010 Service Pack 2 (64-bit editions) 4011674 (Security Update) Important Remote Code Execution Maybe
Microsoft Word 2013 (32-bit editions) 4011695 (Security Update) Important Remote Code Execution Maybe
Microsoft Word 2013 (64-bit editions) 4011695 (Security Update) Important Remote Code Execution Maybe
Microsoft Word 2013 RT Service Pack 1 4011695 (Security Update) Important Remote Code Execution Maybe

Patches

11 patches
Article Type Restart
4011673 Security Update Maybe
4011720 Security Update Maybe
4011023 Security Update Maybe
4011709 Security Update Maybe
4011692 Security Update Maybe
4018309 Security Update Maybe
4011688 Security Update Maybe
4011705 Security Update Maybe
4011721 Security Update Maybe
4011674 Security Update Maybe
4011695 Security Update Maybe

Known Exploits

Acknowledgments

Wayne Low of Fortinet’s FortiGuard Lab