![]() ![]() The bug is described as a heap buffer overflow in Freetype, where Freetype is an open source font rendering software toolkit that allows programmers to support the use of all sorts of modern font files and formats in their applications. The reason for making sure you’ve got this particular update is not only that five security bugs have been patched, including one buffer overflow and three use-after-free vulnerabilities, but also that one of these bugs, designated CVE-2020-15999, is already known to attackers.Īs the update notification states, “Google is aware of reports that an exploit for CVE-2020-15999 exists in the wild.” If you’re a Chromium user (that’s the open-source version of Chrome with no proprietary parts), follow your usual update procedure, which depends on the operating system that you’re using and where you got Chromium in the first place. If you’re in the habit of rarely shutting down your computer, or even of rarely exiting from your browser, now would be a good “rare moment” to give Chrome a chance to ingest the update. 75, you’re close – but still on the previous version, so your system hasn’t updated yet.Īs Google explains, you can spot a pending update by the presence of an upward arrow in a circle at the far right of the address bar.Īt this point, closing and re-opening Chrome will apply the fix. That’s the version that was released yesterday as Chrome’s “stable” version, available to all users on Windows, Linux and Mac, not just to opted-in early adopters. ![]() ![]() If so, please check that your auto-updater is working and that you have the latest version.Ī trip to the About Chrome or About Chromium dialog should give the version identifier. Do you browse with Google Chrome or a related product such as Chromium? ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |