Skip to Content

MC400168: Hardening changes coming 07/2022: Smart card authentication might cause print and scan failures

On July 13, 2021: Microsoft released hardening changes for Windows Key Distribution Center Information Disclosure Vulnerability, CVE-2021-33764. With these changes, smart card (PIV) authentication might cause print and scan failures when you install updates released on July 13, 2021, or later versions on a domain controller (DC). The affected devices are smart card authenticating printers, scanners, and multifunction devices that don’t support either Diffie-Hellman (DH) for key exchange during PKINIT Kerberos authentication or don’t advertise support for des-ede3-cbc (“triple DES”) during the Kerberos AS request.

A temporary mitigation, released in Windows Updates between July 29, 2021, and July 12, 2022, was made available for organizations that encountered this issue and couldn’t bring devices into compliance as required for CVE-2021-33764. However, starting in July 2022, this temporary mitigation will not be usable in security updates. The Windows July 2022 preview update will remove the temporary mitigation and will require compliant printing and scanning devices.

When will this happen

All non-compliant devices must be identified using the audit events starting January 2022 and updated or replaced by the mitigation removal starting on July 19, 2022. Refer to the timeline below to understand the last hardening changes for CVE-2021-33764.

July 19, 2022: Optional preview update release to remove temporary mitigation to require compliant printing and scanning devices in your environment on Windows Server 2019.

August 9, 2022: All updates released on this day or later will be unable to use the temporary mitigation on Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 SP1, Windows Server 2008 SP2.

How this will affect your organization

All temporary mitigation for this scenario will be removed on July 19, 2022, and August 9, 2022, depending on the version of Windows that you are using. There will be no further fallback option in later updates.

After 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.

What you need to do to prepare

You must have your non-compliant devices updated and compliant, or replaced by July 19, 2022, when the temporary mitigation will not be usable in security updates.

Additional information

It is important to ensure that you have your non-compliant devices updated and compliant or replaced. Review the below documentation:

Message ID: MC400168
Created: 14 July 2022
Updated: 15 July 2022
Action required by: 19 July 2022
Platform: World tenant

    Ads Blocker Image Powered by Code Help Pro

    It looks like you are using an adblocker.

    Ads keep our content free. Please consider supporting us by allowing ads on