# CVE-2018-8160: Information disclosure in Microsoft Office

> An attacker can disclose sensitive information when a user opens a malicious message in Microsoft Outlook or Word.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m8vr-j794-rf47

## What is CVE-2018-8160?

CVE-2018-8160 is a medium-severity vulnerability in Microsoft Office, published on 9 May 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An information disclosure vulnerability exists in Outlook when a message is opened, aka "Microsoft Outlook Information Disclosure Vulnerability." This affects Word, Microsoft Office.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2018-8160?

It affects 4 products.


Products: Microsoft Office, Microsoft Office Compatibility Pack, Microsoft Sharepoint Server, Microsoft Web Applications.

## How do I fix CVE-2018-8160?

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

## Is CVE-2018-8160 being exploited?

There is no known exploitation of CVE-2018-8160 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-2018-8160 and fix it if it is affected.

What it is: CVE-2018-8160 is a medium-severity vulnerability in Microsoft Office, published on 9 May 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-8160 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-2018-8160/ (Markdown: https://insights.sbomify.com/CVE-2018-8160/index.md)
```

## Sources

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

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