Patch Tuesday will get off to a busy begin for January
For the primary Patch Tuesday of 2022, Microsoft supplied up fixes for 97 safety points, with six of them rated as important.
Microsoft / IDG
For this week’s Patch Tuesday, the primary of the 12 months, Microsoft addressed 97 safety points, six of them rated important. Though six vulnerabilities have been publicly reported, I don’t classify them as zero-days. Microsoft has mounted numerous safety associated points and is conscious of a number of recognized points that will have inadvertently triggered vital server points together with:
- Hyper-V, which now not begins with the message, “Virtual machine xxx couldn’t be began as a result of the hypervisor is just not operating.”
- ReFS (Resilient) file methods which might be now not accessible (which is type of ironic).
- And Windows area controller boot loops.
There are quite a lot of recognized points this month, and I’m unsure whether or not we’ll see extra points reported with the January server patches. You can discover extra info on the danger of deploying these newest updates with our useful infographic.
Key testing eventualities
There are not any reported high-risk adjustments to the Windows platform this month. However, there’s one reported practical change, and a further characteristic added.
- Test native and distant printing and take a look at printing over RDP.
- Test site-to-site VPN, together with new and present connections.
- Test studying or processing ETL recordsdata.
- Check beginning and stopping Hyper-V in your servers.
- Run Transactional NTFS (TxF) and CLFS take a look at eventualities whereas together with assessments for ReFS file I/O transfers.
Known points
Each month, Microsoft features a checklist of recognized points that relate to the working system and platforms included on this replace cycle. I’ve referenced just a few key points that relate to the corporate’s newest builds, together with:
- SharePoint Server: Most customers can not entry Web.config recordsdata in SharePoint Server. The affected group of customers doesn’t embody farm directors, native directors, or members who’re managed by the system. For extra info, see Users can not entry Web.config recordsdata in SharePoint Server (KB5010126).
- After putting in the June 21, 2021 (KB5003690) replace, some gadgets can not set up new ones, such because the July 6, 2021 (KB5004945) or later updates. You will obtain the error message, “PSFX_E_MATCHING_BINARY_MISSING.” For extra info and a workaround, see KB5005322.
- After putting in updates launched April 22, 2021 or later, a problem happens that impacts variations of Windows Server getting used as a Key Management Services (KMS) host. Client gadgets operating Windows 10 Enterprise LTSC 2019 and Windows 10 Enterprise LTSC 2016 may fail to activate. This challenge solely happens when utilizing a brand new Customer Support Volume Licence Key (CSVLK). Microsoft is engaged on a decision and can present an replace in an upcoming launch.
- After putting in this Windows replace, when connecting to gadgets in an untrusted area utilizing Remote Desktop, connections may fail to authenticate when utilizing sensible card authentication. You may obtain the immediate, “Your credentials didn’t work. The credentials that had been used to hook up with [device name] didn’t work. Please enter new credentials” and “The login try failed” in pink. This challenge is resolved utilizing Known Issue Rollback (KIR). For basic info on utilizing Group Policies, see Group Policy Overview; we now have listed the next group coverage set up recordsdata within the occasion {that a} KIR process is required: Windows Server 2022; Windows 10, model 2004; Windows 10, model 20H2; and Windows 10, model 21H1.
- After putting in KB4493509, gadgets with some Asian language packs put in may even see the error, “0x800f0982 – PSFX_E_MATCHING_COMPONENT_NOT_FOUND.
- After putting in Windows 11, some picture modifying packages won’t render colours accurately on sure excessive dynamic vary (HDR) shows.
Microsoft is engaged on the Windows 11 points, however has but to reply to the Hyper-V, ReFS, or Domain Controller issues. One of one of the best methods to see whether or not recognized points may have an effect on your goal platform is to take a look at the numerous configuration choices for downloading patch knowledge on the Microsoft Security Update steerage web site or the abstract web page for this month’s safety replace.
Major revisions
Microsoft has not launched any main revisions (or minor documentation adjustments) for the January Patch launch.
Mitigations and workarounds
Although there are not any printed mitigations or workarounds referring to the January patches, we count on a response from Microsoft to the Server 2022 patch-related points inside the subsequent few days.
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 Office;
- Microsoft Exchange;
- Microsoft Development platforms ( ASP.NET Core, .NET Core and Chakra Core);
- Adobe (retired???, possibly subsequent 12 months).
Browsers
This month sees a blended bag of updates for Microsoft browsers. Though we do not get any patches for the legacy browsers, Microsoft has launched 5 updates which might be particular to the Chromium model of Edge. In addition to those adjustments, the Chromium challenge has launched an additional 24 updates to the Chromium browser core. You can discover extra details about the Microsoft updates right here, with the discharge notes for the Chromium challenge updates discovered right here. Microsoft has printed detailed info on the Microsoft Edge-specific points (discovered within the Security Update Guide) whereas Google refrains from publishing detailed safety and vulnerability info till all patches are launched.
Add these Chrome (Edge and Chromium) updates to your common scheduled replace launch schedule.
Windows
This is a big replace to the Windows platform with seven updates rated important, and a hefty 80 patches rated as essential. There at the moment are a number of reported points with this month’s server patches affecting (most likely all) Windows area controllers. If you might be seeing the next error message put up replace — “The system course of ‘C:Windowssystem32lsass.exe’ terminated unexpectedly with standing code -1073741819. The system will now shut down and restart.” — you aren’t alone. There are additionally vital numbers of stories that digital machines on just lately up to date Hyper-V don’t begin.
Normally, we might advocate a big testing cycle earlier than a manufacturing launch of Windows updates. However this month’s replace addresses CVE-2022-21907 “which is a very harmful CVE due to its means to permit for an attacker to have an effect on a whole intranet as soon as the assault succeeds”, stated Danny Kim, principal architect at Virsec. The CVE is the newest instance of how software program capabilities might be warped and weaponized; it targets the HTTP trailer help characteristic, which permits a sender to incorporate further fields in a message to provide metadata by offering a specifically crafted message that may result in distant code execution.
Microsoft says this vulnerability is “wormable” so we advocate that you just add this month’s Windows replace to your “Patch Now” schedule.
Windows Testing Guidelines
- Test your IME with each English and Asian language packs.
- Remote Desktop: A consumer ought to be capable to hook up with the RDP host and be capable to redirect drives, audio, clipboard and to printers.
- Test CLFS Logs: (“CRUD”) Create a log, learn from a log, and replace a log.
- Networking: Send and obtain giant measurement recordsdata to different nodes utilizing IPv4 and IPv6.
- Test NTFS utilizing quick identify associated eventualities.
This month’s Windows patches included a significant replace to NTFS (with no practical adjustments); for extra info and prompt testing eventualities, seek advice from the Microsoft doc Transactional NTFS (TxF).
Microsoft Office
Microsoft has launched 4 updates for the venerable Office productiveness suite (one rated important, the remaining three, essential). The important patch (CVE-2022-21840) addresses a distant code execution vulnerability within the Microsoft Core libraries that (fortunately) requires person interplay resembling the next state of affairs by Microsoft: “In an electronic mail assault state of affairs, an attacker may exploit the vulnerability by sending the specifically crafted file to the person and convincing the person to open the file.” So, it is 2022 and by clicking on an electronic mail, we are able to simply give all of it away.
Microsoft has confirmed that these 4 patches absolutely deal with the problem, so please add this replace to your customary Office patch launch schedule.
Microsoft Exchange Server
There are three updates to the Microsoft Exchange Server platform this month. With two rated as essential (CVE-2022-21969 and CVE-2022-21855), the main focus ought to be on the important patch CVE-2022-21846. This vulnerability has a really excessive CVSS score of 9.0. However, the danger of exploitation is far decreased because of the propagation nature of this vulnerabilities’ assault vector. To achieve success, an attacker have to be current on the community or in a position to entry an adjoining part on the goal system (resembling Bluetooth).
Microsoft supplied the next testing pointers for these three patches, which embody:
- Test OWA eventualities with http and (safe) https URLs.
- Test new Exchange “site mailbox” creation(s).
Fortunately, we aren’t anticipating the difficult configuration points this month that we have seen in previous updates. So, “take a look at earlier than deploy” and add these Exchange updates to your customary server replace schedule.
Microsoft improvement platforms
For this cycle, Microsoft launched a single replace (CVE-2022-21911) rated as essential for its improvement platforms. This denial-of-service assault doesn’t require person interplay or admin privileges to reach compromising a goal system. Microsoft has printed an official repair for the problem, which can have an effect on .NET COM servers and REGEX expressions. These parts will want some testing earlier than deployment of the singular .NET replace. You can also need to obtain these and future updates in a separate file for .NET 4.8 patches.
Microsoft has printed a weblog on .NET 4.8 launch cadences and methodologies. Add this replace to your common patch launch schedule.
Adobe (actually simply Reader)
It’s again with a vengeance! Adobe has printed so many vulnerabilities for its Adobe Reader (and Acrobat) merchandise, I initially thought that the lengthy checklist of reminiscence associated points addressed the complete Adobe suite.
Nope.
Adobe Reader has seen at least 26 updates, with 15 rated important, three as essential, and one other seven as reasonable. All variations are affected, and all at the moment supported platforms would require an replace. You can learn extra about this (very) lengthy checklist of updates right here. Add these Adobe updates to your “Patch Now” schedule.