![](\"https:\/\/images.idgesg.net\/images\/article\/2020\/07\/microsoft_windows_updates_cycle_arrows_laptop_mobile_phone_3x2_1200x800-100851684-small.jpg\"\/)
<\/p>\n
With this month’s Patch Tuesday update, Microsoft addressed 130 security vulnerabilities, published two advisories, and included four major CVE revisions. We also have four zero-days to manage for Windows (CVE-2023-32046<\/a>, CVE-2023-32049<\/a>, CVE-2023-36874<\/a> and CVE-2023-36884<\/a>), bringing the Windows platform into a “patch now” schedule.<\/p>\n It should be easier to focus on Microsoft Office and Windows testing this month, as we do not have any Adobe, Exchange, or browser updates. Be sure to carefully review Microsoft’s Storm 0978<\/a> as it provides specific, actionable guidance on managing the serious HTML vulnerability in Microsoft Office (CVE-2022-38023<\/a>).<\/p>\n The\u00a0Readiness<\/a>\u00a0team has crafted this helpful infographic<\/a> to outline the risks associated with each of the updates.<\/p>\n Microsoft each month lists known issues that relate to the operating system and platforms included in the latest update cycle.<\/p>\n Microsoft has published two major revisions:<\/p>\n Microsoft published the following vulnerability-related mitigations for this release:<\/p>\n Each month, the Readiness team\u00a0provides detailed, actionable testing guidance for the latest updates. This guidance is based on assessing a large application portfolio and a detailed analysis of the Microsoft patches and their potential impact on the Windows platforms and application installations.<\/p>\n If you have employed internal web or application servers, it will be worth testing the HTTP3 protocol<\/a>\u00a0\u2014 especially using Microsoft Edge. In addition to this protocol handling update, Microsoft made a significant number of changes and updates to the networking stack requiring the following testing:<\/p>\n Given the large number of system-level changes this month, I have divided the testing scenarios into standard and high-risk profiles.<\/p>\n Given that this update includes fixes for four (some say five) zero-day flaws, we have two main drivers of change this month: key functionality changes in core systems and an urgent need to deliver updates. Microsoft has documented that two core areas have been updated with significant functionality changes, including printing and the local network stack (with a focus on routing). As a result, the following testing should be included before general deployment:<\/p>\n The following changes have been included this month and have not been raised as either high risk (with unexpected outcomes) and do not include functional changes.\u00a0<\/p>\n All these testing scenarios will require significant application-level testing before a general deployment. Given the changes included in this month’s patches, the Readiness team recommends that the followings tests be performed before general deployment:<\/p>\n This month may be a little tough to test your Microsoft Office automation\/scripts and integration with third-party applications due to the change in OLE and how Microsoft has addressed CVE-2023-36884<\/a>. We recommend a full test of Excel macros (if they use OLE\/COM\/DCOM) and any VBS scripts that include Word.<\/p>\n Here are the important changes to servicing (and most security updates) to Windows desktop and server platforms.<\/p>\n Each month, we break down the update cycle into product families (as defined by Microsoft) with the following basic groupings:<\/p>\n Hard to believe, but there are no browser updates in this update cycle. And we don’t see anything coming down the pipeline for a mid-cycle release either. This is a big change and a huge improvement from the days of large, complex, and urgent browser updates. Go Microsoft!<\/p>\n Microsoft released eight critical updates and 95 patches rated as important to the Windows platform, covering these key components:<\/p>\n As mentioned in the Microsoft Office section above, we feel the focus this month should be on the immediate resolution of CVE-2023-36884<\/a>. Though rated as important by Microsoft (sorry to be contrarian), we feel that since it has been both publicly disclosed and exploited it should be treated as urgent. Coupled with the other Windows zero-day (CVE-2023-32046<\/a>) this brings the entire Windows update group into the “Patch Now” schedule for our clients. Once the screaming stops, you can take some time to check out the Windows 11 release<\/a> video; we find it calming.<\/p>\n We need to talk about Microsoft Office. Though there are two critical rated updates for SharePoint (CVE-2023-33157<\/a> and CVE-2023-33160<\/a>) and 14 updates rated important by Microsoft, the elephant in the room is CVE-2023-36884<\/a> (Office and HTML RCE Vulnerability). This vulnerability has been both publicly disclosed and documented as exploited. Officially, this update belongs in the Windows group, but we believe that the true impact lies in how Microsoft Office deals with HTML data (transmit\/store\/compute). CVE-2023-36884<\/a> directly affects Office and your testing regime should reflect this.<\/p>\n Add these Office updates to your standard release schedule, noting that your Office patch testing regime will need to be paired with your Windows update release schedule.<\/p>\n Much to all our good fortune, there are no updates for Microsoft Exchange Server this month.<\/p>\n Compared to the very serious (and numerous) exploits in Office and Windows this month, there are only five updates affecting Visual Studio, ASP.NET and a minor component of Mono<\/a> (the cross platform C# implementation). All these patches are rated important by Microsoft and should be added to your standard developer release schedule.<\/p>\n More good news: there are no updates from Adobe or other third-party vendors in this update.<\/p>\n http:\/\/www.computerworld.com\/category\/security\/index.rss<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" With this month’s Patch Tuesday update, Microsoft addressed 130 security vulnerabilities, published two advisories, and included four major CVE revisions. We also have four zero-days to manage for Windows (CVE-2023-32046<\/a>, CVE-2023-32049<\/a>, CVE-2023-36874<\/a> and CVE-2023-36884<\/a>), bringing the Windows platform into a “patch now” schedule.<\/p>\n<\/p>\n