# CVE-2017-0281: Memory corruption in Microsoft Office

> Attackers can execute arbitrary code by exploiting improper memory object handling in Microsoft Office applications.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 May 2017
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-gq33-m2fg-cpvh

## What is CVE-2017-0281?

CVE-2017-0281 is a high-severity memory corruption vulnerability in Microsoft Office, published on 12 May 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

## Which versions are affected by CVE-2017-0281?

It affects 8 products.


Products: Microsoft Office, Microsoft Office Online Server, Microsoft Office Web Apps, Microsoft Project Server, Microsoft Sharepoint Foundation, Microsoft Sharepoint Server, Microsoft Skype for Business, Microsoft Word.

## How do I fix CVE-2017-0281?

No fix has been published for CVE-2017-0281 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-0281 being exploited?

There is no known exploitation of CVE-2017-0281 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft Office

- [CVE-2018-0798](https://insights.sbomify.com/CVE-2018-0798/): Microsoft Office Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2015-1770](https://insights.sbomify.com/CVE-2015-1770/): Microsoft Office Uninitialized Memory Use (high 8.8, exploited in the wild)
- [CVE-2006-2492](https://insights.sbomify.com/CVE-2006-2492/): Microsoft Word Malformed Object Pointer (high 8.8, exploited in the wild)
- [CVE-2018-0802](https://insights.sbomify.com/CVE-2018-0802/): Microsoft Office Memory Corruption (high 7.8, exploited in the wild)
- [CVE-2017-11882](https://insights.sbomify.com/CVE-2017-11882/): Microsoft Office Memory Corruption (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-0281 and fix it if it is affected.

What it is: CVE-2017-0281 is a high-severity memory corruption vulnerability in Microsoft Office, published on 12 May 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-0281 in the wild and no public exploit code.

Affected product: Microsoft Office. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-0281/ (Markdown: https://insights.sbomify.com/CVE-2017-0281/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-0281
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-0281
- OSV: https://osv.dev/vulnerability/CVE-2017-0281

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-0281/
Summaries are generated and may contain mistakes; the official description above is the record.