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-2941: Inappropriate implementation in Extensions API. Medium CVE-2023-2940: Inappropriate implementation in Downloads. Medium CVE-2023-2939: Insufficient data validation in Installer. Medium CVE-2023-2938: Inappropriate implementation in Picture In Picture. Medium CVE-2023-2937: Inappropriate implementation in Picture In Picture. Reported by Sergei Glazunov of Google Project Zero on High CVE-2023-2936: Type Confusion in V8.
High CVE-2023-2935: Type Confusion in V8. Reported by Mark Brand of Google Project Zero on High CVE-2023-2934: Out of bounds memory access in Mojo. Reported by Quang Nguy?n of Viettel Cyber Security and Nguyen Phuong on High CVE-2023-2933: Use after free in PDF. Reported by Huyna at Viettel Cyber Security on High CVE-2023-2932: Use after free in PDF. High CVE-2023-2931: Use after free in PDF.
High CVE-2023-2930: Use after free in Extensions. High CVE-2023-2929: Out of bounds write in Swiftshader. 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. Strip binaries from the source tree, and use those provided by the system or build them from sourceĪdd, modify, or disable features that inhibit control and transparency (these changes are minor and do not have significant impacts on the general user experience) These components altogether strive to accomplish the following:ĭisable or remove offending services and features that communicate with Google or weaken privacy Ungoogled-chromium is a set of configuration flags, patches, and custom scripts. Fortunately, the source code is available for everything. Even the final build output includes some pre-built binaries. Furthermore, the normal build process for Chromium involves running Google's own high-level commands that invoke many scripts and utilities, some of which download and use pre-built binaries provided by Google. Modifications to Google Chromium for removing Google integration and enhancing privacy, control, and transparencyĪ number of features or background services communicate with Google servers despite the absence of an associated Google account or compiled-in Google API keys.
0 kommentar(er)
