Exploit / PoCcriticalExploited in the wild

Google addresses Chrome zero

Security Affairsby @securityaffairsFeb 4, 2021 · 23:51 UTC (Feb 4, 2021)2 min read7 · 3 reads

Read at securityaffairs.com

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

CVEs: CVE-2021-21148 CVE-2020-15999 CVE-2020-16009 CVE-2020-16010 CVE-2020-16013 CVE-2020-16017

Tags: cve-2021-21148 cve-2020-15999 cve-2020-16009 cve-2020-16010 cve-2020-16013 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-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-16013	Heap Corruption in Google Chrome V8 Engine (CVE-2020-16013) Under Active Attack	8.8	3%	KEV	Jan 8, 2021 KEV Nov 3, 2021
CVE-2020-16017	Use-After-Free Sandbox Escape in Google Chrome	9.6	3%	KEV	Jan 8, 2021 KEV Nov 3, 2021
CVE-2021-21148	Heap Buffer Overflow in Google Chrome/Chromium V8 (CVE-2021-21148)	8.8	20%	KEV	Feb 9, 2021 KEV Nov 3, 2021

From the original article

2 min read at securityaffairs.com

Google has addressed an actively exploited zero-day vulnerability, tracked as CVE-2021-21148, with the release of the Chrome 88. 0. 4324.

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.