If you find a new issue, please let us know by filing a bug. 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 Jann Horn and Mark Brand of Google Project Zero on High CVE-2023-1534: Out of bounds read in ANGLE. High CVE-2023-1533: Use after free in WebProtect. Reported by Mark Brand of Google Project Zero on High CVE-2023-1532: Out of bounds read in GPU Video. Reported by Piotr Bania of Cisco Talos on High CVE-2023-1531: Use after free in ANGLE. Reported by The UK's National Cyber Security Centre (NCSC) on High CVE-2023-1530: Use after free in PDF. High CVE-2023-1529: Out of bounds memory access in WebHID. Reported by Wan Choi of Seoul National University on High CVE-2023-1528: Use after free in Passwords. 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.110 for Mac and Linux and 1.110/.111 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 |