Microsoft Exchange and Active Directory Blog
Microsoft has released new security updates for all Exchange Server versions (2013 - 2019). This time it concerns the vulnerabilities that were successfully used in Pwn2Own 2021 to attack Exchange Server. The following vulnerabilities are fixed: CVE-2021-31209 CVE-2021-31207 CVE-2021-31198 CVE-2021-31195 Here is a description from the Pwn2Own website, presumably exactly this vulnerability is now fixed: The ... Read more
I have just released the new version of the Exchange Reporter. Besides a small bugfix regarding the incorrectly displayed failover time of the databases within a DAG, three new modules are now available. Two of the new modules were contributed by Leslie. Leslie has already found and reported many bugs in the previous versions, so he deserves ... Read more
From time to time it happens that you have to remove an email from your mailbox, for example because it should not have been sent in this way. Experience shows that this often happens with internal newsletters. The question often arises as to whether the mail has already been read, and if so, by how many recipients. With Exchange servers ... Read more
When routing emails in Exchange Hybrid mode, the following error may occur between Exchange on-prem and Microsoft 365 mailboxes when sending mails from a local mailbox (or an external sender) to an M365 mailbox: Remote Server returned '554 5.4.108 SMTPSEND.DNS.MxLoopback; DNS records for the next hop domain are configured in a loop -> ... Read more
Microsoft has released new security updates for all Exchange Server versions (2013 - 2019). These are likely to fix the vulnerabilities that were used in the Pwn2Own 2021 to attack Exchange Server. The following vulnerabilities are fixed: CVE-2021-28483 CVE-2021-28482 CVE-2021-28481 CVE-2021-28480 Here is a description from the Pwn2Own website, probably exactly this ... Read more
A single user was no longer able to access his mailbox after a database failure due to a full log file partition. The problem only affected one user, while all other users were able to access the mailboxes in the database again. A general problem with the database could therefore be ruled out. The settings of the ... Read more
On an Exchange 2016 server that had configured its certificate from Let's Encrypt with the WIN-ACME client, the installation of a CU was aborted with an error at step 16 of 18: Here is the full test of the error message: Error: The following error was generated when "$error.Clear(); Install-ExchangeCertificate -services "IIS, POP, IMAP" -DomainController $RoleDomainController if ($RoleIsDatacenter ... Read more
In the case of successfully attacked Exchange servers with the HAFNIUM exploit, the directory permissions may be changed, resulting in affected Exchange servers reporting an error message when installing updates. Here is an example of a directory where the permissions have been changed: As can be seen in the screenshot, the permissions for the principal ... Read more
The exploit for the Exchange vulnerabilities is now publicly available and, as was to be expected, is spreading even further. Initially, the exploit was blocked on GitHub, which naturally resulted in the exploit being published on various sites. In the meantime, the exploit is also available again on GitHub, only on other ... Read more
Due to the severity of the HAFNIUM exploit, Microsoft has released further updates for older Exchange Server versions. However, the updates cannot be obtained via Windows Update, but must be downloaded and installed manually. Further information on the updates can be found here: March 2021 Exchange Server Security Updates for older Cumulative Updates of Exchange Server Some ... Read more
