atlas by clearpeople

Exchange Server patch alert - Action if you have Exchange on-prem

3 March 2021
  

Current risks to multiple different on-premises Microsoft Exchange Servers where zero-day vulnerabilities are being exploited by a nation-state affiliated group. Please note that EXCHANGE ONLINE is not affected.

Our colleagues at Microsoft have reached out to make sure as many Microsoft customers as possible are made aware of the current risks to multiple different on-premises Microsoft Exchange Servers where zero-day vulnerabilities are being exploited by a nation-state affiliated group. Please note that EXCHANGE ONLINE is not affected.
 
Please check this video describing the issue.
 
Please read the full details below provided directly by Microsoft:
 

Team ClearPeople,

 I am contacting you to alert you to Microsoft’s release of patches for multiple different on-premises Microsoft Exchange Server zero-day vulnerabilities that are being exploited by a nation-state affiliated group.

 The vulnerabilities exist in on-premises Exchange Servers 2010, 2013, 2016, and 2019.  Exchange Online is not affected. We wanted to ensure you were aware of the situation and would ask that you help drive immediate remediation steps.

 Specifically, to minimize or avoid impacts of this situation, Microsoft highly recommends that you take immediate action to apply the patches for any on-premises Exchange deployments you have or are managing for a customer or advise your customer of the steps they need to take. The first priority being servers which are accessible from the Internet (e.g., servers publishing Outlook on the web/OWA and ECP). 

 To patch these vulnerabilities, you should move to the latest Exchange Cumulative Updates and then install the relevant security updates on each Exchange Server. 

  • You can use the Exchange Server Health Checker script, which can be downloaded from GitHub (use the latest release).
  • Running this script will tell you if you are behind on your on-premises Exchange Server updates (note that the script does not support Exchange Server 2010). 
  • We also recommend that your security team assess whether or not the vulnerabilities were being exploited by using the Indicators of Compromise we shared here.

Additional resources:

 

Author bio

Patrick Proesmans

Patrick Proesmans

As Head of Success I’m responsible for all activities related to the full customer success journey. We want to provide our clients the best possible customer experience and meet customer expectations. When I’m not working I try to keep the weeds out of my garden and to enjoy the Spanish sun in the Alicante area.

View all articles by this author View all articles by this author

Get our latest posts in your inbox