{"id":103439,"date":"2020-11-02T21:00:02","date_gmt":"2020-11-02T18:00:02","guid":{"rendered":"https:\/\/en.buradabiliyorum.com\/google-team-reveals-zero-day-windows-exploit\/"},"modified":"2020-11-02T21:00:02","modified_gmt":"2020-11-02T18:00:02","slug":"google-team-reveals-zero-day-windows-exploit","status":"publish","type":"post","link":"https:\/\/buradabiliyorum.com\/en\/google-team-reveals-zero-day-windows-exploit\/","title":{"rendered":"#Google team reveals zero-day Windows exploit"},"content":{"rendered":"

“#Google team reveals zero-day Windows exploit<\/strong>”<\/p>\n

\n
\n
\n
\"Windows
\n Credit: Pixabay\/CC0 Public Domain
\n <\/figcaption><\/figure>\n<\/div>\n<\/div>\n

Google reported a new zero-day vulnerability in Windows Friday that allows for privilege escalation and sometimes resulted in a crash. The vulnerability is a buffer overflow type in a driver found in Windows versions 7 and newer.<\/p>\n

Google’s Project Zero team said the bug, CVE-2020-17087, was being used jointly with an exploit uncovered earlier last week in Google Chrome and Chrome OS. Attackers were able to escape the confines of Chrome’s sandbox and trigger an attack on the operating system. <\/p>\n

Google fixed the Chrome vulnerability and has alerted Microsoft to the remaining bug.<\/p>\n

A zero-day vulnerability is a fault in a system that is disclosed but not yet patched by the manufacturer.<\/p>\n

Project Zero normally discloses vulnerabilities after 90 days or earlier if a solution is made available. But in this instance, because the bug is under active exploit and no patch has yet been issued, the Google team provided Microsoft with a seven-day window to fix the problem before it was made public.<\/p>\n

In a post issued Friday, the Project Zero group stated: “The Windows Kernel Cryptography Driver (cng.sys) exposes a DeviceCNG device to user-mode programs and supports a variety of IOCTLs with non-trivial input structures. It constitutes a locally accessible attack surface that can be exploited for privilege escalation (such as sandbox escape).”<\/p>\n

Microsoft has not yet resolved the problem. Google says it expect Microsoft to issue a patch on November 10, the second Tuesday of the month that is traditionally when Microsoft dispatches accumulated patches.<\/p>\n

Microsoft has offered no guidance on addressing the issue until a patch is released. But a company representative said there is no evidence the bug is being widely exploited. <\/p>\n

In a statement released last week, Microsoft said: “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

Shane Huntley, director of Google’s Threat Analysis team, said the attacks were targeted and are not related to Tuesday’s presidential election.<\/p>\n

Attackers manipulated a function in the Windows Kernel Cryptography Driver by inserting a number into a buffer that is below an allowable level. When the number is converted to a hexadecimal from a binary, input\/output controllers can be hijacked to transmit data into a secure area that allows code execution, providing the attacker with access to the system outside of the protected sandbox.<\/p>\n

The Chrome flaw resolved late last month resided in the FreeType font-rendering library.\n <\/p>\n\n

\n

Windows 10 update could solve Chrome RAM tie-ups\n <\/p><\/div>\n

\n
\n More information:<\/strong>
\n bugs.chromium.org\/p\/project-ze \u2026 ssues\/detail?id=2104<\/a><\/p><\/div>\n

\n \u00a9 2020 Science<\/a> X Network<\/p>\n

<\/p>\n

\n

Citation<\/strong>:
\n Google team reveals zero-day Windows exploit (2020, November 2)
\n retrieved 2 November 2020
\n from https:\/\/techxplore.com\/news<\/a>\/2020-11-google-team-reveals-zero-day-windows.html<\/p>\n

This document is subject to copyright. Apart from any fair dealing for the purpose of private study or research, no
\n part may be reproduced without the written permission. The content is provided for information purposes only.<\/p><\/div>\n<\/p><\/div>\n