KB5014747 is the monthly rollup update for Windows Server 2012 released on the 14th of June. This update replaces or supersedes the KB5014017 monthly rollup update for the month of May. It also covers the changes that were brought about in the emergency OOB or out-of-band update KB5014991 released on 19th May 2022. We bring the key aspects of KB5014747 for your ready reference below.
- Salient points about KB5014747 for Windows Server 2012
- KB5014747 – Vulnerabilities resolved on Windows Server 2012
- Prerequisites for installing KB5014747 on Windows Server 2012
- How can I deploy KB5014747 on Windows Server 2012?
Salient points about KB5014747 for Windows Server 2012
- KB5014747 is a cumulative security update that supersedes KB5014017 and the OOB update KB5014991.
- OOB KB5014991 was released to resolve authentication issues on Windows Server 2012 domain controllers after installing the KB5014017 or KB5014018 updates.
- If you did not deploy the KB5014991 OOB update on Windows Server 2012, you can skip it and instead install KB5014747 directly on Windows Server 2012.
- CVE-2022-30163, CVE-2022-30139, and CVE-2022-30190 are important vulnerabilities that need to be mitigated or patched on Windows Server 2012.
- SSU KB5014027 must be deployed on Windows Server 2012 before installing KB5014747.
- To prevent machine certificate authentication issues, the cumulative updates need to be deployed on application servers before the domain controllers.
- The size of the update file for KB5014747 is 407.4 MB.
KB5014017 Monthly Rollup Update for Windows Server 2012 – May 10 2022
KB5014747 – Vulnerabilities resolved on Windows Server 2012
There is a zero-day vulnerability and other critical vulnerabilities on Windows Server 2012. There have been a total of 60 vulnerability disclosures as part of Microsoft’s security updates for June. Some of these do affect Windows Server 2012.
CVE-2022-30190 – Windows System Diagnostic Tool
- CVE-2022-30190 is a zero-day vulnerability that can lead to remote code execution. It is publicly disclosed and is being exploited.
- The vulnerability lies in Microsoft’s Windows System Diagnostic Tool.
- The CVSS rating for CVE-2022-30190 is 7.8.
- The fix lies in patching Windows Server 2012 with KB5014747 or KB5014741.
- Or, you can disable MSDT URL Protocol as per instructions given on Microsoft’s blog.
CVE-2022-30136 – Windows Network File System
- CVE-2022-30136 is a critical vulnerability with a CVSS rating of 9.8.
- The vulnerability could lead to remote code execution attacks.
- The security risk lies in Windows Network File System version 4.1 Network File System 2 and Network File System version 3 are unaffected by CVE-2022-30136.
- You can apply KB5014747 or KB5014741 to resolve the threat.
- Alternatively, you can mitigate the risk by disabling the NFS version 4.1. However, this will have an impact on the network services and it is recommended to plan the change in detail.
CVE-2022-30163 – Windows Hyper V
- CVE-2022-30163 is a critical vulnerability with a CVSS rating of 8.5. It could lead to remote code execution.
- The attack complexity for CVE-2022-30163 is complex. But, the problem lies in the kind of low-level access that gets compromised through the threat.
- The vulnerability allows an attacker to assume low-level access to the Hyper V host operating system.
- Once the attacker controls the Hyper V operating system, he can deploy malicious code on the server and cause remote code execution threats.
- The vulnerability can be resolved by patching KB5014747 or KB5014741 on Windows Server 2012.
Prerequisites for installing KB5014747 on Windows Server 2012
- SSU KB5014027 needs to be deployed on Windows Server 2012 prior to installing KB5014747 monthly rollup update. You can download the KB5014027 SSU through the Microsoft Update Catalog page for KB5014027. The size of the update file is 9.7 MB.
- To prevent machine certificate authentication issues, it is suggested by Microsoft to install KB5014747 monthly rollup updates on application servers that pass authentication certificates on the network. Once the non-domain controllers are patched, you can roll out the KB5014747 to the domain controllers.
- An alternate approach to preventing machine certificate authentication issues is to set the CertificateMappingMethods to 0x1F through the registry editor. Deploy KB5014747 after creating this registry entry. Once KB5014747 has been deployed, you can remove the entry under CertificateMappingMethods. You can read more about this method on the KB5014754 page on Microsoft site.
How can I deploy KB5014747 on Windows Server 2012?
Monthly rollup KB5014747 is available for deployment through all the regular means of Windows Update.
- KB5014747 can be deployed through Windows Update.
- KB5014747 can also be deployed through Microsoft Update for Business.
- WSUS can be used to import and deploy KB5014747 on Windows Server 2012.
- You can deploy KB5014747 manually through the Microsoft Catalog Update. KB5014747 can be downloaded through the Microsoft Update Catalog page for KB5014747. The size of the update file is 407.4 MB.
KB5014747 monthly rollup update for Windows Server 2012 can be deployed on the server through all the regular Windows Update channels. KB5014027 SSU should be installed prior to installing KB5014747. Also, do remember that KB5014747 is a cumulative update and replaces KB5014017 and KB5014991.
You may also like to read the content related to Windows Updates for the month of June 2022:
- KB5014678 Cumulative Update for Windows Server 2022
- KB5014692 Cumulative Update for Windows Server 2019
- KB5014702 Cumulative Update for Windows Server 2016 – June 2022
- KB5014741 Security Update for Windows Server 2012
- KB5014746 Security Update for Windows Server 2012 R2
We are sorry that this post was not useful for you!
Let us improve this post!
Tell us how we can improve this post?
Rajesh Dhawan is a technology professional who loves to blog about smart wearables, Cloud computing and Microsoft technologies. He loves to break complex problems into manageable chunks of meaningful information.