Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 7.8 CISA Known Exploited Vulnerability

CVE-2017-0261

Microsoft Office Use-After-Free Vulnerability

Microsoft Office

Microsoft Office 2010 SP2, Office 2013 SP1, and Office 2016 allow a remote code execution vulnerability when the software fails to properly handle objects in memory, aka "Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-0262 and CVE-2017-0281.

CVSS
7.8
HIGH
EPSS
78.1%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
12 May 2017
CWE-416

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 3 March 2022. US federal agencies were required to remediate it by 24 March 2022.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 78.1%, which is higher than 99.6% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2017-0261 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2017-0261.

What does CVE-2017-0261 affect?

CVE-2017-0261 affects Microsoft Office. Microsoft Office 2010 SP2, Office 2013 SP1, and Office 2016 allow a remote code execution vulnerability when the software fails to properly handle objects in memory, aka "Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-0262 and CVE-2017-0281.

How severe is CVE-2017-0261?

CVE-2017-0261 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 78.1%, higher than 99.6% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 24 March 2022.

How should organisations respond to CVE-2017-0261?

Apply the vendor patch for Microsoft Office as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.