Patchfirst
CVE-2020-15999 KEVPublic exploit Critical · 9.6 EPSS 63.9%

Google Chrome FreeType Heap Buffer Overflow Vulnerability

Google · Chrome FreeType

Summary

The Freetype font rendering component in Google Chrome contains a heap buffer overflow that can lead to heap corruption. An attacker who can get a victim to open a crafted HTML page can potentially exploit this flaw, requiring only network delivery of the page and user interaction (visiting the page) with no authentication.

Official description · NVD

Heap buffer overflow in Freetype in Google Chrome prior to 86.0.4240.111 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Breakdown
69.6 / 100
Exploited
Yes, in CISA KEV
Reports
0
Tactics
2/15

How an attack unfolds

Based on mappings. Select a step to see the evidence.
  1. How attackers get in

  2. What they do

First seen exploited 15 days before it was disclosed. Public exploit code (PoC-in-GitHub) appeared 1 day after disclosure.

  1. First seen exploitedVulnCheck KEV evidence15 days before
  2. Disclosedday 0
  3. Public exploit codePoC-in-GitHub+1 day
  4. Added to CISA KEVEU database agrees+12 mo

CISA KEV listing is when exploitation was confirmed, not necessarily the first attack.

techniques

2 , grouped by in kill-chain order, 2 cited passages 2

Initial AccessTA0001

Drive-by Compromise T1189 Medium
AI mapping from the description · how it is exploited

Malicious webpage delivers exploit to victim browser

via a crafted HTML page
From the official description (NVD) Original (opens in a new tab) ↗

ExecutionTA0002

Exploitation for Client Execution T1203 Medium
AI mapping from the description · primary impact

Heap overflow in browser yields code execution

Heap buffer overflow in Freetype in Google Chrome
From the official description (NVD) Original (opens in a new tab) ↗

Detection

0 rules for this CVE · 38 general rules for its techniques

Rules for this CVE

0 that reference CVE-2020-15999 directly.

CVE-specific rules are not available in this build. Search SigmaHQ ↗

General rules for this CVE’s techniques

These detect the technique in general, not this specific vulnerability.

Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.

Am I affected? What do I upgrade to?

From GitHub Security Advisories and OSV

4 packages in 1 ecosystem. No single main package: each of these ships the affected code.

  • NuGetCefSharp.Common
    Affected: All versions before 85.3.130Upgrade to 85.3.130 or later
  • NuGetCefSharp.Wpf
    Affected: All versions before 85.3.130Upgrade to 85.3.130 or later
  • NuGetCefSharp.WinForms
    Affected: All versions before 85.3.130Upgrade to 85.3.130 or later
  • NuGetCefSharp.Wpf.HwndHost
    Affected: All versions before 85.3.130Upgrade to 85.3.130 or later

Check your lockfile against all CVEs

What security researchers reported

Not named in any threat report yet

Also mentioned in 50 community threat pulses (AlienVault OTX)

Weaker evidence

Pulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.

References

12 links, grouped by NVD tag (10 duplicates merged)
↑ ↓ chooseEnter openEsc close