CVE-2017-0261High

Microsoft security update for CVE-2017-0261 — Microsoft Office

Published
May 9, 2017
Last Modified
—

🔗 CVE IDs covered (1)

CVE-2017-0261 →

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2017-0261. This page also shows what EchelonGraph holds for CVE-2017-0261, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products6

  • Microsoft Office 2010 Service Pack 2 (32-bit editions)
  • Microsoft Office 2010 Service Pack 2 (64-bit editions)
  • Microsoft Office 2013 Service Pack 1 (32-bit editions)
  • Microsoft Office 2013 Service Pack 1 (64-bit editions)
  • Microsoft Office 2016 (32-bit edition)
  • Microsoft Office 2016 (64-bit edition)

✅ Updates Microsoft lists: 6 updates

6 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update—
—Security Update—
—Security Update—
—Security Update—
—Security Update—
—Security Update—

🧭 EchelonGraph on CVE-2017-0261

EchelonGraph score
9.0 CRITICAL
CISA KEV
Listed since March 3, 2022
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

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.

Published by Microsoft Corporation, the CVE Numbering Authority that assigned CVE-2017-0261, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (7)