Google heeft versie 118 van zijn webbrowser Chrome uitgebracht. Google Chrome is beschikbaar voor Windows, Linux en macOS. Er zijn ook versies voor Android en iOS, maar die volgen een iets ander releaseschema. In versie 118 heeft Google diverse verbeteringen met betrekking tot de beveiliging aangebracht. Zo staat Encrypted Client Hello nu standaard aan en kan Google extensies uitschakelen die niet via de Chrome Web Store zijn geïnstalleerd. Meer informatie over de veranderingen die in deze uitgave zijn aangebracht, naast de gebruikelijke bug- en securityfixes, kan bij GHacks worden gevonden.
Google Chrome 118Google informs users on the official Chrome Releases blog that it has patched 20 unique security issues in the Chrome web browser. 14 of those are listed on the page, the remaining six were discovered internally. The main issue is CVE-2023-5218. It is a critical security issue, an use after free in Site Isolation. The remaining publicly disclosed vulnerabilities have a severity rating of medium or low. They address additional use after free and heap buffer overflow issues, as well as "inappropriate implementations".
Chrome 118 is the first stable version of Google's web browser with Encrypted Client Hello support. Google introduced support in Chrome Canary back in 2022 and has been working on the feature since. Without going into too many details, Encrypted Client Hello protects the domain name from being leaked to network operators when users open sites and services in the browser. It improves privacy as a consequence, as network operators such as the ISP, do not know anymore which sites a user accesses. One effect of this is that DNS-based blocking is no longer working, provided that the site and server in question support the new technology. Mozilla introduced support for Encrypted Client Hello in Firefox 118 and most Chromium-based browsers will support the feature soon.
Another security feature gives Google the ability to disable extensions remotely that were not installed from the Chrome Web Store. Enhanced Safe Browsing needs to be enabled in Chrome for this to work and Google claims that it will use the feature only to disable malicious extensions. The disabling may happen manually or through automated detection systems according to Google.
Another Enhanced Safe Browsing change improves the deep scanning functionality. Chrome 118 users may now be prompted to provide the password for an archive file to allow Safe Browsing to analyze it.
Chrome is now also collecting "telemetry information about chrome.tabs API calls made by extensions" if Enhanced Safe Browsing is enabled. The information is analyzed on Google servers to improve the "detection of malicious and policy violating extensions".
:fill(white):strip_exif()/i/2002189289.jpeg?f=thumbmedium)
:strip_exif()/u/53522/crop583d477015a24.gif?f=community){kind=small}
/u/20302/pc.png?f=community){kind=small}
/u/153650/2women60x60a.JPG?f=community){kind=small}
/u/590416/crop5d8a8f12228ba_cropped.png?f=community){kind=small}