On the last day of April 2022, Google quietly sent a fresh build of desktop Chrome into the world, carrying roughly thirty repairs to flaws in the software that millions of people use to read, shop, and work. It is the sort of ordinary tending that keeps a shared tool safe, the way a gardener clears the paths before the next storm. A news outlet first framed it as a breach, then corrected itself the next day, reminding us that not every alarm is a fire. The company is holding back the finer details for now, so that those who would exploit the cracks cannot read the blueprint while most of us a
Google Patches 30 Chrome Security Flaws, Half Rated High Severity; Users Urged to Update Now
Google is holding back details so attackers don't get a roadmap.
Mark
So did Chrome get hacked or not? The first version of this story said it had.
Mimi
No. Hot Hardware corrected it on May 2. What happened is Google shipped Chrome 101 with about 30 security fixes, and about half a dozen are rated High.
Luke
Worth stressing that the correction removes the breach claim entirely. Nothing in the reporting says any of these flaws was exploited in the wild.
Mark
Why is Google keeping the bug details restricted?
Mimi
Its release notes say access may stay restricted until most users have updated. The idea is to avoid handing attackers a guide while people are still unpatched.
Mark
And the memory errors, why do those matter?
Mimi
Memory manipulation and overflow bugs are a common way for malware to inject code and run it arbitrarily.
Luke
Careful, though. The article says a good portion of recently published bugs are of that type. It doesn't break down which of the 30 are which, and it admits it's too early to get into the details.
Mark
So what's a reader actually supposed to do?
Mimi
Update. Menu, Settings, About Chrome, then Restart Chrome. Or reinstall fresh.
Luke
And the 'billions of users' figure is the publication's characterization, not something from Google's notes. The advice holds either way, but that number is not documented here.
Le Pouls
- Google pushed Chrome 101 to desktop users with about thirty security fixes, roughly six of them flagged as High severity.
- Many of the flaws involve memory overflow and manipulation, a familiar doorway through which malware can slip in and run its own code.
- A news report briefly suggested Chrome had been hacked, then issued a correction calling it a routine patch batch rather than a confirmed breach.
- Google is keeping bug details sealed until most users have updated, racing to close the window before attackers can study the fixes.
- The fastest path to safety is simple: open Chrome's About page, let it fetch the update, and restart the browser.
On the last day of April 2022, Google quietly sent a fresh build of desktop Chrome into the world, carrying roughly thirty repairs to flaws in the software that millions of people use to read, shop, and work. It is the sort of ordinary tending that keeps a shared tool safe, the way a gardener clears the paths before the next storm. A news outlet first framed it as a breach, then corrected itself the next day, reminding us that not every alarm is a fire. The company is holding back the finer details for now, so that those who would exploit the cracks cannot read the blueprint while most of us are still standing on the old floor.
On April 26, 2022, Google released a Stable Channel update for desktop Chrome, build 101.0.4951.41, covering Windows, Mac, and Linux. It bundled about thirty security fixes, half a dozen of them rated High. The update was not a breach, though an earlier report on May 1 had treated it as one until a correction the next day set the record straight.
What troubles security watchers is the nature of many of these bugs. A large share involve memory manipulation and overflow errors, the kind of weakness malware authors have long used to inject code and make it run. Google is restricting the technical details until most users have updated, so attackers cannot use the notes as a map while older versions are still in circulation. That restriction may also extend to flaws in third-party libraries that other projects have not yet fixed.
For ordinary users, the message is plain. Open Chrome, click the three-dot menu, go to Settings and then About Chrome, and let the browser download the new version. When the Restart Chrome button appears, click it. More details will likely surface once the fixes have spread, but for now, updating is the main protection available.
On April 26, 2022, Google pushed an update to the Stable Channel of desktop Chrome that carried about 30 security fixes. Roughly half a dozen of them are rated High severity. The build is Chrome 101.0.4951.41, and it covers Windows, Mac, and Linux.
The story is a little different from how it first ran. Hot Hardware published its piece on May 1 under the assumption that Chrome had been hacked. On May 2 it added a correction: that was wrong. What actually happened is a routine but sizable batch of patches, not a confirmed breach.
Google's release notes list the fixes at length, but they also carry a caveat that matters. Access to bug details and links may be kept restricted until a majority of users have updated. Google says it will also maintain those restrictions if a bug sits in a third-party library that other projects depend on and haven't yet fixed. In plain terms, the company is holding back specifics so that attackers can't use them as a roadmap while many people are still running the older version.
Hot Hardware notes that a good portion of the bugs published recently involve memory manipulation and memory overflow errors. Those are a well-worn route for malware authors, who can use them to inject code into memory and get it to run arbitrarily. If someone exploited such a flaw, the outcome could be malicious code executing on the machine. The publication is careful to say it is too early to dig into the details of the individual fixes, and with Google restricting the information, a full picture isn't yet available.
The audience for the update is enormous. Hot Hardware puts Chrome's user base in the billions, and its recommendation is to update immediately.
The manual process is short. Open Chrome and click the three-dot menu at the top right, usually next to your profile picture or initial if you're signed in. Choose Settings, then click About Chrome in the left panel. That triggers the browser's update check and downloads the new version automatically. When the download finishes, a Restart Chrome button appears; click it and the update is applied. Alternatively, you can download the Chrome installer again and do a fresh install, since it always fetches the latest stable release.
What to watch for next is the disclosure. Because Google is withholding bug details until most users have the fix, more information should surface later. Until then, installing the update is the main protection available to ordinary users.
Citations marquantes
Access to bug details and links may be kept restricted until a majority of users are updated with a fix.— Google Chrome release notes
Envie de l'histoire complète ?
Lire l'original sur Hot Hardware ↗
Technology