CVE-2020-16010: Google Chrome for Android UI Heap Buffer Overflow Vulnerability
CVE-2020-16010 · Severity: critical · CVSS 9.6 · Exploited in the wild · Published 2021-11-03
A heap buffer overflow vulnerability exists in the UI component of Google Chrome for Android. A remote attacker who has already compromised the renderer process can exploit this flaw via a crafted HTML page to perform a sandbox escape.
Yes. CVE-2020-16010 is known to be exploited in the wild, first recorded on 3 November 2021. Treat it as urgent.
How severe is CVE-2020-16010?
Critical severity, with a CVSS score of 9.6, published 3 November 2021.
Which products and versions are affected?
Google Chrome prior to 86.0.4240.185.
Is there a fix for CVE-2020-16010?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2020-16010 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2020-16010?
Check whether you run Google Chrome For Android Ui. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Affected products
Google Chrome prior to 86.0.4240.185
Timeline
2020-11-02: disclosed: NVD Published Date
2021-11-03: kev added: Date added to CISA Known Exploited Vulnerabilities Catalog
2020-11-02: exploited: Reported as exploited in the wild at time of disclosure