New zero-day flaw on Chrome, force update now!

The ninth fault of the year, discovered just days after the eighth. An unusual frequency at Google.

And new! Google teams have released a security update for its Chrome browser aimed at fixing a new zero-day flaw. The company therefore invites you to update your web browser as soon as possible – in case you have disabled automatic updates.

The eighth zero-day fault dated from the end of November only

Do not panic, you are not in the middle of a time loop forcing you to relive November 25, 2022. Indeed, ten days ago, we already invited you to update Google Chrome in order to correct a zero- day discovered by a certain Clément Lecigne.

If this famous Mr. Lecigne still has the paternity of the discovery of the day, it is no longer the CVE-2022-4135 flaw that he has pierced in broad daylight, but rather the CVE-2022-4262 flaw. And since CVE-2022-4135 was the eighth zero-day flaw of the year affecting Google Chrome, CVE-2022-4262 is logically the… ninth. You see, no time loop.

Unfortunately for Google, the company had not accustomed us to such regularity in terms of zero-day flaws. As you will see from the history below, usually there would be at least a few weeks between two such discoveries.

• CVE-2022-4262 – December 2
• CVE-2022-4135 – November 24
• CVE-2022-3723 – October 28
• CVE-2022-3075 – September 2
• CVE-2022-2856 – August 17
• CVE-2022-2294 – July 4
• CVE-2022-1364 – April 14
• CVE-2022-1096 – March 25
• CVE-2022-0609 – February 14

Just remember to restart Chrome

As usual, Google does not provide all the details at this time, simply so as not to reveal valuable information that could be useful to malicious individuals. The company limits itself to mentioning a flaw affecting the V8 JavaScript engine.

However, it urges you to check that your Chrome browser has changed to version 108.0.5359.94/.95 (Windows) or 108.0.5359.94 (macOS and Linux). As a rule, unless you have intentionally changed this setting, Chrome updates are automatic.

However, another, more common factor can leave an update pending: a browser that hasn’t been closed for a while. Indeed, the application of an update requires the restart of the browser.

Source : Google