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

MediaTek Multiple Chipsets vulnerability

Multiple MediaTek chipsets contain insufficient input validation in Command Queue driver ioctl handlers, enabling out-of-bounds write and privilege escalation. Observed in active exploit chains.

Verdict

Today item — known-exploited.

Out-of-bounds write vulnerability in MediaTek chipset drivers allows local privilege escalation through improper ioctl input validation and missing SELinux restrictions. Actively exploited in coordinated attack chains targeting Android devices.

CISA KEV Yes · 2021-11-033EPSS 0.01299 (verify live)4Exploit Public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
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 2021-11-03).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.01299 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: MediaTek, Multiple Chipsets. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-787 Out-of-bounds Write — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-787 · Out-of-bounds WriteMemory 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
Craft malicious ioctl command with oversized buffer to trigger out-of-bounds write in Command Queue driver.
Business
Attacker gains kernel-level code execution on affected device.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
Escalate privileges by overwriting kernel memory structures and bypassing SELinux policy enforcement.
Business
Complete device compromise with unrestricted system access and ability to persist malware.
3

Lateral reach — past segmentation narrative 3

Attacker
Chain exploit with CVE-2019-2215 and CVE-2020-0041 to establish multi-stage attack infrastructure.
Business
Coordinated compromise of device fleet enables large-scale data exfiltration and lateral movement.
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)
  • Public PoC available (VulnCheck)
  • 2 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by google_android (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 google_androidCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.