![]() ![]() If there is currently no way to bring your devices into compliance with section 3.2.1 of RFC 4556 specification as required for CVE-2021-33764, a temporary mitigation is now available while you work with your printing or scanning device manufacturer to bring your environment into compliance within the timeline below. Important You must have your noncompliant devices updated and compliant or replaced by July 12, 2022, when the temporary mitigation will not be usable in security updates. ![]() Important NoticeĪll temporary mitigation for this scenario will be removed in July 2022 and August 2022, depending on the version of Windows that you are using (see table below). ![]() There will be no further fallback option in later updates. All noncompliant devices must be identified using the audit events starting January 2022 and updated or replaced by the mitigation removal starting in late July 2022.Īfter July 2022, devices which are not compliant with the RFC 4456 specification and CVE-2021-33764 will not be usable with an updated Windows device. Updates released with hardening changes for CVE-2021-33764. All later updates have this hardening change on by default. Updates released with temporary mitigation to address printing and scanning issues on noncompliant devices. Updates released on this date or later must be installed on you DC and the mitigation must be turned on through registry key using the steps below. Updates released with temporary mitigation to address printing and scanning issues on noncompliant devices. Updates release on this date or later must be installed on you DC and the mitigation must be turned on through registry key using the steps below. Updates will log audit events on Active Directory domain controllers that identify printers that are RFC-4456 incompatible printers that fail authentication once DCs install the July 2022/August 2022 or later updates. Optional preview update release to remove temporary mitigation to require complaint printing and scanning devices in your environment. ![]()
0 Comments
Leave a Reply. |