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

> Remote attackers can execute arbitrary code by tricking users into opening specially crafted email messages in Microsoft Office.

- **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:** 15 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-89rc-8q8r-mfh8

## What is CVE-2017-8507?

CVE-2017-8507 is a high-severity memory corruption vulnerability in Microsoft Outlook, published on 15 Jun 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

A remote code execution vulnerability exists in the way Microsoft Office software parses specially crafted email messages, aka "Microsoft Office Memory Corruption Vulnerability".

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

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

It affects 1 product.


Products: Microsoft Outlook.

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

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

## Is CVE-2017-8507 being exploited?

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

## Other vulnerabilities in Microsoft Outlook

- [CVE-2017-11774](https://insights.sbomify.com/CVE-2017-11774/): Microsoft Office Outlook Security Feature Bypass (high 7.8, exploited in the wild)
- [CVE-2001-0538](https://insights.sbomify.com/CVE-2001-0538/): Code injection in n/a (critical 10.0)
- [CVE-2013-3870](https://insights.sbomify.com/CVE-2013-3870/): Use after free in n/a (critical 9.3)
- [CVE-2010-2728](https://insights.sbomify.com/CVE-2010-2728/): Memory corruption in n/a (critical 9.3)
- [CVE-2010-0266](https://insights.sbomify.com/CVE-2010-0266/): Code injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8507 is a high-severity memory corruption vulnerability in Microsoft Outlook, published on 15 Jun 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-8507 in the wild and no public exploit code.

Affected product: Microsoft Outlook. 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-8507/ (Markdown: https://insights.sbomify.com/CVE-2017-8507/index.md)
```

## Sources

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

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