You cannot apply the update for Exchange 2019 CU9 to Exchange 2019 CU8.

Running cmdlets against EMC using invoked runspace might result in no-language mode error ( info).īe advised that these security updates are Cumulative Update level specific.

Cross-forest Free/Busy might stop working resulting in 400 Bad Request ( solution).

Accounts ending in ‘$’ cannot use EMS or access the ECP.

The blog also mentions some issues, which are identical to the ones mentioned with the May 2021 Security Updates: You you need to separate the update from deploying the update, see end of article for a tip. After deploying the SU, from an elevated CMD prompt, run Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms from Exchange’s bin folder.

When you are running Exchange 2013 CU23 in your organization, and no later Exchange builds are present, you need to deploy a schema update immediately after deploying the Security Update.

When running n-1 CU of Exchange 2019 (CU9) or Exchange 2016 (CU20), and you do not plan to upgrade to the latest CU yet but do wish to install this Security Update, you must also update the AD Schema using the CU10 or CU21 installation files.

More detailed information can be found at the original blog post here, which mentions some specific post-deployment instructions:

CVE-2021-34470 is only addressed in the security update for Exchange 2013 CU23.

CVE-2021-33768 does not seem applicable to Exchange 2019 CU9 or Exchange 2016 CU20.

Vulnerabilities mentioned in the table above are addressed in the following security updates: Exchange

CVE-2021-31206 was the vulnerability discovered at the Pwn2Own 2021 contest.

However, as far as I can see CVE-2021-34473, CVE-2021-34523 and CVE-2021-33766 were addressed in the April 2021 and eventually the May 2021 Security Updates, which also would explain MSRC’s mention of earlier CUs, such as Exchange 2019 CU8.

When looking at the MSRC information, you will notice 3 additional CVE issues addressed for July 13th.

The vulnerabilities addressed in these security updates are: Vulnerability

Update July 20th: Added VC++2012 requirement to tip on running MT to prepare Exchange 2013 schema separately.Īnother month, another Patch Tuesday! A quick blog on the July’s security updates for Exchange Server 2013 up to 2019.

Exchange 2013 owa