First published: Thu Nov 19 2020(Updated: )
Insufficient data validation in V8 in Google Chrome prior to 87.0.4280.88 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Credit: chrome-cve-admin@google.com Lucas Pinheiro Microsoft Browser Vulnerability Research
Affected Software | Affected Version | How to fix |
---|---|---|
debian/chromium | 90.0.4430.212-1~deb10u1 116.0.5845.180-1~deb11u1 120.0.6099.129-1~deb11u1 119.0.6045.199-1~deb12u1 120.0.6099.129-1~deb12u1 120.0.6099.129-1 | |
Google Chrome (Trace Event) | <87.0.4280.88 | 87.0.4280.88 |
Google Chrome (Trace Event) | <87.0.4280.88 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Found alongside the following vulnerabilities)
CVE-2020-16040 is categorized as a critical vulnerability due to potential remote code execution risks.
The recommended fix for CVE-2020-16040 is to upgrade to the latest version of Google Chrome or Chromium above 87.0.4280.88.
CVE-2020-16040 affects Google Chrome versions prior to 87.0.4280.88 and specific versions of the Chromium browser.
Yes, CVE-2020-16040 can be exploited via crafted HTML pages that cause heap corruption.
Exploitation of CVE-2020-16040 could allow an attacker to execute arbitrary code in the context of the affected browser.