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: Medium CVE-2023-4078: Inappropriate implementation in Extensions. Medium CVE-2023-4077: Insufficient data validation in Extensions. Reported by Natalie Silvanovich of Google Project Zero on
High CVE-2023-4076: Use after free in WebRTC. High CVE-2023-4075: Use after free in Cast. High CVE-2023-4074: Use after free in Blink Task Scheduling. High CVE-2023-4073: Out of bounds memory access in ANGLE. Reported by Apple Security Engineering and Architecture (SEAR) on High CVE-2023-4072: Out of bounds read and write in WebGL. Chrome combines a minimal design with sophisticated technology to make the web faster, safer, and easier. Reported by Guang and Weipeng Jiang of VRI on Google Chrome is a fast, simple, and secure web browser, built for the modern web. High CVE-2023-4071: Heap buffer overflow in Visuals. High CVE-2023-4070: Type Confusion in V8. Reported by Man Yue Mo of GitHub Security Lab on High CVE-2023-4069: Type Confusion in V8. High CVE-2023-4068: Type Confusion in V8. 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.
0 kommentar(er)
