{"id":45298,"date":"2020-11-02T20:51:11","date_gmt":"2020-11-03T01:51:11","guid":{"rendered":"https:\/\/www.opensource.im\/uncategorized\/google-discloses-windows-zeroday-bug-exploited-in-the-wild-we-live-security.php"},"modified":"2020-11-02T20:51:11","modified_gmt":"2020-11-03T01:51:11","slug":"google-discloses-windows-zeroday-bug-exploited-in-the-wild-we-live-security","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/cryptography\/google-discloses-windows-zeroday-bug-exploited-in-the-wild-we-live-security.php","title":{"rendered":"Google discloses Windows zeroday bug exploited in the wild &#8211; We Live Security"},"content":{"rendered":"<p><p>The security hole isnt expected to be plugged until the forthcoming Patch Tuesday bundle of security fixes<\/p>\n<p>Googles Project Zero researchers have disclosed details about a zero-day vulnerability in Windows that they say is being exploited by attackers.<\/p>\n<p>The memory-corruption flaw resides in the Windows Kernel Cryptography Driver (cng.sys) and, according to Google, constitutes a locally accessible attack surface that can be exploited for privilege escalation (such as sandbox escape).<\/p>\n<p>The researchers also released proof-of-concept (PoC) code that theyd tested out on a recent version of Windows 10 (version 1903, 64-bit) and believe that the security bug could have been around since Windows 7, potentially meaning that all versions from Windows 7 through 10 could be affected.<\/p>\n<p>Per media reports, the flaw is being exploited in conjunction with another zero-day, which is indexed as CVE-2020-15999 and affects FreeType, a widely used software development library that is also part of the Google Chrome web browser.<\/p>\n<p>Google reported the discovery of the newly-found bug, which is tracked asCVE-2020-17087, to Microsoft, but since it found evidence of the loophole being exploited in the wild, it opted for a seven-day disclosure deadline.<\/p>\n<p>Currently, the security loophole doesnt have a patch, but Project Zeros technical lead Ben Hawkes tweetedthat they do expect one to be released on November 10th, which coincides with the upcoming Patch Tuesday.<\/p>\n<p>Microsoft, meanwhile, provided this statement toTechCrunch:<\/p>\n<p>Microsoft has a customer commitment to investigate reported security issues and update impacted devices to protect customers. While we work to meet all researchers deadlines for disclosures, including short-term deadlines like in this scenario, developing a security update is a balance between timeliness and quality, and our ultimate goal is to help ensure maximum customer protection with minimal customer disruption.<\/p>\n<p>A company spokesperson also went to add that the attack seems to be quite limited and that there is no proof pointing to it being a widespread issue. The attacks are thought to be unrelated to the upcoming US presidential election.<\/p>\n<p>Since the beginning of this year, Microsoft has disclosed and patched several severe bugs in Windows, including a pair of zero-days back in March and another zero-day, which was found by the United States National Security Agency (NSA).<\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Read the original post:<br \/>\n<a target=\"_blank\" href=\"https:\/\/www.welivesecurity.com\/2020\/11\/02\/google-discloses-windows-zero-day-bug-exploited-in-the-wild\/\" title=\"Google discloses Windows zeroday bug exploited in the wild - We Live Security\" rel=\"noopener noreferrer\">Google discloses Windows zeroday bug exploited in the wild - We Live Security<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> The security hole isnt expected to be plugged until the forthcoming Patch Tuesday bundle of security fixes Googles Project Zero researchers have disclosed details about a zero-day vulnerability in Windows that they say is being exploited by attackers. The memory-corruption flaw resides in the Windows Kernel Cryptography Driver (cng.sys) and, according to Google, constitutes a locally accessible attack surface that can be exploited for privilege escalation (such as sandbox escape). <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1600],"tags":[],"class_list":["post-45298","post","type-post","status-publish","format-standard","hentry","category-cryptography"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/45298"}],"collection":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/comments?post=45298"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/45298\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=45298"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=45298"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=45298"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}