CVE-2017-0281
First published: Fri May 12 2017(Updated: )
Microsoft Office 2007 SP3, Office 2010 SP2, Office 2013 SP1, Office 2016, Office Online Server 2016, Office Web Apps 2010 SP2,Office Web Apps 2013 SP1, Project Server 2013 SP1, SharePoint Enterprise Server 2013 SP1, SharePoint Enterprise Server 2016, SharePoint Foundation 2013 SP1, Sharepoint Server 2010 SP2, Word 2016, and Skype for Business 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-0261 and CVE-2017-0262.
Credit: secure@microsoft.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Microsoft Office | =2007-sp3 | |
| Microsoft Office | =2010-sp2 | |
| Microsoft Office | =2013-sp1 | |
| Microsoft Office | =2016 | |
| Microsoft Office Online Server | =2016 | |
| Microsoft Office Web Apps | =2010-sp2 | |
| Microsoft Office Web Apps | =2013-sp1 | |
| Microsoft Project Server | =2013-sp1 | |
| Microsoft SharePoint Foundation 2013 | =2013-sp1 | |
| Microsoft SharePoint Server 2010 | =2010-sp2 | |
| Microsoft SharePoint Server 2010 | =2013-sp1 | |
| Microsoft SharePoint Server 2010 | =2016 | |
| Microsoft Skype for Business | =2016 | |
| Microsoft Office Word | =2016 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-0281?
CVE-2017-0281 has a severity rating of critical, as it allows remote code execution.
How do I fix CVE-2017-0281?
To fix CVE-2017-0281, you need to apply the relevant security updates released by Microsoft for the affected Office products.
What products are affected by CVE-2017-0281?
CVE-2017-0281 affects various versions of Microsoft Office from 2007 to 2016, as well as Office Online Server and SharePoint.
Can CVE-2017-0281 be exploited by attackers?
Yes, CVE-2017-0281 can be exploited by attackers through maliciously crafted Office documents.
Is there a workaround for CVE-2017-0281?
While there is no official workaround for CVE-2017-0281, users are advised to be cautious with unsolicited Office documents.
- agent/references
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/author
- agent/last-modified-date
- agent/remedy
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/microsoft
- canonical/microsoft office
- version/microsoft office/2007-sp3
- version/microsoft office/2010-sp2
- version/microsoft office/2013-sp1
- version/microsoft office/2016
- canonical/microsoft office online server
- version/microsoft office online server/2016
- canonical/microsoft office web apps
- version/microsoft office web apps/2010-sp2
- version/microsoft office web apps/2013-sp1
- canonical/microsoft project server
- version/microsoft project server/2013-sp1
- canonical/microsoft sharepoint foundation 2013
- version/microsoft sharepoint foundation 2013/2013-sp1
- canonical/microsoft sharepoint server 2010
- version/microsoft sharepoint server 2010/2010-sp2
- version/microsoft sharepoint server 2010/2013-sp1
- version/microsoft sharepoint server 2010/2016
- canonical/microsoft skype for business
- version/microsoft skype for business/2016
- canonical/microsoft office word
- version/microsoft office word/2016