CVE-2020-16013 Google Chromium V8 Incorrect Implementation Vulnerabililty
A remote attacker can exploit heap corruption in the V8 engine via a crafted HTML page, potentially executing arbitrary code.
- Exploited in the wild
- Since 3 Nov 2021
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2020-16013?
CVE-2020-16013 is a high-severity memory corruption vulnerability in Google Chrome, published on 8 Jan 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
Inappropriate implementation in V8 in Google Chrome prior to 86.0.4240.198 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Weakness: CWE-787
Which versions are affected by CVE-2020-16013?
8 open source packages ship an affected version, including CefSharp.Common, CefSharp.WinForms and CefSharp.Wpf. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
CefSharp.Common NuGet | All versions | 86.0.241 |
CefSharp.Common NuGet | All versions | 86.0.241 |
CefSharp.WinForms NuGet | All versions | 86.0.241 |
CefSharp.WinForms NuGet | All versions | 86.0.241 |
CefSharp.Wpf NuGet | All versions | 86.0.241 |
CefSharp.Wpf NuGet | All versions | 86.0.241 |
2 more packages
CefSharp.Wpf.HwndHost NuGet | All versions | 86.0.241 |
CefSharp.Wpf.HwndHost NuGet | All versions | 86.0.241 |
Products include Google Chrome.
How do I fix CVE-2020-16013?
Upgrade CefSharp.Common to 86.0.241 or later. US federal agencies must fix it by 3 May 2022.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2020-16013 being exploited?
Yes. Attackers have exploited CVE-2020-16013 in the wild since at least 3 Nov 2021.
Other vulnerabilities in Google Chrome
Sources
Also known as DEBIAN-CVE-2020-16013, GHSA-x7fx-mcc9-27j7, UBUNTU-CVE-2020-16013.