# CVE-2018-8245: Code injection in Microsoft Publisher

> Attackers can execute arbitrary code by exploiting improper OLE object instantiation in Microsoft Publisher, requiring user interaction to open a malicious file.

- **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:** 14 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v2hp-7464-6hp5

## What is CVE-2018-8245?

CVE-2018-8245 is a high-severity code injection vulnerability in Microsoft Publisher, published on 14 Jun 2018. 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 when Microsoft Publisher fails to utilize features that lock down the Local Machine zone when instantiating OLE objects, aka "Microsoft Publisher Remote Code Execution Vulnerability." This affects Microsoft Publisher.

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

It affects 1 product.


Products: Microsoft Publisher.

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

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

## Is CVE-2018-8245 being exploited?

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

## Other vulnerabilities in Microsoft Publisher

- [CVE-2013-1318](https://insights.sbomify.com/CVE-2013-1318/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-1319](https://insights.sbomify.com/CVE-2013-1319/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-1320](https://insights.sbomify.com/CVE-2013-1320/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-1322](https://insights.sbomify.com/CVE-2013-1322/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-0102](https://insights.sbomify.com/CVE-2008-0102/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-8245 and fix it if it is affected.

What it is: CVE-2018-8245 is a high-severity code injection vulnerability in Microsoft Publisher, published on 14 Jun 2018. 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-2018-8245 in the wild and no public exploit code.

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

## Sources

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

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