basicsecurity.net
Proof, not just disclosure.
Threats / Google / CVE-2020-6572
CVE-2020-6572 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Google Chrome Media vulnerability

Google Chrome Media contains a use-after-free vulnerability allowing remote code execution through crafted HTML pages.

Verdict

Today item — known-exploited.

Use-after-free in Chrome Media enables unauthenticated remote attackers to achieve code execution by delivering malicious HTML. Active exploitation observed in the wild.

CISA KEV Yes · 2022-01-103EPSS 0.10586 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
2 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-01-10).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.10586 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Google, Chrome Media. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-416 Use After Free — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-416 · Use After FreeMemory safety
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious HTML page that triggers memory reuse in Chrome's media handling code.
Business
User visits attacker-controlled or compromised website without additional interaction required.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I exploit the use-after-free condition to corrupt memory and redirect execution flow to my payload.
Business
Attacker gains arbitrary code execution within the Chrome process with user privileges.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute malicious code on the victim's system to establish persistence or exfiltrate data.
Business
Confidentiality, integrity, and availability of user systems compromised; potential lateral movement to network resources.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 2 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by Chrome (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by ChromeCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.