# CVE-2020-0069: Mediatek Multiple Chipsets Insufficient Input Validation

> Local attackers can escalate privileges via an out-of-bounds write in the Mediatek Command Queue driver due to insufficient input sanitization.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2020
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-xx48-fp29-wh9j

## What is CVE-2020-0069?

CVE-2020-0069 is a high-severity memory corruption vulnerability in Google Android, published on 10 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the ioctl handlers of the Mediatek Command Queue driver, there is a possible out of bounds write due to insufficient input sanitization and missing SELinux restrictions. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-147882143References: M-ALPS04356754

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2020-0069?

It affects 29 products.


Products: Google Android, Huawei Berkeley-L09 Firmware, Huawei Columbia-Al10b Firmware, Huawei Columbia-L29d Firmware, Huawei Columbia-Tl00b Firmware, Huawei Columbia-Tl00d Firmware, Huawei Cornell-Al00a Firmware, Huawei Cornell-Tl10b Firmware, Huawei Dura-Al00a Firmware, Huawei Honor 20 Pro Firmware, Huawei Honor 8a Firmware, Huawei Honor View 20 Firmware, Huawei Jakarta-Al00a Firmware, Huawei Katyusha-Al00a Firmware, Huawei Katyusha-Al10a Firmware, Huawei Madrid-Al00a Firmware, Huawei Nova 3 Firmware, Huawei Nova 4 Firmware, Huawei Paris-L29b Firmware, Huawei Princeton-Al10b Firmware and 9 more.

## How do I fix CVE-2020-0069?

No fix has been published for CVE-2020-0069 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2020-0069 being exploited?

Yes. Attackers have exploited CVE-2020-0069 in the wild since at least 3 Nov 2021.

Public exploit code:

- Root your MediaTek device with CVE-2020-0069 (github_poc): https://github.com/R0rt1z2/AutomatedRoot
- https://github.com/quarkslab/CVE-2020-0069_poc (github_poc): https://github.com/quarkslab/CVE-2020-0069_poc
- reversing mtk-su (github_poc): https://github.com/TheRealJunior/mtk-su-reverse-cve-2020-0069
- CVE-2020-0069 (github_poc): https://github.com/0xf15h/mtk_su

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-0069 and fix it if it is affected.

What it is: CVE-2020-0069 is a high-severity memory corruption vulnerability in Google Android, published on 10 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2020-0069 in the wild since at least 3 Nov 2021.

Affected product: Google Android. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-0069/ (Markdown: https://insights.sbomify.com/CVE-2020-0069/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-0069
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-0069
- OSV: https://osv.dev/vulnerability/CVE-2020-0069

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-0069/
Summaries are generated and may contain mistakes; the official description above is the record.