Cyber risk and advisory programs that identify security gaps and build strategies to address them.
MDR that provides improved detection, 24/7 threat hunting, end-to-end coverage and most of all, complete Response.
Our team delivers the fastest response time in the industry. Threat suppression within just 4 hours of being engaged.
Be protected by the best from Day 1.
24/7 Threat Investigation and Response.
Expert hunting, research and content.
Defend brute force attacks, active intrusions and unauthorized scans.
Protect assets from ransomware, trojans, rootkits and more.
Intelligence and visibility across AWS, O365, DevOps and more.
Configuration escalations, policy and posture management.
Detects malicious insider behavior leveraging Machine Learning models.
On September 10th, researcher Steven Seeley publicly released Proof-of-Concept (PoC) code for a critical remote code execution vulnerability he discovered affecting Microsoft Exchange Servers 2016 and 2019 (CVE-2020-16875). This vulnerability was originally announced by Microsoft on September 8th . Successful exploitation would result in execution of arbitrary code in the context of the SYSTEM user, allowing an attacker to view, change, and delete data, or create new accounts on the impacted system.
In order to exploit this vulnerability, an attacker would require credentials belonging to accounts in a specific Exchange role. Although eSentire assesses that widespread exploitation of this vulnerability remains unlikely, affected organizations are advised to prioritize applying the relevant patches to remediate this threat as part of a defense in depth strategy.
What we’re doing about it
What you should do about it
Steven Seeley (mr_me), the researcher who disclosed the vulnerability to Microsoft, authored two PoC exploits for the vulnerability. An advisory was posted on the srcincite.io website on September 10th, 2020, containing the PoCs and additional information on the vulnerability . According to the advisory, the “flaw exists within the processing of the New-DlpPolicy cmdlet. The issue results from the lack of proper validation of user-supplied template data when creating a dlp policy”. Mr. Seeley also confirms that credentials belonging to a user with a specific Exchange role (DLP Role) are required to successfully exploit this vulnerability.
Requirements for exploitation for both PoC exploits:
PowerShell PoC Exploit
Python PoC Exploit
Given the above conditions for successful exploitation, eSentire assesses that widespread exploitation of this vulnerability is unlikely. The vulnerability is more likely to be exploited post-compromise, as part of an ongoing intrusion where an attacker has obtained the necessary requirements for exploitation.