First published: Sun Sep 06 2020(Updated: )
Inappropriate implementation in Blink in Google Chrome prior to 86.0.4240.111 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Credit: amaebi_jp chrome-cve-admin@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
Google Chrome | <86.0.4240.111 | 86.0.4240.111 |
Google Chrome | <86.0.4240.111 | |
Fedoraproject Fedora | =31 | |
Fedoraproject Fedora | =32 | |
Fedoraproject Fedora | =33 | |
openSUSE Backports SLE | =15.0-sp2 | |
Debian Debian Linux | =10.0 | |
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 |
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-16000 is a vulnerability in Blink in Google Chrome prior to 86.0.4240.111 that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.
CVE-2020-16000 affects Google Chrome versions prior to 86.0.4240.111.
CVE-2020-16000 has a severity value of 8.8, which is considered high.
To fix CVE-2020-16000, update Google Chrome to version 86.0.4240.111 or later.
Yes, you can find references for CVE-2020-16000 at the following links: [1] http://lists.opensuse.org/opensuse-security-announce/2020-11/msg00016.html [2] https://chromereleases.googleblog.com/2020/10/stable-channel-update-for-desktop_20.html [3] https://crbug.com/1125337