{"id":20952,"date":"2023-04-18T08:44:25","date_gmt":"2023-04-18T12:44:25","guid":{"rendered":"https:\/\/me-en.kaspersky.com\/blog\/chrome-vulnerability-april-2023\/20952\/"},"modified":"2023-04-18T17:58:50","modified_gmt":"2023-04-18T13:58:50","slug":"chrome-vulnerability-april-2023","status":"publish","type":"post","link":"https:\/\/me-en.kaspersky.com\/blog\/chrome-vulnerability-april-2023\/20952\/","title":{"rendered":"And now it&#8217;s Chrome needs updating!"},"content":{"rendered":"<p>Another day \u2013 another browser vulnerability discovered! Indeed, the number of dangerous security holes has doubled within a week! Only recently we highlighted the urgent <a href=\"https:\/\/www.kaspersky.com\/blog\/ios-macos-vulnerabilities-april-2023\/47938\/\" target=\"_blank\" rel=\"noopener nofollow\">need to update<\/a> iOS and macOS due to a major bug in Apple WebKit (the engine inside Safari and other browsers in iOS). And now, due to a similar threat in terms of exploitability, you need to update other browsers too. This time the focus of attention is Google Chrome and related browsers (and not only browsers, but let\u2019s not get ahead of ourselves).<\/p>\n<h2>Vulnerabilities in the V8 engine<\/h2>\n<p>\nThe vulnerability <a href=\"https:\/\/nvd.nist.gov\/vuln\/detail\/CVE-2023-2033\" target=\"_blank\" rel=\"nofollow noopener\">CVE-2023-2033<\/a> has been found in the V8 engine. This engine is used for processing JavaScript. It was found by the same researcher at Google\u2019s Threat Analysis Group (TAG) who had a hand in the discovery of the iOS and macOS vulnerabilities described in our <a href=\"https:\/\/www.kaspersky.com\/blog\/ios-macos-vulnerabilities-april-2023\/47938\/\" target=\"_blank\" rel=\"noopener nofollow\">previous post<\/a>.<\/p>\n<p>Since it\u2019s standard Google policy not to release details about a vulnerability until most users have updated their browsers, there are no specifics yet about this security hole. What we do know, however, is that an <a href=\"https:\/\/chromereleases.googleblog.com\/2023\/04\/stable-channel-update-for-desktop_14.html\" target=\"_blank\" rel=\"nofollow noopener\">exploit for this vulnerability already exists<\/a>.<\/p>\n<p>For successful exploitation, attackers need to lure victims to a specially crafted malicious web page. That enables them to <a href=\"https:\/\/www.theregister.com\/2023\/04\/17\/chrome_emergency_patch\/\" target=\"_blank\" rel=\"nofollow noopener\">run arbitrary code on the target computer<\/a>. Like the previously found vulnerability in Safari WebKit, this hole facilitates zero-click attacks. In other words, cybercriminals can infect a device without any active actions on the user\u2019s part \u2014 just getting the victim to visit a dangerous site is enough.<\/p>\n<p>The vulnerability is known to exist at the very least in the desktop versions of <a href=\"https:\/\/en.wikipedia.org\/wiki\/Chromium_(web_browser)%23Browsers_based_on_Chromium\" target=\"_blank\" rel=\"nofollow noopener\">all browsers based on Chromium<\/a>, which means not only Google Chrome itself, but also Microsoft Edge, Opera, Yandex Browser, Vivaldi, Brave, and many others. It likely affects <a href=\"https:\/\/en.wikipedia.org\/wiki\/Electron_(software_framework)\" target=\"_blank\" rel=\"nofollow noopener\">Electron-based<\/a> applications, too. As we <a href=\"https:\/\/www.kaspersky.com\/blog\/dangers-of-desktop-messengers\/47453\/\" target=\"_blank\" rel=\"noopener nofollow\">wrote<\/a> not so long ago, such programs are essentially web pages opened in the Chromium browser built into the application.<\/p>\n<h2>How to protect yourself<\/h2>\n<p>\nTo neutralize the threat of CVE-2023-2033 on your computer, update all Chromium-based browsers installed on it right away. See our detailed post with an explanation of how to do this in <a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-update-google-chrome\/43547\/\" target=\"_blank\" rel=\"noopener nofollow\">Google Chrome<\/a>. But to cut to the chase:<\/p>\n<ul>\n<li>Update Google Chrome to version 112.0.5615.121.<\/li>\n<\/ul>\n<div id=\"attachment_47948\" style=\"width: 3010px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/me-en.kaspersky.com\/blog\/files\/sites\/37\/2023\/04\/18164634\/chrome-vulnerability-april-2023-updated-EN-scaled-1-scaled-scaled-scaled.jpg\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-47948\" src=\"https:\/\/me-en.kaspersky.com\/blog\/files\/sites\/37\/2023\/04\/18164634\/chrome-vulnerability-april-2023-updated-EN-scaled-1-scaled-scaled-scaled.jpg\" alt=\"Update Google Chrome to version 112.0.5615.121\" width=\"3000\" height=\"2006\" class=\"size-full wp-image-47948\"><\/a><p id=\"caption-attachment-47948\" class=\"wp-caption-text\">The security hole we describe is fixed in Google Chrome version 112.0.5615.121<\/p><\/div>\n<ul>\n<li>Patch the vulnerability in other Chromium-based applications, too: you can find a patch to update Microsoft Edge to version 112.0.1722.48 <a href=\"https:\/\/learn.microsoft.com\/en-us\/deployedge\/microsoft-edge-relnotes-security#april-14-2023\" target=\"_blank\" rel=\"nofollow noopener\">here<\/a>, while the <a href=\"https:\/\/vivaldi.com\/blog\/desktop\/minor-update-four-5-7\/\" target=\"_blank\" rel=\"nofollow noopener\">Vivaldi<\/a> and <a href=\"https:\/\/www.reddit.com\/r\/brave_browser\/comments\/12n1njh\/release_channel_150119\/\" target=\"_blank\" rel=\"nofollow noopener\">Brave<\/a> websites already have patches for these browsers.<\/li>\n<li>Always restart the browser after updating; otherwise the update won\u2019t take effect.<\/li>\n<li>Update all Electron-based applications as well (patches for them will likely appear a while later).<\/li>\n<\/ul>\n<p>And of course, be sure to protect all your devices with a <a href=\"https:\/\/me-en.kaspersky.com\/premium?icid=me-en_bb2022-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kprem___\" target=\"_blank\" rel=\"noopener\">reliable antivirus<\/a> that safeguards against new vulnerabilities that are already being exploited but haven\u2019t been fixed yet.<\/p>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"premium-geek\">\n","protected":false},"excerpt":{"rendered":"<p>Why you should update to the latest version of Google Chrome, Microsoft Edge, Opera, Yandex Browser, Vivaldi, Brave and other Chromium-based browsers.<\/p>\n","protected":false},"author":2726,"featured_media":20954,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1486],"tags":[1097,16,1548,1268,22,38,121,268],"class_list":{"0":"post-20952","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-threats","8":"tag-0days","9":"tag-chrome","10":"tag-edge","11":"tag-exploits","12":"tag-google","13":"tag-microsoft","14":"tag-updates","15":"tag-vulnerabilities"},"hreflang":[{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/chrome-vulnerability-april-2023\/20952\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/chrome-vulnerability-april-2023\/25530\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/chrome-vulnerability-april-2023\/28136\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/chrome-vulnerability-april-2023\/25826\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/chrome-vulnerability-april-2023\/35126\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/chrome-vulnerability-april-2023\/47946\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/chrome-vulnerability-april-2023\/26150\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/chrome-vulnerability-april-2023\/31832\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/chrome-vulnerability-april-2023\/31517\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/me-en.kaspersky.com\/blog\/tag\/chrome\/","name":"Chrome"},"_links":{"self":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/20952","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/2726"}],"replies":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=20952"}],"version-history":[{"count":3,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/20952\/revisions"}],"predecessor-version":[{"id":20956,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/20952\/revisions\/20956"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/20954"}],"wp:attachment":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=20952"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=20952"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=20952"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}