I’m not sharing all of this to scare you, or to say “ha ha, my Chromebook got an update before yours did!” Nor am I suggesting you switch over to test Lacros on a primary device right now. This particular issue, CVE-2022-1096, is ranked as High and even worse, Google says it “is aware that an exploit for CVE-2022-1096 exists in the wild. But when it comes to High or Severe browser exploits, you want a fix as quickly as possible. I realize a few days is simply that: A few days. Nearly all Chromebook users are just getting it now. With Lacros, which again is Google Chrome for Linux, I got my security update as all of the other traditional computer platforms last week. Since Google can quickly patch Chrome for Linux, Mac, and Windows and then push just a small browser update to those platforms, it can implement fixes fast. The recent Google Chrome zero-day bug actually illustrates a key benefit of this approach. And if you aren’t aware, Lacros is going to become the default browser on all Chromebooks. Instead, it’s the Linux version of Chrome running on my Chromebook. Technically Lacros is Google Chrome, but it’s not the Chrome OS version of Chrome if that makes sense. Or at least not the Chrome browser that has been integrated as part of Chrome OS for a decade.įor testing, I switched over to the Lacros browser full-time. How did I get my Chromebook browser patched last week? It’s because I’m not using the Chrome browser on my device. My Chromebook got the Google Chrome update last week though, showing the benefits of the Lacros browser. That’s when a Chrome OS 99 Stable Channel update became available. Google Chrome received a patch last week to address this, but Chromebooks had to wait until yesterday. Essentially, there is potential for executable code to be injected into your browser. Last week, news made the rounds about a new Google Chrome zero-day bug.
0 kommentar(er)
