CVE-2016-1646 Google Chromium V8: 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 Jun 22, 2022
What to do
- Install Google's security update for Chromium V8. 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 Chromium V8 Out-of-Bounds Read Vulnerability
- Product
- Google Chromium V8
- CISA description
- Google Chromium V8 Engine contains an out-of-bounds read vulnerability that allows a remote attacker to cause a denial of service or possibly have another unspecified impact via crafted JavaScript code. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.
- Type of flaw
- Memory-safety flaw (CWE-119)
- Confirmed exploited
- Jun 8, 2022
- US federal patch deadline
- Jun 22, 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-2016-1646 ·
Questions about CVE-2016-1646
Is CVE-2016-1646 being exploited?
Yes. CISA added CVE-2016-1646 to its Known Exploited Vulnerabilities catalog on Jun 8, 2022, which means there is reliable evidence of real-world attacks.
How do I fix CVE-2016-1646?
Install Google's security update for Chromium V8. 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-2016-1646?
Only if you use Google Chromium V8. This one is aimed at devices or apps of the kind people own.