Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL. We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel. High CVE-2023-4764: Incorrect security UI in BFCache. A full list of changes in this build is available in the log. High CVE-2023-4763: Use after free in Networks. The Stable channel has been updated to 1.82 for Windows and Mac as part of our early stable release to a small percentage of users. High CVE-2023-4762: Type Confusion in V8. High CVE-2023-4761: Out of bounds memory access in FedCM. 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. Google has fixed 26 different security issues in Chrome 116 for desktop systems. The company is switching to a weekly security update cycle to reduce the time bad actors have to exploit new vulnerabilities. Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. Chrome for Android: 1.92 Google will release security updates more often starting in Chrome 116.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |