<\/div>\n

Google released emergency security updates to address an actively exploited Chrome zero-day vulnerability.<\/h2>\n\n\n\n

Google has released emergency security updates to address a high-severity zero-day vulnerability vulnerability, tracked as CVE-2024-4761, in the Chrome browser.<\/p>\n\n\n\n

The vulnerability is an out-of-bounds write issue that resides in the V8 JavaScript engine of the Google web browser. <\/p>\n\n\n\n

The company confirmed that the flaw is exploited in attacks in the wild.<\/p>\n\n\n\n

“CVE-2024-4761: Out of bounds write in V8. Reported by Anonymous on 2024-05-09″<\/em> reads the advisory<\/strong><\/a>. “<\/gwmw>Google is aware that an exploit for CVE-2024-4761 exists in the wild.”<\/gwmw><\/p>\n\n\n\n

The company addressed the zero-day flaw with the release of 124.0.6367.207\/.208 for Mac\/Windows and 124.0.6367.207 for Linux. Google will roll out updates to all users over the coming days\/weeks.<\/p>\n\n\n\n

The vulnerability CVE-2024-4671<\/a> is the sixth zero-day exploited in attacks fixed by the IT giant this year.<\/p>\n\n\n\n

As usual, Google did not publish details about the attacks exploiting the vulnerability.<\/p>\n\n\n\n

“Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven\u2019t yet fixed<\/em>” continues the advisory.<\/p>\n\n\n\n

Below is the list of actively exploited zero-day flaws in the Chrome browser that have been fixed this year:<\/p>\n\n\n\n

\n
• CVE-2024-0519<\/a><\/strong>: an out of bounds memory access in the Chrome JavaScript engine. (January 2024)<\/li>\n\n\n\n
• CVE-2024-2887<\/a><\/strong>:  a type confusion issue that resides in WebAssembly. Manfred Paul demonstrated<\/a> the vulnerability during the Pwn2Own 2024. (March 2024)<\/li>\n\n\n\n
• CVE-2024-2886<\/a><\/strong>: a use after free issue that resides in the WebCodecs. The flaw was demonstrated by Seunghyun Lee (@0x10n<\/a>) of KAIST Hacking Lab during the Pwn2Own 2024. (March 2024)<\/li>\n\n\n\n
• CVE-2024-3159<\/a><\/strong>: an out-of-bounds memory access in V8 JavaScript engine. The flaw was demonstrated by Edouard Bochin (@le_douds) and Tao Yan (@Ga1ois) of Palo Alto Networks during the Pwn2Own 2024 on March 22, 2024. (March 2024)<\/li>\n\n\n\n
• CVE-2024-4671<\/strong><\/a>: a use-after-free issue that resides in the Visuals component (May 2024). <\/gwmw><\/gwmw><\/li>\n<\/ul>\n\n\n\n

  Follow me on Twitter: @securityaffairs<\/strong><\/a> and Facebook<\/strong><\/a> and Mastodon<\/a><\/p>\n\n\n\n

  Pierluigi Paganini<\/strong><\/a><\/p>\n\n\n\n

  (<\/strong>SecurityAffairs<\/strong><\/a> \u2013<\/strong> hacking, Chrome)<\/strong><\/p>\n\n\n\n

  <\/gwmw><\/p>\n","protected":false},"excerpt":{"rendered":"

  Google released emergency security updates to address an actively exploited Chrome zero-day vulnerability. Google has released emergency security updates to address a high-severity zero-day vulnerability vulnerability, tracked as CVE-2024-4761, in the Chrome browser. The vulnerability is an out-of-bounds write issue that resides in the V8 JavaScript engine of the Google web browser. The company confirmed […]<\/p>\n","protected":false},"author":1,"featured_media":45647,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[3323,5,55],"tags":[2037,42,4112,9508,9506,10918,687,1533,528],"class_list":["post-163136","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-breaking-news","category-hacking","category-security","tag-chrome","tag-google","tag-hacking","tag-hacking-news","tag-information-security-news","tag-it-information-security","tag-pierluigi-paganini","tag-security-news","tag-zero-day"],"yoast_head":"\n