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

> Remote attackers can execute arbitrary code via crafted PowerPoint files due to improper memory handling in Microsoft PowerPoint for Mac.

- **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:** 5 Aug 2024
- **Also known as:** GHSA-xxpr-8m4r-4fgq

## What is CVE-2017-0264?

CVE-2017-0264 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 PowerPoint for Mac 2011 allows a remote code execution vulnerability when the software fails to properly handle objects in memory, aka "Microsoft Office Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-0254 and CVE-2017-0265.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Microsoft Powerpoint for Mac.

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

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

## Is CVE-2017-0264 being exploited?

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

## Other vulnerabilities in Microsoft Office

- [CVE-2017-0265](https://insights.sbomify.com/CVE-2017-0265/): Memory corruption in Microsoft Office (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-0264 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-0264 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-0264/ (Markdown: https://insights.sbomify.com/CVE-2017-0264/index.md)
```

## Sources

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

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