Please see the Chrome Security Page for more information. Below, we highlight fixes that were contributed by external researchers. A full list of changes in this build is available in the log. The Stable and extended stable channels has been updated to 1.198 for Mac and Linux and 1.198/199 for Windows, which will roll out over the coming days/weeks. Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL. Various fixes from internal audits, fuzzing and other initiatives 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.Īs usual, our ongoing internal security work was responsible for a wide range of fixes: Low CVE-2023-3740: Insufficient validation of untrusted input in Themes.
Medium CVE-2023-3738: Inappropriate implementation in Autofill. Reported by Narendra Bhati of Suma Soft Pvt. Medium CVE-2023-3737: Inappropriate implementation in Notifications.
Medium CVE-2023-3736: Inappropriate implementation in Custom Tabs. Medium CVE-2023-3735: Inappropriate implementation in Web API Permission Prompts. Medium CVE-2023-3734: Inappropriate implementation in Picture In Picture. Medium CVE-2023-3733: Inappropriate implementation in WebApp Installs. Reported by Mark Brand of Google Project Zero on High CVE-2023-3732: Out of bounds memory access in Mojo. High CVE-2023-3730: Use after free in Tab Groups. High CVE-2023-3728: Use after free in WebRTC. High CVE-2023-3727: Use after free in WebRTC.
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.
0 kommentar(er)
