Interested in switching release channels? Find out how here. 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: Reported by Philipp Beer on and Axel Chong on Medium CVE-2022-4926: Insufficient policy enforcement in Intents. Medium CVE-2023-0474: Use after free in GuestView. Medium CVE-2023-0473: Type Confusion in ServiceWorker API. High CVE-2023-0472: Use after free in WebRTC. Reported by chichoo Kim(chichoo) and Cassidy on High CVE-2023-0471: Use after free in WebTransport. 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. A full list of changes in this build is available in the log. The Stable channel has been updated to 1.119 for Mac and Linux and 1.119/.120 for Windows, which will roll out over the coming days/weeks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |