![](\"https:\/\/images.idgesg.net\/images\/article\/2020\/07\/conceptual_representation_of_technical_support_fixes_service_maintenance_updates_digital_sign_wrench_screwdriver_branching_circuits_throughout_system_by_traitov_gettyimages-1199145131_cso_nw_2400x1600-100853236-large.3x2.jpg?auto=webp&quality=85,70\"\/)
<\/p>\n
Credit to Author: Greg Lambert| Date: Fri, 17 Jun 2022 12:09:00 -0700<\/strong><\/p>\n June’s Patch Tuesday updates, released on June 14, address 55 vulnerabilities in Windows, SQL Server, Microsoft Office, and Visual Studio (though there are oo Microsoft Exchange Server or Adobe updates this month). And a zero-day vulnerability in a key Windows component,<\/span> CVE-2022-30190<\/span><\/a>, led to a \u201cPatch Now\u201d recommendation for Windows, while the .NET, Office and SQL Server updates can be included in a standard release schedule. <\/span><\/p>\n You can find more information on the risk of deploying these Patch Tuesday updates in this infographic<\/a><\/span>.<\/span><\/p>\n Given the large number of changes included in this June patch cycle I have broken out the testing scenarios for high risk and standard risk groups.<\/span><\/p>\n These high-risk changes are likely to include functionality changes, may deprecate existing functions, and will likely require new testing plans.\u00a0<\/span>Test your signed drivers using physical and virtual machines, (BIOS and UEFI) and across all platforms (x86, 64-bit):<\/span><\/p>\n Each of these high-risk test cycles must include a manual shut-down, reboot, and restart. The following changes are not documented as including functional changes, but will still require at least “<\/span>smoke testing<\/span><\/a>” before general deployment:<\/span><\/p>\n In addition to these standard testing guidelines, we recommend that all core applications undergo a testing regime that includes self-repair, uninstall, and update. This is due to the changes to Windows Installer (MSI) this month. Not enough IT departments test the update, repair, and uninstall functions of their application portfolio. It’s good to challenge each application package as part of the Quality Assurance (QA) process that includes the key application lifecycle stages of installation, activation, update, repair, and then uninstall. <\/span><\/p>\n Not testing these stages could leave IT systems in an undesirable state \u2014 at the very least, it will be an unknown state.<\/span><\/p>\n Each month, Microsoft includes a list of known issues that relate to the operating system and platforms affected this cycle. This month, there are some complex changes to consider, including:<\/span><\/p>\n As you may be aware, Microsoft published an<\/span> out-of-band update<\/span><\/a> (OOB) last month (on May 19). This update affected the following core Windows Server based networking features:<\/span><\/p>\n The security vulnerabilities addressed by this OOB update only affects servers operating as domain controllers and application servers that authenticate to domain controller servers. Desktop platforms are not affected. Due to this earlier patch, Microsoft has recommended that<\/span>\u00a0this June’s update be installed on all intermediate or application servers that pass authentication certificates from authenticated clients to the domain controller (DC) first. Then install this update on all DC role computers. Or pre-populate <\/span>CertificateMappingMethods<\/strong> to <\/span>0x1F<\/strong> as documented in the<\/span> registry key information<\/span><\/a> section of <\/span>KB5014754<\/span><\/a> on all DCs. Delete the <\/span>CertificateMappingMethods<\/strong> registry setting <\/span>only<\/em> after the June 14 update has been installed on all intermediate or application servers and all DCs. <\/span><\/p>\n Did you get that? I must note with a certain sense of irony, that the most detailed, order-specific set of instructions that Microsoft has ever published (ever), are buried deep, mid-way through a very long technical article. I hope everyone is paying attention.<\/span><\/p>\n Though we have fewer “new” patches released this month, there are a lot of updated and newly released patches from previous months, including:<\/span><\/p>\n I think that we can safely work through the Visual Studio updates, and the Endpoint Configuration Manager changes will take some time to implement, but both changes do not have significant testing profiles. DCOM changes are different \u2014 they are tough to test and generally require a business owner to validate not just the installation\/instantiation of the DCOM objects, but the business logic and the desired outcomes. Ensure that you have a full list of all applications that have DCOM dependencies and run through a business logic test, or you may have some unpleasant surprises \u2014 with very difficult-to-debug troubleshooting scenarios.<\/span><\/p>\n For this Patch Tuesday, Microsoft published one key mitigation for a serious Windows vulnerability:<\/span><\/p>\n Making this change will require a restart of the target server.<\/span><\/p>\n Each month, we break down the update cycle into product families (as defined by Microsoft) with the following basic groupings:<\/span><\/p>\n We are seeing a welcome trend of fewer and fewer critical updates to the entire Microsoft browser portfolio. For this cycle, Microsoft has released<\/span> five updates<\/span><\/a> to the<\/span> Chromium<\/span> version of Edge. They are all low risk to deploy and resolve the following reported vulnerabilities:<\/span><\/p>\n A key factor in this downward trend of browser related security issues, is the decline and now retirement of Internet Explorer<\/a> (IE). IE is officially no longer supported as of this July.<\/span> The future of Microsoft’s browsers is Edge,<\/span><\/a> according to Microsoft. Microsoft has provided us with a video overview of Internet Explorer’s retirement. Add these Chromium\/Edge browser updates to your standard application release schedule.<\/span><\/p>\n With 33 of this month’s 55 Patch Tuesday updates, the Windows platform is the primary focus \u2014 especially given the low-risk, low-profile updates to Microsoft Browsers, Office, and development platforms (.NET). The Windows updates cover a broad base of functionality, including:<\/span> NTFS<\/span><\/a>, Windows networking, the codecs (media) libraries, and the Hyper-V and docker components. As mentioned earlier, the most difficult-to-test and troubleshoot will be the kernel updates and the local security sub-system (<\/span>LSASS<\/span><\/a>). Microsoft recommends a<\/span> ring-based deployment<\/span><\/a> approach, which will work well for this month\u2019s updates, primarily due to the number of core infrastructural changes that should be picked up in early testing. (<\/span>Microsoft has published another video about the changes this month to the Windows 11 platform,<\/span>\u00a0found<\/span>\u00a0here<\/span><\/a>.)<\/span><\/p>\n Microsoft has fixed the widely-exploited Windows <\/span>Follina MSDT zero-day vulnerability<\/span><\/a> reported as <\/span>CVE-2022-30190<\/span><\/a>,\u00a0which given the other three critical updates (<\/span>CVE-2022-30136<\/span><\/a>,<\/span> CVE-2022-3063<\/span><\/a> and<\/span> CVE-2020-30139<\/span><\/a>) leads to a “Patch Now” recommendation.<\/span>\u00a0<\/span><\/p>\n Microsoft released seven updates to the Microsoft Office platform (SharePoint, Excel, and the Office Core foundation library), all of them rated important. The SharePoint server updates are relatively low risk, but will require a server reboot. We were initially worried about the<\/span> RCE<\/span><\/a> vulnerability in Excel, but on review it appears that the \u201cremote\u201d in Remote Code Execution refers to the attacker location. This Excel vulnerability is more of an Arbitrary Code Execution vulnerability; given that it requires user interaction and access to a local target system, it is a much-reduced risk. Add these low-profile Office updates to your standard patch deployment schedule.<\/span><\/p>\n We have a<\/span> SQL server update<\/span><\/a> this month, but no Microsoft Exchange Server updates for June. This is good news.<\/span><\/p>\n Microsoft has released a single, relatively low-risk (<\/span>CVE-2022-30184<\/span><\/a>) update to the .NET and Visual Studio platform. If you are using a Mac (I love the<\/span> Mac version of Code<\/span><\/a>), Microsoft recommends that you update to<\/span> Mac Visual Studio 2022<\/span><\/a> (still in preview) as soon as possible. As of July (yes, next month) the Mac version of Visual Studio 2019 will no longer be supported. And yes, losing patch support in the same month as the next version is released is tight. Add this single .NET update to your standard development patch release schedule.<\/span><\/p>\n There are no Adobe Reader or Acrobat updates for this cycle. Adobe has released a<\/span> security bulletin<\/span><\/a> for their other (non-Acrobat or PDF related) applications \u2014 all of which are rated at the lowest level 3 by Adobe. There will be plenty of work with printers in the coming weeks, so this is a welcome relief.<\/span><\/p>\n http:\/\/www.computerworld.com\/category\/security\/index.rss<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Credit to Author: Greg Lambert| Date: Fri, 17 Jun 2022 12:09:00 -0700<\/strong><\/p>\n June’s Patch Tuesday updates, released on June 14, address 55 vulnerabilities in Windows, SQL Server, Microsoft Office, and Visual Studio (though there are oo Microsoft Exchange Server or Adobe updates this month). And a zero-day vulnerability in a key Windows component,<\/span> CVE-2022-30190<\/span><\/a>, led to a \u201cPatch Now\u201d recommendation for Windows, while the .NET, Office and SQL Server updates can be included in a standard release schedule. <\/span><\/p>\n<\/p>\n