← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

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

Gociux · Google Chromium V8 · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2020-16009, Google Chromium V8 Type Confusion 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 Chromium V8. If you run it, CISA's required action is: Apply updates per vendor instructions.

exploitedYesCISA KEV · 3 Nov 2021
ransomwareNot knownno confirmed use
EPSStop 5%very likely to be exploited
severity8.8CVSS 3.1 · high
US federal due3 May 2022BOD 22-01 deadline

What it is

Google Chromium V8 Engine contains a type confusion vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.

VendorGoogle (77 exploited CVEs in KEV)
ProductChromium V8
VulnerabilityGoogle Chromium V8 Type Confusion Vulnerability
WeaknessCWE-787, CWE-843
Published3 Nov 2020
Added to KEV3 Nov 2021
Reported by (CNA)Chrome

What to do

  1. Check whether you run it. Look for Chromium V8 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.

Other exploited CVEs in Chromium V8

References

Questions

Is CVE-2020-16009 being exploited?

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

Is CVE-2020-16009 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-16009?

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 Chromium V8 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 →