The wording of this article is false to begin with and should state “Chromium” instead of “Chrome”. Chrome should hardly have any security issues of its own considering that it’s Chromium + some proprietary binary blobs + different branding essentially. The article’s info is about security bugs affecting all Chromium-based browsers, not just Chrome. The article is not about Chromium based browsers. > The article does and it is to Google’s Chrome I was referring to. I am firmly within the “Let the market decide, as long as the dominant force ain’t closed source it will be OK” Hawack Firefox is like FreeBSD in that scenario, so in a supposed Linux monopoly, you would be among the crowd demanding more use of FreeBSD. Btw, a Chromium monopoly would be akin to a Linux monopoly… Many distros (browsers) all using the Linux kernel (Chromium base). That is, if the alternative has the very same vision for the web as the thing it is supposedly an alternative to, meaning it is useless. Being a bit disingenuous here, eh? Isn’t that beneath you? Who talks about Chrome… Tom, you have been around here for ages and you know that Chrome isn’t the only Chromium-based browser, it’s just the biggest one in terms of market share. In both cases people are actively being misled. Well, either that, or outright propaganda in favor of your preferred project.
I just resent the fact that a simple logical deduction seemingly isn’t possible here. It is still recommended to update Chrome to the latest version as soon as Hawack Google makes no mention of attacks in the wild. Low CVE-2022-2163: Use after free in Cast UI and Toolbar.Reported by YoungJoo of CompSecLab at Seoul National University on High CVE-2022-2481: Use after free in Views.Reported by Sergei Glazunov of Google Project Zero on High CVE-2022-2480 : Use after free in Service Worker API.
Here is the full list as reported by Google: The maximum severity rating of all 11 security issues is high, the second highest after critical. Google does not list security issues that it found internally on the blog. Six of these, all reported by third-party researchers, are mentioned specifically on the blog. The blog post confirms that 11 different security issues are patched in the new Chrome release. Google published an article on the Chrome Releases Blog to inform Chrome users and administrators about the update.
0 kommentar(er)
