Google patches seventh zero-day exploit in Chrome in 2022
A critical Google Chrome update for the Mac and Windows desktop browsers is available that addresses an actively exploited vulnerability.

Google Chrome is an alternative browser to Safari
Chrome users should update to version 107.0.5304.87 for Mac and version 107.0.5304.87/.88 for Windows as soon as possible to patch against a known active exploit. To update Chrome on Mac:
This latest patch follows reports suggesting Google Chrome is the most vulnerable browser in 2022.
According to a report from Bleeping Computer, this is Chrome's seventh zero-day vulnerability fix since the start of the year. It patches a bug associated with CVE-2022-3723, which is described as a type confusion bug in the Chrome V8 Javascript engine.
Google didn't provide much information about the bug or how it was exploited for security reasons. Users should update their Chrome browser to ensure they are protected from the latest vulnerabilities.
This update follows an update released on September 2, which also addressed a zero-day vulnerability. It isn't clear how widespread active exploits are, but users should update regardless.
Read on AppleInsider

Google Chrome is an alternative browser to Safari
Chrome users should update to version 107.0.5304.87 for Mac and version 107.0.5304.87/.88 for Windows as soon as possible to patch against a known active exploit. To update Chrome on Mac:
- Launch the Chrome browser
- Click on the icon for More -- three vertical dots - at top right
- Choose Help
- Click on About Google Chrome
- If it appears, click on Update Google Chrome
This latest patch follows reports suggesting Google Chrome is the most vulnerable browser in 2022.
According to a report from Bleeping Computer, this is Chrome's seventh zero-day vulnerability fix since the start of the year. It patches a bug associated with CVE-2022-3723, which is described as a type confusion bug in the Chrome V8 Javascript engine.
Google didn't provide much information about the bug or how it was exploited for security reasons. Users should update their Chrome browser to ensure they are protected from the latest vulnerabilities.
This update follows an update released on September 2, which also addressed a zero-day vulnerability. It isn't clear how widespread active exploits are, but users should update regardless.
Read on AppleInsider
Comments
Problem solved!
Written and illustrated by the guy Google once hired to explain to their own employees what Chrome was.
Is interesting that in an interview a few years ago, Tim Cook said that, even though of the security and privacy mechanisms, "it's not a perfect thing".
Tim Cook defends Google search deal despite Apple’s privacy focus - The Verge
Maybe that small imperfection is enough for Google to invest billions every year. It's obvious that Google is getting something from this deal. Maybe you did the right thing by changing your default engine to DDG, and Apple should do the same. Or maybe Apple is right, and Google is trustworthy, and the negatives comments here are wrong. Who knows...
This has nothing to do with what Google is doing to protect the browser and you from security and privacy threats assuming the code is working as Google intended and where Google is unaware that these vulnerabilities are present. What Google does with its code is a different class of security and privacy concern because those reflect Google’s intentions. Nobody (other than bad actors, or good actors depending on which side you’re on) ever intends to put a security or privacy vulnerability/bug into their code. These are not intentional. These are defects that directly override the best intentions of the software developers and question the quality of the software testing process.
Okay, Google and Chrome are mentioned here, which I suppose opens up the floodgates of criticism around anything Google does, intentional or otherwise. But it seems like the primary knock on Google here should be to question the quality of their software, not question their search or navigation algorithms. Even then, questioning software quality based on the numbered of identified zero day vulnerabilities needs to be a nuanced discussion. It’s not always the case that finding more bugs/vulnerabilities means there are more bugs/vulnerabilities to be found. You also need to look at who is finding these vulnerabilities, how many eyes are probing for vulnerabilities, how widely the software in question is being used, and whether it’s a closed source or open source code base.