{"id":19848,"date":"2022-08-13T04:30:14","date_gmt":"2022-08-13T12:30:14","guid":{"rendered":"http:\/\/www.palada.net\/index.php\/2022\/08\/13\/news-13581\/"},"modified":"2022-08-13T04:30:14","modified_gmt":"2022-08-13T12:30:14","slug":"news-13581","status":"publish","type":"post","link":"http:\/\/www.palada.net\/index.php\/2022\/08\/13\/news-13581\/","title":{"rendered":"Patch Tuesday update addresses 123 vulnerabilities, two critical zero-days"},"content":{"rendered":"

<\/p>\n

Credit to Author: Greg Lambert| Date: Sat, 13 Aug 2022 04:58:00 -0700<\/strong><\/p>\n

Microsoft’s August Patch Tuesday release addresses 123 security issues in Microsoft Windows, Office, Exchange (it’s back!) and Visual Studio \u2014 and unfortunately, we have two zero-days with reports of active exploitation in the wild. Since this is\u00a0a broad update, it will require planning and testing before deployment. <\/span><\/p>\n

The first (<\/span>CVE-2022-34713<\/span><\/a>) occurs in the Windows diagnostic tools and the second (CVE-2022-30134<\/a>) affects Microsoft Exchange<\/span>. Basically, the holidays are over and it’s time to pay attention to Microsoft updates again. We have made “Patch Now” recommendations for Windows, Exchange and Adobe for this month.<\/span><\/p>\n

Y<\/span>ou 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 August patch cycle, I have broken down the testing scenarios into high risk and standard risk groups:<\/span><\/p>\n

High Risk:<\/strong> These are likely to include functionality changes, may deprecate existing functionality and will likely require creating new testing plans:<\/span><\/p>\n

The following updates are not documented as functional changes, but still require a full test cycle:<\/span><\/p>\n

Given the changes to the SSU,<\/span> Windows Boot Manager<\/span><\/a> and updates to the Windows kernel (WIN32KY.SYS) this month, it may be worth having a look at some Microsoft testing platforms such as the Microsoft Test Authoring and Execution Framework (<\/span>TAEF<\/span><\/a>). You will have to know<\/span> C++<\/span><\/a> or<\/span> C#<\/span><\/a> and you will need the Windows Driver kit (<\/span>WDK<\/span><\/a>). Noting that for each of these testing scenarios, a manual shut-down, reboot and restart is suggested, with a focus on Boot Manager entries in the event viewer logs.<\/span><\/p>\n

Each month, Microsoft includes a list of known issues that relate to the operating system and platforms that are included in this update cycle. This month, there are some really complex changes:<\/span><\/p>\n

And for the latest release of Windows 11, it looks as if this month’s update may lead to the utility<\/span> XPS Viewer<\/span><\/a> behaving badly (using increasing processor and memory resources) before closing unexpectedly (i.e. badly). A reboot will solve the issue until Microsoft posts a fix.<\/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:<\/span><\/p>\n

Probably the most important workaround this month relates to Microsoft Outlook crashing and locking up immediately after start-up.\u00a0<\/span>Microsoft explains, “When you start Outlook Desktop, it gets past loading profile and processing, briefly opens, and then stops responding,” Microsoft is currently working on the issue and we expect an update soon. Microsoft offered the following workarounds:<\/span><\/p>\n

You can find out more about Microsoft Diagnostic settings<\/span> here<\/span><\/a>. This is a little embarrassing for Microsoft as this is another significant Office issue following the recent<\/span> Uber receipt<\/span><\/a> crashing issue.<\/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

Browsers<\/strong><\/p>\n

Microsoft released three updates to its Edge browser (<\/span>CVE-2022-33636<\/span><\/a>,<\/span> CVE-2022-33649<\/span><\/a> and<\/span> CVE-2022-35796<\/span><\/a>). Following a trend, none of these are rated as critical. There were also 17 updates to the Chromium project. Google has published all these changes in its\u00a0<\/span>update<\/span>\u00a0log<\/span><\/a>. For further information, refer to the Chromium<\/span> security update\u00a0page<\/span><\/a>. Along with these security fixes, there were a few new features in the latest stable release (103) which\u00a0<\/span>can be found\u00a0<\/span>here<\/span><\/a>. Add these low-profile updates to your standard patch release schedule.<\/span><\/p>\n

Windows<\/strong><\/p>\n

Microsoft addressed 13 critical issues and 43 issues rated important this month. This is fairly broad update that covers the following key Windows features:<\/span><\/p>\n

In addition to this large update,<\/span> CVE-2022-34713<\/span><\/a> (Microsoft Windows Support Diagnostic Tool (MSDT) Remote Code Execution Vulnerability) has been reported as both publicly disclosed and exploited in the wild, making this a serious Windows<\/span> zero-day<\/span>. This serious Windows security flaw is a<\/span> path traversal flaw<\/span><\/a> that attackers can exploit to copy an executable to the Windows Startup folder when a user opens a specially-crafted file through an email client or downloaded from the web. In lighter news, you can find the latest\u00a0<\/span>Windows 11 update video<\/span>\u00a0here<\/span><\/a>. Add these critical Windows updates to your “Patch Now” release schedule.<\/span><\/p>\n

Microsoft released an out-of-band (OOB) patch (<\/span>KB5002248<\/span><\/a>) for Microsoft Office 2016 (both 32- and 64-bit) relating to VBA projects and Microsoft Access. This month’s release cycle delivers only four updates, all rated important. Microsoft Excel, Outlook and a few core Microsoft Office libraries are affected, with the most serious leading to remote code execution scenarios. Fortunately, all of these security issues have official fixes from Microsoft and are all relatively difficult to exploit, particularly in a well-managed enterprise environment. Add these low-profile updates to your standard release schedule.<\/span><\/p>\n

Unfortunately we have six updates for Microsoft Exchange Server, with three rated critical and the remaining three rated important.\u00a0<\/span>As promised in<\/span>\u00a0May<\/span><\/a>, Microsoft has updated its patching process to include self-extracting EXE’s. You will not find these latest updates in the Microsoft catalog, so I have included a list of <\/span>updates available for the following specific builds of Exchange Server:<\/span><\/p>\n

Given the publicly disclosed vulnerability in Microsoft Exchange (<\/span>CVE-2022-30134<\/span><\/a>) which allows an attacker to read targeted email messages, Microsoft has recommended you apply these security related fixes <\/span>immediately (<\/span><\/i>italics added by Microsoft). To get the latest updates, you may also have to run the\u00a0<\/span>Exchange<\/span>\u00a0SetupAssist\u00a0PowerShell script<\/span><\/a>.\u00a0<\/span><\/p>\n

Your organization may already be comfortable with the new update format, but if you are in doubt about the status of your Exchange servers, you can run the Microsoft CSS<\/span> Health Checker<\/span><\/a>. My feeling is that some preparation and planning is required to stage these updates. It took me a while just to walk through the patching decision\/logic trees this month, never mind<\/span> troubleshooting failed Exchange updates<\/span><\/a>. Add this month’s updates to your “Patch Now” schedule, noting that all updates this month will require a server reboot.<\/span><\/p>\n

Microsoft released five updates rated as important for Visual Studio and .NET Core. The .NET vulnerability (<\/span>CVE-2022-34716<\/span><\/a>) is really tough to exploit and depends upon successfully executing a technically challenging blind “external entity” injection (<\/span>XXE<\/span><\/a>) attack. The remaining Visual Studio vulnerabilities relate to remote code execution (<\/span>RCE<\/span><\/a>) scenarios exploited through a local email client (requiring the user to open a specially crafted file). Add these updates to your standard developer update schedule.<\/span><\/p>\n

Who would have thought it? We are back this August with three updates rated critical and four as important for Adobe Reader.<\/span> APSB22-39<\/span><\/a> has been published by Adobe but not included by Microsoft in this month’s patch cycle. All seven reported vulnerabilities relate to memory leak issues and could lead to a remote code execution scenario (<\/span>RCE<\/span><\/a>), requiring immediate attention. Add these Adobe updates to your “Patch Now” schedule.<\/span><\/p>\n

http:\/\/www.computerworld.com\/category\/security\/index.rss<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

<\/p>\n

Credit to Author: Greg Lambert| Date: Sat, 13 Aug 2022 04:58:00 -0700<\/strong><\/p>\n

\n
\n

Microsoft’s August Patch Tuesday release addresses 123 security issues in Microsoft Windows, Office, Exchange (it’s back!) and Visual Studio \u2014 and unfortunately, we have two zero-days with reports of active exploitation in the wild. Since this is\u00a0a broad update, it will require planning and testing before deployment. <\/span><\/p>\n

The first (<\/span>CVE-2022-34713<\/span><\/a>) occurs in the Windows diagnostic tools and the second (CVE-2022-30134<\/a>) affects Microsoft Exchange<\/span>. Basically, the holidays are over and it’s time to pay attention to Microsoft updates again. We have made “Patch Now” recommendations for Windows, Exchange and Adobe for this month.<\/span><\/p>\n

To read this article in full, please click here<\/a><\/p>\n<\/section>\n<\/article>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"colormag_page_container_layout":"default_layout","colormag_page_sidebar_layout":"default_layout","footnotes":""},"categories":[11062,10643],"tags":[10516,714,24580,10525],"class_list":["post-19848","post","type-post","status-publish","format-standard","hentry","category-computerworld","category-independent","tag-microsoft","tag-security","tag-small-and-medium-business","tag-windows"],"_links":{"self":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/19848","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/comments?post=19848"}],"version-history":[{"count":0,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/19848\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/media?parent=19848"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/categories?post=19848"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/tags?post=19848"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}