Despite Microsoft’s announcement in May that non-security releases (C and D updates) are paused until more notice, with 129 updates in June’tuesday launch cycle s Patch, there is a lot to do – for the deployment team as well as your application testing group(s).

We see another critical update to Adobe Flash Gamer (see how to create your kill bits below) and critical updates to Microsoft’s browsers that – based on your legacy program portfolio – may necessitate immediate action. Month may be the number and character of improvements to the Windows system the area to spotlight this.

Plenty of Windows elements and subsystems &ldquo are;touched” by this 30 days’s updates latest, resulting in a big testing surface. Unlike previous up-dates, this month’s few growth tool updates could also result in some additional testing specifications for specific services.

For this 30 days, we have to focus on the assumption that of the Windows, Adobe and browser improvements will demand a reboot. The Microsoft Programmer and Office tools up-dates may necessitate a reboot, depending on one’s body.

Known Issues

Each month, Microsoft carries a list of known conditions that relate to the operating-system and platforms which are one of them update cycle. I’ve referenced several key problems that relate to the most recent builds from Microsoft which includes:

• Right after installing this update on a Home windows 10 device with a radio wide area network (WWAN) LTE modem, achieving the internet might not be possible. However, the Network Online connectivity Position Indicator (NCSI) in the notification area might nevertheless indicate you are connected to the web. Microsoft is focusing on a resolution and can provide an update within an upcoming release.
• After installing KB4493509, devices with some Asian language packs installed may have the error, “0x800f0982 – Microsoft is focusing on a resolution to the issue.

You could find Microsoft&rsquo also;s summary of Known Issues for the June 2020 release within a page.

Major Revisions

Two updates had main revisions because of this month’s update routine from Microsoft:

• CVE-2020-0762 and CVE-2020-0763: Microsoft has released security updates for Windows Defender Security Canter engine to handle both these vulnerabilities
• CVE-2020-1108: To comprehensively address CVE-2020-1108, Microsoft has released updates for .NET Primary 2.1 and .NET Primary 3.1.

Each month, we breakdown the update cycle into product families (as described by Microsoft) with the next basic groupings:

• Browsers (Microsoft IE and Advantage)
• Microsoft Windows (each desktop and server)
• Microsoft Office (Including Internet Apps and Swap)
• Microsoft Growth platforms (ASP.NET Core, .NET Primary and Chakra Primary)
• Adobe Flash Participant

Browsers

Month with 22 relatively highly-rated exploits to solve this, Microsoft has released 5 critical, six important, 5 moderate and an additional six updates rated as low. Normally, this true amount of updates to Microsoft’s browsers would result in a rapid reaction and urgent deployment of patches, especially like these critical updates deal with issues that may lead to arbitrary program code operate on compromised systems (through basically going to specially crafted malicious sites).

However, the vast majority of this month’s protection vulnerabilities relate with how VBScript handles ActiveX program code in memory. What will this mean? Well, for some well-run IT houses ActiveX has been verbotenverboten for some time, and is probable very tightly managed (we.e. disabled) alongside browser assistance for VBScript. In case you are running a restricted ship, add these improvements to your regular deployment effort. In case you are concerned about legacy apps with VBScript or ActiveX dependencies (actually) running amok, after that these updates have to be put into the top of one’s testing regime.

Microsoft Windows

This month’s Patch Tuesday up-date is really a (another) huge upgrade for the Home windows ecosystem. Despite having Microsoft pausing all optional up-dates and concentrating on security fixes still, June’s revise cycle includes a lot more than 90 safety fixes to Home windows and unusually contains the next quality update that resolves:

• Problems that prevent customers from updating .MSI data files from the network folder.
• Problems that may cause the advertising of the server to the domain controller to fail. This occurs once the Local Safety Authority Subsystem Services (LSASS) process is defined as Protected Process Lighting (PPL).
• A security issue described in CVE-2018-0886 with the addition of support for the “Encryption Oracle Remediation” policy setting and changing the default value from Susceptible to Mitigated. To learn more about how this may affect your environment if you work with Remote Desktop, see KB4093492.

Again, this can be a huge update – with Microsoft addressing critical and important vulnerabilities across over 50 different areas in the Windows 10 OS.

• Windows Kernel: 14 fixes Elevation of privilege and Security Feature Bypass
• Windows Runtime: 11 Elevation of Privilege updates
• Windows Diagnostic Hub: 8 Elevation of privilege patches
• Windows Error Reporting: 4 Elevation of Privilege and information Disclosure issues

Sufficient reason for the older/legacy systems included in Microsoft’s ESU patch regime we have been seeing some real hotspots with vulnerabilities address this month in the next areas:

• VBScript: 6 Elevation of Privilege
• Windows Installer: 3 Elevation of Privilege
• Win32 Kernel: 4 Elevation of Privilege

Following all this, we’ve some real concerns concerning the updates to OLE (CVE-2020-1281 and CVE-2020-1212) and the update to the now aging COM model with CVE-2020-1311as our algorithmic testing engine found some issues inside our application testing portfolio. Month given the quantity and nature of updates this, this update is thought by us must be tested against a core band of applications, and deployed in stages then.

Given the large(ish) amount of updates to the Windows kernel, we might see some update compatibility problems with Windows drivers (especially drivers reliant on the GDI+ sub-system and possible font related issues). Test, deploy in watch and stages for driver and font problems in your telemetry because of this month’s update cycle.

Microsoft Office

There was an individual critical update to Microsoft SharePoint Server and eight remaining important updates for Microsoft Office. Of the eight, six relate (again) to SharePoint server and a XSS (Cross-scripting) attack. Many of these SharePoint (and another two updates that relate with Outlook and Excel) are difficult to exploit on recent versions of Office. Add this update to your standard Office update schedule. Noting that the SharePoint update shall need a reboot to the server.

Microsoft Development Platforms

I think we have to focus on the updates for Microsoft’s development tools because of this update cycle. You can find five updates released to handle a comparatively serious elevation of privilege vulnerability in another of Microsoft’s diagnostic tools (Diagnostics Hub Standard Collector) that runs as an area service. Microsoft has released updates linked to this component before (CVE-2010-0810) and something released with Visual Studio resulted in reported memory issues and memory leaks. This update has among the highest CVSS (risk) scores for development tool vulnerabilities and for that reason must be tested and patched as important.

You’re suggested by me try Windows 10, Release 2004 (You will want to?) watching the memory using:

“%WinDir%system32DiagSvcsDiagnosticsHub.StandardCollector.Service.exe”. If it presents over 30% processor utilization, you might have a nagging problem. Add this update to your development update release schedule with particular focus on the collector service.

Adobe Flash Player

Microsoft has released an update rated as critical (ADV200010) to handle an individual vulnerability (APSB20-30) in Adobe Flash player which could result in a remote code execution scenario. Microsoft has the right advice this month: set the “kill bits” to Adobe Flash – and disable the capability to instantiate Flash Player in virtually any browser. To avoid Adobe Flash Player from running it is possible to set the application form (hardblock) compatibility bits in a .REG text file with the next settings:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftInternet ExplorerActiveX CompatibilityD27CDB6E-AE6D-11CF-96B8-444553540000]

“Compatibility Flags”=dword:00000400

[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftInternet ExplorerActiveX CompatibilityD27CDB6E-AE6D-11CF-96B8-444553540000]

“Compatibility Flags”=dword:0000040

Once done, it is possible to rest easy and deploy this update making use of your standard desktop update schedule.