← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2020-16010 exploited? Yes: in CISA KEV since 3 Nov 2021

Gociux · Google Chrome for Android UI · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2020-16010, Google Chrome for Android UI Heap Buffer Overflow Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 3 Nov 2021, 365 days after it was published. It affects Google Chrome for Android UI. If you run it, CISA's required action is: Apply updates per vendor instructions.

exploitedYesCISA KEV · 3 Nov 2021
ransomwareNot knownno confirmed use
EPSStop 10%more likely than most to be exploited
severity9.6CVSS 3.1 · critical
US federal due3 May 2022BOD 22-01 deadline

What it is

Google Chrome for Android UI contains a heap buffer overflow vulnerability that allows a remote attacker, who has compromised the renderer process, to potentially perform a sandbox escape via a crafted HTML page.

VendorGoogle (77 exploited CVEs in KEV)
ProductChrome for Android UI
VulnerabilityGoogle Chrome for Android UI Heap Buffer Overflow Vulnerability
WeaknessCWE-787
Published3 Nov 2020
Added to KEV3 Nov 2021
Reported by (CNA)Chrome

What to do

  1. Check whether you run it. Look for Chrome for Android UI in your asset inventory, including appliances and cloud images. Stack check lists every exploited Google CVE at once.
  2. Apply the fix. Apply updates per vendor instructions.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 3 Nov 2020.
  4. Get told next time. Email alerts when CISA adds a CVE for Google.

References

Questions

Is CVE-2020-16010 being exploited?

Yes. CISA added CVE-2020-16010 to the Known Exploited Vulnerabilities catalog on 3 Nov 2021, which means there is reliable evidence of exploitation in the wild.

Is CVE-2020-16010 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2020-16010?

Apply updates per vendor instructions. Check Google's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected Chrome for Android UI and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in November 2021 · Google scorecard · act-now radar.

Running Google in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →