{"id":365,"date":"2024-08-22T06:53:39","date_gmt":"2024-08-22T06:53:39","guid":{"rendered":"https:\/\/familiebuckens.nl\/?p=365"},"modified":"2024-08-23T06:54:26","modified_gmt":"2024-08-23T06:54:26","slug":"google-fixes-high-severity-chrome-flaw-actively-exploited-in-the-wild","status":"publish","type":"post","link":"https:\/\/familiebuckens.nl\/index.php\/2024\/08\/22\/google-fixes-high-severity-chrome-flaw-actively-exploited-in-the-wild\/","title":{"rendered":"Google Fixes High-Severity Chrome Flaw Actively Exploited in the Wild"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Google has rolled out security fixes to address a high-severity security flaw in its Chrome browser that it said has come under active exploitation in the wild. Tracked as\u00a0<strong>CVE-2024-7971<\/strong>, the vulnerability has been described as a type confusion bug in the V8 JavaScript and WebAssembly engine. &#8220;Type confusion in V8 in Google Chrome prior to 128.0.6613.84 allowed a remote attacker to exploit heap corruption via a crafted HTML page,&#8221; according to a\u00a0<a href=\"https:\/\/nvd.nist.gov\/vuln\/detail\/CVE-2024-7971\" target=\"_blank\" rel=\"noreferrer noopener\">description<\/a>\u00a0of the bug in the NIST National Vulnerability Database (NVD).<\/p>\n\n\n<a class=\"wp-block-read-more\" href=\"https:\/\/familiebuckens.nl\/index.php\/2024\/08\/22\/google-fixes-high-severity-chrome-flaw-actively-exploited-in-the-wild\/\" target=\"_self\"><a href=\"https:\/\/thehackernews.com\/2024\/08\/google-fixes-high-severity-chrome-flaw.html\">Google Fixes High-Severity Chrome Flaw Actively Exploited in the Wild (thehackernews.com)<\/a><span class=\"screen-reader-text\">: Google Fixes High-Severity Chrome Flaw Actively Exploited in the Wild<\/span><\/a>","protected":false},"excerpt":{"rendered":"<p>Google has rolled out security fixes to address a high-severity security flaw in its Chrome browser that it said has come under active exploitation in the wild. Tracked as\u00a0CVE-2024-7971, the vulnerability has been described as a type confusion bug in the V8 JavaScript and WebAssembly engine. &#8220;Type confusion in V8&#8230;<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20,17],"tags":[31],"class_list":["post-365","post","type-post","status-publish","format-standard","hentry","category-cybersecurity","category-vulnerability","tag-31"],"_links":{"self":[{"href":"https:\/\/familiebuckens.nl\/index.php\/wp-json\/wp\/v2\/posts\/365","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/familiebuckens.nl\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/familiebuckens.nl\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/familiebuckens.nl\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/familiebuckens.nl\/index.php\/wp-json\/wp\/v2\/comments?post=365"}],"version-history":[{"count":1,"href":"https:\/\/familiebuckens.nl\/index.php\/wp-json\/wp\/v2\/posts\/365\/revisions"}],"predecessor-version":[{"id":366,"href":"https:\/\/familiebuckens.nl\/index.php\/wp-json\/wp\/v2\/posts\/365\/revisions\/366"}],"wp:attachment":[{"href":"https:\/\/familiebuckens.nl\/index.php\/wp-json\/wp\/v2\/media?parent=365"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/familiebuckens.nl\/index.php\/wp-json\/wp\/v2\/categories?post=365"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/familiebuckens.nl\/index.php\/wp-json\/wp\/v2\/tags?post=365"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}