Skip to content
Fencer Intel
high 8.8

CVE-2020-16013 kev in the critical feed json

Inappropriate implementation in V8 in CefSharp

published 5y ago modified 4mo ago also GHSA-x7fx-mcc9-27j7 , EUVD-2020-1474

cvss
8.8
version 3.1, CNA
cisa kev
Exploited
added 2021-11-03
epss
2.8%
EPSS 2.8% chance of exploitation in 30 days, percentile 86%
public exploits
0
none known

Summary

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.

Patch / fix

cisa required action Apply updates per vendor instructions.

  • nuget CefSharp.Common 86.0.241
  • nuget CefSharp.Wpf 86.0.241
  • nuget CefSharp.WinForms 86.0.241
  • nuget CefSharp.Wpf.HwndHost 86.0.241
  • Google Chrome 86.0.4240.198
  • chromium Debian 14, Debian 13, Debian 12 87.0.4280.88-0.1

debian advisories DEBIAN-CVE-2020-16013

  • chromium-browser Ubuntu 16.04 LTS 86.0.4240.198-0ubuntu0.16.04.1
  • chromium-browser Ubuntu 18.04 LTS 86.0.4240.198-0ubuntu0.18.04.1

ubuntu advisories UBUNTU-CVE-2020-16013

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • chromium-browser RHEL 6 EXTRAS 86.0.4240.198-1.el6_10

red hat advisories RHSA-2020:5165

  • chromium openSUSE Tumbleweed 93.0.4577.82-1.1
  • chromium openSUSE Tumbleweed 113.0.5672.92-1.1
  • opera openSUSE Leap 15.2 NonFree, openSUSE Leap 15.1 NonFree 72.0.3815.400-lp152.2.24.1
  • chromium Package Hub 15 SP2 86.0.4240.198-bp152.2.35.1
  • chromium Package Hub 15 SP1 86.0.4240.198-bp151.3.134.1
  • chromium Package Hub 15 SP1 86.0.4240.198-bp151.3.128.1
  • chromium Package Hub 15 SP2, Package Hub 15 SP1, openSUSE Leap 15.2 +1 more 86.0.4240.198-bp152.2.29.1

opensuse advisories openSUSE-SU-2024:10681-1openSUSE-SU-2024:12948-1openSUSE-SU-2020:2178-1openSUSE-SU-2020:2016-1openSUSE-SU-2020:2013-1openSUSE-SU-2020:1943-1

  • chromium Arch Linux 86.0.4240.198-1

arch linux advisories AVG-1981

Is CVE-2020-16013 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-16013 updated cvss 8.8

chromium-browser: Inappropriate implementation in V8

  • Red Hat Enterprise Linux Desktop Supplementary (v. 6) chromium-browser 86.0.4240.198-1.el6_10 Red Hat Enterprise Linux HPC Node Supplementary (v. 6) chromium-browser 86.0.4240.198-1.el6_10 Red Hat Enterprise Linux Server Supplementary (v. 6) chromium-browser 86.0.4240.198-1.el6_10 Red Hat Enterprise Linux Workstation Supplementary (v. 6) chromium-browser 86.0.4240.198-1.el6_10
    fixed: vendor fix RHSA-2020:5165

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

cisa ICSA-23-264-05 updated cvss 8.8

Rockwell Automation Connected Components Workbench

  • Rockwell Automation Connected Components Workbench < R21
    affected: vendor fix, mitigation “Customers using the affected software are encouraged to apply the risk mitigations, if possible.” compatibility.rockwellautomation.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Timeline

  1. Found exploited as a 0-day (Project Zero)
  2. 0-day patched (Project Zero)
  3. Published
  4. Added to CISA KEV
  5. CISA patch deadline
  6. CISA SSVC: exploitation active

Known exploited

Added
5y ago
Patch by
2022-05-03 (4y ago)
Ransomware
Not known
Required action
Apply updates per vendor instructions.
Vendor, product
Google, Chromium V8
CISA name
Google Chromium V8 Incorrect Implementation Vulnerabililty

Zero-day

Detected in real attacks while still unknown to the vendor and the public, per Google Project Zero's 0day In-the-Wild tracker.

Found
2020-11-09
Patched
2020-11-11
Details
project zero tracker

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

2.76% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected packages

ecosystem package affected fixed in
nuget CefSharp.Common
<86.0.241
86.0.241
nuget CefSharp.Wpf
<86.0.241
86.0.241
nuget CefSharp.WinForms
<86.0.241
86.0.241
nuget CefSharp.Wpf.HwndHost
<86.0.241
86.0.241

Affected products

  • Google Chrome

Classification

Weakness
  • CWE-787 Out-of-bounds Write
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.