{"id":6482,"date":"2021-01-28T14:13:57","date_gmt":"2021-01-28T14:13:57","guid":{"rendered":"https:\/\/woas.academy\/?p=6482"},"modified":"2021-01-28T14:17:19","modified_gmt":"2021-01-28T14:17:19","slug":"new-chrome-zero-day-under-active-attacks-update-your-browser","status":"publish","type":"post","link":"https:\/\/woas.academy\/pt\/new-chrome-zero-day-under-active-attacks-update-your-browser\/","title":{"rendered":"New chrome zero-day under active attacks \u2013 update your browser"},"content":{"rendered":"<p>Google has patched a second actively exploited zero-day flaw in the Chrome browser in two weeks, along with addressing nine other security vulnerabilities in its latest update.<\/p>\n<p>The company\u00a0<a href=\"https:\/\/chromereleases.googleblog.com\/2020\/11\/stable-channel-update-for-desktop.html\" target=\"_blank\" rel=\"noreferrer noopener\">released<\/a>\u00a086.0.4240.183 for Windows, Mac, and Linux, which it said will be rolling out over the coming days\/weeks to all users.<\/p>\n<p>The zero-day flaw, tracked as\u00a0<strong>CVE-2020-16009<\/strong>, was reported by Clement Lecigne of Google\u2019s Threat Analysis Group (TAG) and Samuel Gro\u00df of Google Project Zero on October 29.<\/p>\n<p>The company also warned that it \u201cis aware of reports that an exploit for CVE-2020-16009 exists in the wild.\u201d<\/p>\n<p>Google hasn\u2019t made any details about the bug or the exploit used by threat actors public so as to allow a majority of users to install the updates and prevent other adversaries from developing their own exploits leveraging the flaw.<\/p>\n<p>But Ben Hawkes, Google Project Zero\u2019s technical lead,\u00a0<a href=\"https:\/\/twitter.com\/benhawkes\/status\/1323374326150701057\" target=\"_blank\" rel=\"noreferrer noopener\">said<\/a>\u00a0CVE-2020-16009 concerned an \u201cinappropriate implementation\u201d of its V8 JavaScript rendering engine leading to remote code execution.<\/p>\n<p>Aside from the ten security fixes for the desktop version of Chrome, Google has also addressed a separate zero-day in Chrome for Android that was being exploited in the wild \u2014 a sandbox escape flaw tracked as CVE-2020-16010.<\/p>\n<p>The zero-day disclosures come two weeks after Google fixed a critical buffer overflow flaw (<a href=\"https:\/\/thehackernews.com\/2020\/10\/chrome-zeroday-attacks.html\" target=\"_blank\" rel=\"noreferrer noopener\">CVE-2020-15999<\/a>) in the Freetype font library.<\/p>\n<p>Then late last week, the company revealed a Windows privilege escalation zero-day (<a href=\"https:\/\/thehackernews.com\/2020\/11\/warning-google-discloses-windows-zero.html\" target=\"_blank\" rel=\"noreferrer noopener\">CVE-2020-17087<\/a>) that was employed in combination with the above font rendering library flaw to crash Windows systems.<\/p>\n<p>The search giant hasn\u2019t so far clarified if the same threat actor was exploiting the two zero-days.<\/p>\n<p>Source:\u00a0<em>The Hacker News<\/em><\/p>","protected":false},"excerpt":{"rendered":"<p>Google has patched a second actively exploited zero-day flaw in the Chrome browser in two weeks, along with addressing nine other security vulnerabilities in its latest update. The company\u00a0released\u00a086.0.4240.183 for Windows, Mac, and Linux, which it said will be rolling out over the coming days\/weeks to all users. The zero-day flaw, tracked as\u00a0CVE-2020-16009, was reported [&hellip;]<\/p>","protected":false},"author":2,"featured_media":6490,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[36],"tags":[],"class_list":["post-6482","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-social-networks"],"_links":{"self":[{"href":"https:\/\/woas.academy\/pt\/wp-json\/wp\/v2\/posts\/6482","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/woas.academy\/pt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/woas.academy\/pt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/woas.academy\/pt\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/woas.academy\/pt\/wp-json\/wp\/v2\/comments?post=6482"}],"version-history":[{"count":5,"href":"https:\/\/woas.academy\/pt\/wp-json\/wp\/v2\/posts\/6482\/revisions"}],"predecessor-version":[{"id":6494,"href":"https:\/\/woas.academy\/pt\/wp-json\/wp\/v2\/posts\/6482\/revisions\/6494"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/woas.academy\/pt\/wp-json\/wp\/v2\/media\/6490"}],"wp:attachment":[{"href":"https:\/\/woas.academy\/pt\/wp-json\/wp\/v2\/media?parent=6482"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/woas.academy\/pt\/wp-json\/wp\/v2\/categories?post=6482"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/woas.academy\/pt\/wp-json\/wp\/v2\/tags?post=6482"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}