CVE-2020-0069 · Severity: critical · CVSS 7.8 · Exploited in the wild · Published 2021-11-03
MediaTek Command Queue drivers contain an out-of-bounds write vulnerability due to insufficient input validation and missing SELinux restrictions in ioctl handlers. This flaw allows a local attacker to escalate privileges without user interaction. The vulnerability has been observed in the wild as part of the 'AbstractEmu' exploit chain.
Quick answers
Is CVE-2020-0069 exploited in the wild?
Yes. CVE-2020-0069 is known to be exploited in the wild, first recorded on 3 November 2021. Treat it as urgent.
How severe is CVE-2020-0069?
Critical severity, with a CVSS score of 7.8, published 3 November 2021.
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2020-0069 attacked?
It is attacked with local access, in an operating system.
Am I affected by CVE-2020-0069?
Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Affected products
Google Android kernel Android kernel
MediaTek Command Queue driver
MediaTek Multiple Chipsets
Timeline
2020-03-01: advisory: Android Security Bulletin - March 2020
2021-11-03: kev added: Added to CISA Known Exploited Vulnerabilities Catalog