Giveaway of the Day Forums

1. 

   mikiem2
   Moderator

   zdnet[.]com/article/microsofts-big-patch-tuesday-fixes-exploited-zero-day-flaw-and-120-more-bugs/

   Too soon to tell if there are any big problems or nasty bugs yet, but this *may* be a more important update since one of the flaws that's fixed is being actively exploited.

   Microsoft has released patches for 141 flaws in its August 2022 Patch Tuesday update including two previously undisclosed (zero-day) flaws, of which one is actively being exploited.

   The total patch count for the August 2022 Patch Tuesday Update actually includes 20 flaws in Edge that Microsoft had previously released fixes for, leaving 121 flaws affecting Windows, Office, Azure, .NET Core, Visual Studio and Exchange Server.

   The actively exploited bug is a remote code execution flaw affecting the Microsoft Windows Support Diagnostic Tool (MSDT), tracked as CVE-2022-34713. According to Microsoft, it is related to a bug that some in security researchers refer to as "Dogwalk".

   And a reminder for anyone effected [i.e. corp + those who've used the hack]:

   Security firm Ivanti notes that as of the August Patch Tuesday update, there are only six months of Extended Security Updates (ESU) remaining for Windows 7 and Windows Server 2008/2008R2.

   Posted 2 years ago #
2. 

   mikiem2
   Moderator

   A problem has surfaced with one of the included fixes not installing on some devices. The problem Microsoft intended to fix was a vulnerability called BootHole. When Secure Boot is turned on & active, the UEFI BIOS will try to match the boot code, e.g., to start Windows, against a database of known good samples. If the boot code cannot be matched, the code will not be run. The vulnerability comes from one of the samples in that database needing to be removed -- malware could add a malicious boot loader and Secure Boot would not detect it as bad.

   neowin[.]net/news/new-boothole-flaw-in-secure-boot-affects-a-huge-number-of-linux-and-windows-systems/

   Microsoft developed a fix, KB5012170, that was included in the cumulative update for August, 2022, but that specific fix isn't installing on some devices, while the rest of the updates usually succeed.

   neowin[.]net/news/microsoft-warns-about-windows-update-fails-uefi-update-might-be-necessary-to-fix/

   Microsoft is still trying to figure out why. They note that in some cases updating the BIOS firmware helps. Note: the web site for the device manufacturer, or motherboard manufacturer with a self-built PC, is the only place to find out if there is an updated BIOS firmware package & to download it. If you decide to give updating the BIOS a try, follow the instructions for the update EXACTLY, and be aware that if something goes wrong, it can brick the device.

   And of course ignore all of this if you do not have secure boot enabled & active.

   Posted 2 years ago #
3. 

   mikiem2
   Moderator

   KB5012170 is causing additional problems for some... according to reports it may cause long boot times, may change RAID configurations, and for those using BitLocker, it may cause the BitLocker recovery screen to appear.

   bleepingcomputer[.]com/news/microsoft/windows-kb5012170-update-causing-bitlocker-recovery-screens-boot-issues/

   Posted 2 years ago #
4. 

   mikiem2
   Moderator

   neowin[.]net/news/microsoft-confirms-bitlocker-issues-in-the-latest-windows-updates/

   Microsoft's confirmed the BitLocker issues...

   Those who have already installed KB5012170 and are now getting BitLocker recovery prompts must enter their BitLocker recovery keys. The official guidance is available in the documentation from Microsoft.

   Those who are yet to install KB5012170 or restart their systems after applying the update can temporarily suspend BitLocker to bypass the bug:

   Run Command Prompt as Administrator and enter the Manage-bde -protectors -disable %systemdrive% -rebootcount 2 command.

   Install KB5012170.

   Restart your computer two times.

   BitLocker should be back running after the second restart. You can verify its status using the Manage-bde -protectors -Enable %systemdrive% command.

   Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.