Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2020-0069: Local privilege escalation in MediaTek Command Queue driver

Published Mar 10, 2020 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS1.4%73rd percentile
CISA KEVYesAdded Nov 3, 2021
In the wildActivePer CISA KEV
Vendors
GoogleHuawei Technologies
IdentifiersCVE-2020-0069CWE-787 · Out-of-bounds Write

CVE-2020-0069 is an out-of-bounds write vulnerability in the ioctl handlers of the MediaTek Command Queue driver in the Android kernel. Insufficient input sanitization and missing SELinux restrictions allow local privilege escalation without additional execution privileges or user interaction. The AbstractEmu Android malware family exploited this vulnerability as part of its rooting functionality.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can elevate an unprivileged local execution context to privileged access on an affected Android device. AbstractEmu used this vulnerability among its rooting exploits; the campaign's resulting root access enabled silent software installation, permission grants, security-setting changes, and access to other applications' sensitive data. The precise privileges and memory-corruption effects of this individual exploit are not further specified.

Mitigation

If you can’t patch tonight, do this now.

Mitigation includes applying the latest Android security updates, restricting app installations to trusted sources (such as the Google Play Store), and monitoring for indicators of compromise. Enterprises should enforce mobile device management policies to prevent installation of untrusted apps and monitor for signs of rooting or privilege escalation.

Remediation

Patch, then assume compromise.

The vulnerability was addressed by Google and Mediatek via security updates to the Android kernel, which included proper input validation in the ioctl handlers and improved SELinux policy enforcement. Users should update their devices to the latest available security patch level to remediate this vulnerability.

Public exploits

Exploits

