March brings us a stable set of updates from Microsoft for Windows, Microsoft Office, Exchange, and Edge (Chromium), however no crucial points requiring a “Patch Now” launch schedule (although Microsoft Exchange would require some technical effort this month). We have revealed some testing pointers, with a concentrate on printing, distant desktop over VPN connections, and server-based networking adjustments. We additionally advocate testing your Windows installer packages with a selected concentrate on roll-back and uninstall performance. You can discover extra details about the chance of deploying these Patch Tuesday updates with this handy infographic. And, if you’re searching for extra data on .NET updates, there’s a nice publish from Microsoft that highlights this month’s adjustments.Key testing eventualitiesThere was at the least one high-risk reported change to the Windows platform for March. We have included the next tough testing pointers primarily based on our evaluation of the modified recordsdata and contents of this month’s Windows and Office updates:
(High Risk): Test your networked printers over the Remote Desktop Protocol (RDP). Microsoft has not revealed any practical adjustments for this month’s replace as modifications are on account of safety considerations.
V4 Printer Driver, print utilizing distant, and community primarily based redirected printer(s).
Test your backup and restore processes when utilizing Encrypted Files Systems (EFS).
Validate that your VPNs authenticate appropriately over the Point-to-Point tunnelling protocol (PPTP).
Test your Windows Error reporting processes with Create/Read/Update/Delete (CRUD) for all log recordsdata.
Locate software references to NtAlpcCreatePort in your Windows servers and validate your software outcomes.
If you have got time, it could be price testing UNC paths to DOS packing containers (on account of a number of adjustments to the networking and authentication stack). There’s additionally been an replace to the FastFAT system driver and the way End User Defined Characters (EUDC) are dealt with. Microsoft has now included deployment and reboot necessities for this March 2022 replace in a single web page.Known pointsEach month, Microsoft features a checklist of recognized points that relate to the working system and platforms included on this cycle. There is greater than regular this time, so I’ve referenced a couple of key points that relate to the newest builds from Microsoft, together with:
After putting in this replace, when connecting to units in an untrusted area utilizing Remote Desktop, connections would possibly fail to authenticate when utilizing good card authentication. You would possibly obtain the immediate, “Your credentials did not work.” Like final month, Microsoft has launched various GPO recordsdata that resolve this situation, together with: Windows Server 2022 and Windows 10.
After putting in updates launched Jan. 11 or later, functions that use the Microsoft .NET Framework to accumulate or set Active Directory Forest Trust Information utilizing the System.DirectoryServers API could fail or generate an error message.
There was an impressive situation from January’s replace cycle the place the executable DWM.EXE crashes after putting in KB5010386. This situation has now been resolved. If you might be searching for extra knowledge on a majority of these reported points, one nice useful resource from Microsoft is the Health Center — particularly, you will discover out about Windows 10 and Windows 11 recognized points and their present standing. Major revisionsThough there’s a a lot smaller checklist of patches for this patch cycle, Microsoft launched a number of revisions to earlier patches, together with:
CVE-2021-3711: This is a Visual Studio replace from November 2021. A brand new model has been up to date to incorporate assist for the newest variations of Visual Studio 2022. No further actions are required.
CVE-2021-36927: This up to date patch addresses a TV Tuner codec situation in 2021. Microsoft has helpfully revealed an up to date documentation set for this, noting that the repair is now official and totally resolves the reported situation. No additional actions required.
Mitigations and workaroundsThis month, Microsoft has not revealed any mitigations or workarounds for the Windows, Microsoft Office, browser or improvement platform updates and patches. There is an ongoing checklist of mitigations and updates associated to recognized points for Microsoft Exchange (they’re included in our Exchange-related part). Each month, we break down the replace cycle into product households (as outlined by Microsoft) with the next primary groupings:
Browsers (Microsoft IE and Edge);
Microsoft Windows (each desktop and server);
Microsoft Development platforms ( ASP.NET Core, .NET Core and Chakra Core);
Adobe (retired???, perhaps subsequent 12 months).
BrowsersFollowing a pattern set by Microsoft over the previous few months, solely the Chromium Edge browser has been up to date. With no crucial updates, and 21 reported vulnerabilities rated as necessary by Microsoft, that is one other simple replace cycle. Other than working via potential points with the Brotli compression engine, you need to be capable of deploy the browser updates in your regular launch schedule.WindowsFollowing the pattern of fewer (in quantity and in nature) updates this month, Microsoft launched simply two crucial updates (CVE-2022-22006 and CVE-2022-24501). Neither replace is prone to have an effect on core platforms as every patches a singular video codec and a Microsoft Store element. The remaining 40 patches are all rated as necessary by Microsoft and replace the next core Windows parts:
Remote Desktop shopper (RDP);
Windows Error log (this has been up to date each month this 12 months);
Networking (SMB and PTPTP);
Windows Update and Windows Installer.
You could wish to add a Windows Installer take a look at to your testing regime this month. Add these Windows updates to your normal launch schedule. Microsoft OfficeIf you had been ever searching for a “low-risk” patch profile for Microsoft Office, this month’s updates are an excellent candidate. Microsoft has launched six patches to Office, all of that are rated as necessary. Most importantly, they both have an effect on Skype (which isn’t so necessary) or the “Click to Run” (CTR) set up of Office. The CTR model is the virtualized, self-contained model of the Office set up that’s streamed right down to the goal system. By design, these installations have little to no impact on the working system and given the character of the adjustments made this month, there’s little or no deployment danger. Add these Office updates to your normal deployment schedule.Microsoft Exchange ServerLastly, a crucial vulnerability from Microsoft. No…, wait! Darn, it is for Exchange. Microsoft Exchange is within the dangerous books this month with one of many few critical-rated vulnerabilities (CVE-2022-23277). Of the 2 Exchange-related patches for March, the opposite (CVE-2022-24463) is rated as necessary and will result in a possible credential spoofing state of affairs. The crucial situation is rated as extremely prone to be exploited, however does require that the attacker is authenticated. This is just not a “worm-able” vulnerability, so we advocate you add the Microsoft Exchange updates to your normal server deployment. This replace would require a reboot to your servers. There have been a number of revealed points with latest Microsoft Exchange updates, and so we have now included an inventory of recognized points when updating your Exchange Servers, together with:
When you attempt to manually set up this safety replace by double-clicking the replace file (.MSP) to run it in Normal mode (that’s, not as an administrator), some recordsdata are usually not appropriately up to date.
Exchange providers would possibly stay in a disabled state after you put in this safety replace. To resolve this situation, begin the replace course of as an Administrator.
When you block third-party cookies in an online browser, you may be regularly prompted to belief a selected add-in, although you retain choosing the choice to belief it.
When you attempt to request free/busy data for a person in a distinct forest in a trusted cross-forest topology, the request fails and generates a “(400) Bad Request” error message.
Copyright © 2022 IDG Communications, Inc.