CVE-2020-16010 Google Chrome for Android UI: memory-safety flaw
In plain words: The program mishandles the memory it uses to keep track of data. A specially made input can scramble that memory. Usually lets an attacker crash the program or run their own code with its permissions.
Confirmed exploited by CISA on · US federal patch deadline May 3, 2022
What to do
- Install Google's security update for Chrome for Android UI. If no update exists, follow the vendor's workaround or stop using the product until one ships.
- Let the browser auto-update and relaunch it when it asks — the fix is not active until you do.
- Keep extensions to a minimum and remove ones you do not recognise.
- Stop using Internet Explorer and any browser that no longer gets updates.
Who is affected
Could reach you. This one is aimed at devices or apps of the kind people own.
What's at risk: A malicious or hacked website can be enough. Browser bugs are often the first step in a longer attack on the whole computer or phone.
The details
- Official name
- Google Chrome for Android UI Heap Buffer Overflow Vulnerability
- Product
- Google Chrome for Android UI
- CISA description
- 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.
- Type of flaw
- Memory-safety flaw (CWE-787)
- Confirmed exploited
- Nov 3, 2021
- US federal patch deadline
- May 3, 2022
Ask Cleus about it
Ask about a vulnerability, an update, a weird message, or the news. Plain-word answers, free, no account.
Answering about CVE-2020-16010 ·
Questions about CVE-2020-16010
Is CVE-2020-16010 being exploited?
Yes. CISA added CVE-2020-16010 to its Known Exploited Vulnerabilities catalog on Nov 3, 2021, which means there is reliable evidence of real-world attacks.
How do I fix CVE-2020-16010?
Install Google's security update for Chrome for Android UI. If no update exists, follow the vendor's workaround or stop using the product until one ships. Let the browser auto-update and relaunch it when it asks — the fix is not active until you do.
Am I affected by CVE-2020-16010?
Only if you use Google Chrome for Android UI. This one is aimed at devices or apps of the kind people own.