3 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
AutomatedRootThis repository is an operational exploit toolkit for rooting MediaTek-based Android devices vulnerable to CVE-2020-0069 (mtk-su). The main entry point is 'mtk-su.py', a Python script that interacts with the device via ADB using the pure-python-adb library. The toolkit supports both system-mode (SuperSU) and bootless-mode (Magisk) rooting, as well as an unroot option. The exploit works by pushing architecture-specific binaries and shell scripts to the device, then executing them to gain root privileges. The scripts handle remounting system partitions, copying and installing root binaries, patching SELinux, and managing root management apps. The repository is structured with Python modules for device interaction and configuration, and shell scripts for on-device actions. No network endpoints are present; all actions are performed locally via ADB. The exploit is not part of a framework and is operational, requiring user interaction and device access. The main targets are MediaTek Android devices with vulnerable SoCs, and the result is root access with the option to install Magisk or SuperSU, or to unroot the device.R0rt1z2 · Disclosed Sep 6, 2019 · python · shell · localOperationalmtk_suThis repository implements a local privilege escalation (LPE) exploit for CVE-2020-0069, targeting MediaTek-based Android devices (such as the MT6739 SoC) running vulnerable kernels (tested on Android 8.1.0). The exploit is written in C++ and is structured as a standalone binary, with the main entry point in src/main.cpp. The codebase is modular, with separate components for kernel symbol resolution (kallsyms), SELinux status manipulation, and process credential escalation. The exploit works by leveraging a vulnerability in the MediaTek command queue (cmdq) driver to gain arbitrary kernel read/write access. It then disables SELinux enforcing mode by directly modifying kernel memory and overwrites the current process's credentials with those of the root process, effectively granting root privileges. Finally, it spawns a root shell (/system/bin/sh) for the attacker. The exploit requires building with the Android NDK and running on a compatible, vulnerable device. Notable fingerprintable endpoints include the SELinux enforcement file and the system shell path. The code is operational and provides a working root shell if successful.0xf15h · Disclosed Sep 4, 2023 · c++ · cmake · localOperationalCVE-2020-0069_pocThis repository provides a proof-of-concept (PoC) exploit for CVE-2020-0069, targeting the Xiaomi Redmi 6a (Mediatek MT6762M SoC) running a vulnerable Android kernel. The exploit consists of: - A C program (kernel_rw.c) that enables arbitrary kernel memory read/write by exploiting the /dev/mtk_cmdq device driver. - A shell script (poc.sh) that automates the process of locating the kernel version string in memory, patching it, and writing it back to demonstrate the exploit's capabilities. - A C shared library (syscall_hook.c) for tracing the mtk-su binary, which is not the main exploit but aids in analysis. The repository is structured with JNI source files (C code and Mediatek header files) under the jni/ directory, a build system for Android NDK, and the PoC script at the root. The exploit demonstrates the ability to read and write arbitrary kernel memory, which can be leveraged for privilege escalation or further attacks. The main attack vector is local, requiring code execution on the target device (e.g., via adb shell). The exploit is a functional PoC and not weaponized, as it requires manual steps and is tailored for research and demonstration purposes.quarkslab · Disclosed Mar 24, 2020 · c · bash · localPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleAndroidoperating_system
Huawei TechnologiesBerkeley-L09 Firmwareoperating_system
Huawei TechnologiesColumbia-Al10b Firmwareoperating_system
Huawei TechnologiesColumbia-L29d Firmwareoperating_system
Huawei TechnologiesColumbia-Tl00b Firmwareoperating_system
Huawei TechnologiesColumbia-Tl00d Firmwareoperating_system
Huawei TechnologiesCornell-Al00a Firmwareoperating_system
Huawei TechnologiesCornell-Tl10b Firmwareoperating_system
Huawei TechnologiesDura-Al00a Firmwareoperating_system
Huawei TechnologiesHonor 20 Pro Firmwareoperating_system
Huawei TechnologiesHonor 8a Firmwareoperating_system
Huawei TechnologiesHonor View 20 Firmwareoperating_system
Huawei TechnologiesJakarta-Al00a Firmwareoperating_system
Huawei TechnologiesKatyusha-Al00a Firmwareoperating_system
Huawei TechnologiesKatyusha-Al10a Firmwareoperating_system
Huawei TechnologiesMadrid-Al00a Firmwareoperating_system
Huawei TechnologiesNova 3 Firmwareoperating_system
Huawei TechnologiesNova 4 Firmwareoperating_system
Huawei TechnologiesParis-L29b Firmwareoperating_system
Huawei TechnologiesPrinceton-Al10b Firmwareoperating_system
Huawei TechnologiesSydney-Al00 Firmwareoperating_system
Huawei TechnologiesSydney-Tl00 Firmwareoperating_system
Huawei TechnologiesSydneym-Al00 Firmwareoperating_system
Huawei TechnologiesTony-Al00b Firmwareoperating_system
Huawei TechnologiesTony-Tl00b Firmwareoperating_system
Huawei TechnologiesY6 2019 Firmwareoperating_system
Huawei TechnologiesYale-Al00a Firmwareoperating_system
Huawei TechnologiesYale-L21a Firmwareoperating_system
Huawei TechnologiesYalep-Al10b Firmwareoperating_system
FAQ

Frequently asked questions

Is CVE-2020-0069 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 3, 2021.
Is there a public exploit for CVE-2020-0069?
Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2020-0069, the earliest disclosed Sep 6, 2019.
Is there a patch for CVE-2020-0069?
The vulnerability was addressed by Google and Mediatek via security updates to the Android kernel, which included proper input validation in the ioctl handlers and improved SELinux policy enforcement. Users should update their devices to the latest available security patch level to remediate this vulnerability.
What products are affected by CVE-2020-0069?
Google Android, Huawei Technologies Berkeley-L09 Firmware, Huawei Technologies Columbia-Al10b Firmware, Huawei Technologies Columbia-L29d Firmware, Huawei Technologies Columbia-Tl00b Firmware, and at least 24 more.
How severe is CVE-2020-0069?
CVE-2020-0069 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 1.4% (73rd percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.