Google Patches Chrome Browser ZERO-Day Vulnerability – Update it Now
Finally, the Google has patched zer0-day vulnerability in Chrome browser. The patch has released 86.0.04240.180 version for Windows, Mac and Linux OS platforms. Which will roll out over the coming days/weeks.
A list of all changes is available in the log. Interested in switching release channels?Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.
Security Fixes and Rewards
Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. It will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.
This update includes 10 security fixes. Below, Google highlight fixes that were contributed by external researchers.
Please see the Chrome Security Page for more information.
- [$15000][1138911] High CVE-2020-16004: Use after free in user interface. Reported by Leecraso and Guang Gong of 360 Alpha Lab working with 360 BugCloud on 2020-10-15
- [$15000][1139398] High CVE-2020-16005: Insufficient policy enforcement in ANGLE. Reported by Jaehun Jeong(@n3sk) of Theori on 2020-10-16
- [$5000][1133527] High CVE-2020-16006: Inappropriate implementation in V8. Reported by Bill Parks on 2020-09-29
- [$1000][1125018] High CVE-2020-16007: Insufficient data validation in installer. Reported by Abdelhamid Naceri (halov) on 2020-09-04
- [$TBD][1134107] High CVE-2020-16008: Stack buffer overflow in WebRTC. Reported by Tolya Korniltsev on 2020-10-01
- [$NA][1143772] High CVE-2020-16009: Inappropriate implementation in V8. Reported by Clement Lecigne of Google’s Threat Analysis Group and Samuel Groß of Google Project Zero on 2020-10-29
- [$NA][1144489] High CVE-2020-16011: Heap buffer overflow in UI on Windows. Reported by Sergei Glazunov of Google Project Zero on 2020-11-01
Google is aware of reports that an exploit for CVE-2020-16009 exists in the wild, and said thanks to all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.
As usual, ongoing internal Google security researcher work was responsible for a wide range of fixes:
[1144284] Various fixes from internal audits, fuzzing and other initiatives.
