Exploit / PoCcriticalExploited in the wild

Google fixes the second zero-day in Chrome in 2 weeks actively exploited

Security Affairsby @securityaffairsNov 3, 2020 · 08:25 UTC (Nov 3, 2020)3 min read2 · 1 read

Read at securityaffairs.com

Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

CVEs: CVE-2020-16009 CVE-2020-16010 CVE-2020-16004 CVE-2020-16005 CVE-2020-16006 CVE-2020-16007 CVE-2020-16008 CVE-2020-16011 CVE-2020-17087 CVE-2020-15999

Tags: cve-2020-16009 cve-2020-16010 cve-2020-16004 cve-2020-16005 cve-2020-16006 exploit

Vulnerabilities mentioned

All

CVE	Vulnerability	CVSS	EPSS	Signals	Published
CVE-2020-15999	Heap Buffer Overflow in FreeType Font Rendering in Google Chrome (CVE-2020-15999)	9.6	64%	KEVPoC ×2	Nov 3, 2020 KEV Nov 3, 2021
CVE-2020-16011 +5 related CVEs CVE-2020-16006 CVE-2020-16005 CVE-2020-16004 CVE-2020-16008 CVE-2020-16007	Heap buffer overflow in UI in Google Chrome on Windows prior to 86.0.4240.183 allowed a remote attacker who had compromised the renderer process to potentially…	9.6 group max	2%		Nov 3, 2020
CVE-2020-16009	Type Confusion in Google Chromium V8 Engine Enables RCE via Crafted HTML Pages	8.8	48%	KEVPoC ×2	Nov 3, 2020 KEV Nov 3, 2021
CVE-2020-16010	Heap Buffer Overflow in Google Chrome for Android Enables Sandbox Escape	9.6	6%	KEV	Nov 3, 2020 KEV Nov 3, 2021
CVE-2020-17087	Windows Kernel Buffer Overflow Enables Local Privilege Escalation (CVE-2020-17087)	7.8	5%	KEV	Nov 11, 2020 KEV Nov 3, 2021

From the original article

3 min read at securityaffairs.com

Google released Chrome 86. 0. 4240.

Security Affairs

By @securityaffairs · securityaffairs.com

Read the full article at Security Affairs

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.