High CVE-2022-3450: Use after free in Peer Connection. High CVE-2022-3449: Use after free in Safe Browsing. High CVE-2022-3448: Use after free in Permissions API. Reported by Narendra Bhati of Suma Soft Pvt. High CVE-2022-3447: Inappropriate implementation in Custom Tabs. High CVE-2022-3446: Heap buffer overflow in WebSQL. Reported by Nan Wang and Yong Liu of 360 Vulnerability Research Institute on High CVE-2022-3445: Use after free in Skia. Please see the Chrome Security Page for more information. Below, we highlight fixes that were contributed by external researchers. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed. Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. Įxtended stable channel has been updated to 1.119 for Windows, Mac which will roll out over the coming days/weeks. A full list of changes in this build is available in the log. We hope that the fix that has been rolled out has taken care of your woes with the unstable bug and that Google may keep updating Chrome with newer and better fixes that add to our benefits and not to our worries.The Stable channel has been updated to 1.119 for Windows, Mac and Linux, which will roll out over the coming days/weeks.
This only goes further to prove even giant tech spearheads like Google are susceptible to human errors and that’s something that always needs to be accounted for in every project. Though the WebContents Occlusion update was allegedly tested and tried out for months in something called ‘Google Canary’ which lets you test beta versions of updates before it’s rolled out for the masses. So the latest issue of Chrome is most likely to solve this bug if you’re someone who has been affected by this. Google has finally addressed this bug and was quick to roll out a fix to mitigate this issue. It only affected users who run Chrome on a Windows Server which is a very common practice in enterprise networks. Though Google Chrome users who were on their smartphones, tabs or home personal computers weren’t affected by this. The ‘experiment’ which led to Google Chrome acting differently on Windows Serverīusinesses, especially IT-based solutions businesses mint money by the second, and therefore, not being able to access the internet via Chrome for around 2 hours approximately had a huge impact on them financially.
0 kommentar(er)
