CVE-2020-16875 is a remote code execution vulnerability in Microsoft Exchange Server caused by improper validation of cmdlet arguments. The flaw is exposed through Exchange functionality associated with Data Loss Prevention management and Exchange Control Panel operations. An authenticated attacker who has, or can obtain, an account assigned to the required Exchange role can supply crafted cmdlet arguments that are processed unsafely, resulting in arbitrary code execution on the Exchange server. Successful exploitation executes code in the security context of NT AUTHORITY\SYSTEM.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Microsoft Exchange Server remote code execution vulnerability in the Data Loss Prevention component exposed through ECP, allowing authenticated attackers with DLP privileges to execute arbitrary code as SYSTEM.
Specific vulnerability listed in the content with severity Critical.
Specific named vulnerability listed in the content; no product or technical description is provided beyond severity/date and tabular flags.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.