{"id":23740,"date":"2024-01-18T04:10:03","date_gmt":"2024-01-18T12:10:03","guid":{"rendered":"http:\/\/www.palada.net\/index.php\/2024\/01\/18\/news-17470\/"},"modified":"2024-01-18T04:10:03","modified_gmt":"2024-01-18T12:10:03","slug":"news-17470","status":"publish","type":"post","link":"http:\/\/www.palada.net\/index.php\/2024\/01\/18\/news-17470\/","title":{"rendered":"Update Chrome! Google patches actively exploited zero-day vulnerability"},"content":{"rendered":"\n

Google has\u00a0released an update<\/a>\u00a0for Chrome which includes four security fixes, including one for a vulnerability that has reportedly already been exploited.<\/p>\n

The easiest way to update Chrome is to allow it to update automatically, which basically uses the same method as outlined below but does not require your attention. But you can end up lagging behind if you never close the browser or if something goes wrong\u2014such as an extension stopping you from updating the browser.<\/p>\n

So, it doesn\u2019t hurt to check now and then. And now would be a good time, given the severity of the vulnerability in this patch. My preferred method is to have Chrome open the page chrome:\/\/settings\/help<\/em> which you can also find by clicking Settings > About Chrome<\/strong>.<\/p>\n

If there is an update available, Chrome will notify you and start downloading it. Then all you have to do is relaunch the browser in order for the update to complete, and for you to be safe from those vulnerabilities.<\/p>\n

\"screenshot<\/figure>\n

After the update, the version should be 120.0.6099.224, or later<\/p>\n

Technical details<\/h2>\n

Google never gives out a lot of information about vulnerabilities, for obvious reasons. Access to bug details and links may be kept restricted until a majority of users are updated with a fix. However, from the update page we can learn a few things.<\/p>\n

Three vulnerabilities found by external researchers all lie in Chrome\u2019s V8 JavaScript engine.<\/p>\n

The Common Vulnerabilities and Exposures (CVE) database lists publicly disclosed computer security flaws. The three V8 vulnerabilities are listed as:<\/p>\n

CVE-2024-0517<\/a>: an out of bounds write in V8 in Google Chrome prior to 120.0.6099.224 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.<\/p>\n

An out-of-bounds write can occur when a program writes outside the bounds of an allocated area of memory, potentially leading to a crash or arbitrary code execution. This can happen when the size of the data written is larger than the size of the allocated memory area, when the data is written to an incorrect location within the memory area, or when the program incorrectly calculates the size or location of the data to be written.<\/p>\n

CVE-2024-0518<\/a>: a type confusion in V8 in Google Chrome prior to 120.0.6099.224 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.<\/p>\n

Type confusion vulnerabilities are programming flaws that happen when a piece of code doesn\u2019t verify the type of object that is passed to it before using it. Type confusion can allow an attacker to feed function pointers or data into the wrong piece of code. In this case, it can lead to heap corruption.<\/p>\n

Heap corruption occurs when a program modifies the contents of a memory location outside of the memory allocated to the program. The heap is an area of memory made available for use by the program. The program can request blocks of memory for its use within the heap.<\/p>\n

CVE-2024-0519<\/a>: out of bounds memory access in V8 in Google Chrome prior to 120.0.6099.224 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.<\/p>\n

An out-of-bounds memory access means that the software has access to data past the end, or before the beginning, of the intended buffer.<\/p>\n

Google notes that it is aware of reports that an exploit for CVE-2024-0519 exists in the wild.<\/p>\n

V8 is an open-source JavaScript and WebAssembly engine developed by the Chromium Project for Chromium and Google Chrome web browsers, so users of other Chromium based browsers, like Microsoft Edge, can expect to see similar updates in the near future.<\/p>\n

Microsoft says<\/a> it\u2019s actively working on releasing a security patch and added:<\/p>\n

\n

\u201cIt’s worth highlighting that Microsoft Edge’s enhanced security mode feature mitigates this vulnerability. You can opt-in into this security feature and have peace of mind that Microsoft Edge is protecting you against this exploit.\u201d<\/p>\n<\/blockquote>\n

Use the following steps to configure enhanced security in Edge.<\/p>\n

    \n
  1. In Microsoft Edge, go to Settings and more<\/strong> > Settings<\/strong> > Privacy, search, and services<\/strong>.<\/li>\n
  2. Under Security<\/strong>, verify that Enhance your security on the web<\/strong> is enabled.<\/li>\n
  3. Select the option that’s best for your browsing.<\/li>\n<\/ol>\n

    The following toggle settings are available:<\/p>\n