The chromium codebase is an over bloated pig. Putting lipstick on a pig, does not change the fact it is a pig. Using that codebase comes with loads of security issues, lack of privacy features, even though chromium is FOSS, it is just googles garbage. ”Īs some among us already know, Google failings in securing their closed source browser also affects other browsers using chromium codebase, because “you can put lipstick on a pig but chromium is still primarily google engineered code developed primarily for a market dominant closed source monopoly environment = CHROME and even EDGE” and it is a bit naive for chromium codebase browser makers to think they are not under the same path that google leads them down, which is *DRUM ROLL PLEASE* Serious and consistent security failings as companies (google) who primarily develop for closed source software are just terrible programmers, with no real invention and true respect for the advantages of privacy and FOSS which comes under the scrutiny of a massive FOSS community with eyes on the code! Chromium codebase provides the vast majority of code for the Google Chrome browser, which is proprietary software. “Other Chromium-based browsers are affected by security issues as well. Expect updates for these browsers in the coming days that address the security issues fixed in Google Chrome. Other Chromium-based browsers are affected by security issues as well. The remaining vulnerabilities are a use after free in WebRTC and WebXR, and a type confusion in V8. The critical security issue, CVE-2023-3214, is a use after free in "autofill payments" according to Google's description. Google makes no mentions of exploits in the wild, but administrators should update the Chrome web browser as soon as possible to protect it from attacks that target these vulnerabilities. One of the security issues has a severity rating of critical, the three remaining ones that Google disclosed a severity rating of high. The fifth was discovered internally and Google does not reveal information about security issues discovered internally. The company lists four of them on the official Chrome Releases blog. Google fixed five security issues in the Chrome web browser.
Google released updates for Chrome for iOS and Android as well, but these do not address security issues according to the short release notes on the Chrome releases blog. Google plans to roll out the update to the entire Chrome population "over the coming days/weeks". The version should be the following one after the update, depending on the operating system that is used on the device:
Chrome will download and install any update that it finds during the check.
Chrome users may select Menu > Help > About Google Chrome, or load chrome://settings/help directly, to display the installed version and run a check for updates. The security update is available already and most Chrome installations should be updated to the new release automatically.
0 kommentar(er)
