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

Published Mar 2, 2020
·
Updated

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

Other sources

Multiple MediaTek chipsets contain an insufficient input validation vulnerability and have missing SELinux restrictions in the Command Queue drivers ioctl handlers. This causes an out-of-bounds write leading to privilege escalation. This vulnerability was observed chained with CVE-2019-2215 and CVE-2020-0041 under exploit chain "AbstractEmu."

CISA

Affected Software

79 affected components
MediaTek Multiple Chipsets
Google Android
Google Android
All of the following
Huawei Berkeley-l09 Firmware<10.0.0.177\(c10e3r1p4\)
Huawei Berkeley-L09
All of the following
Huawei Columbia-al10b Firmware<10.0.0.178\(c00e178r1p4\)
Huawei Columbia-AL10B
All of the following
Huawei Columbia-l29d Firmware<10.0.0.177\(c10e4r1p4\)
Huawei Columbia-L29D
All of the following
Huawei Columbia-tl00b Firmware<10.0.0.178\(c01e178r1p4\)
Huawei Columbia-TL00B
All of the following
Huawei Columbia-tl00d Firmware<10.0.0.178\(c01e178r1p4\)
Huawei Columbia-tl00d
All of the following
Huawei Cornell-al00a Firmware<9.1.0.340\(c00e333r1p1t8\)
Huawei Cornell-AL00A
All of the following
Huawei Cornell-tl10b Firmware<9.1.0.340\(c01e333r1p1t8\)
Huawei Cornell-tl10b
All of the following
Huawei Dura-al00a Firmware<1.0.0.190\(c00\)
Huawei Dura-al00a
All of the following
Huawei Honor 20 Pro Firmware<10.0.0.194\(c636e3r3p1\)
Huawei HONOR 20 PRO
All of the following
Huawei Y6 2019 Firmware<9.1.0.290\(c185e5r4p1\)
Huawei Y6 2019
All of the following
Huawei Nova 3 Firmware<9.1.0.338\(c00e333r1p1t8\)
Huawei Nova 3
All of the following
Huawei Nova 4 Firmware<10.0.0.160\(c01e32r2p4\)
Huawei nova 4
All of the following
Huawei Honor 8a Firmware<9.1.0.291\(c185e3r4p1\)
Huawei Honor 8A
All of the following
Huawei Honor View 20 Firmware<10.0.0.198\(c432e10r3p4\)
Huawei Honor View 20
All of the following
Huawei Jakarta-al00a Firmware<9.1.0.251\(c00e106r2p2\)
Huawei Jakarta-al00a
All of the following
Huawei Katyusha-al00a Firmware<9.1.0.146\(c00e131r2p2\)
Huawei Katyusha-al00a
All of the following
Huawei Katyusha-al10a Firmware<9.1.0.160\(c00e150r1p7\)
Huawei Katyusha-al10a
All of the following
Huawei Madrid-al00a Firmware<9.1.0.261\(c00e120r4p1\)
Huawei Madrid-al00a
All of the following
Huawei Paris-l29b Firmware<9.1.0.380\(c636e1r1p3t8\)
Huawei Paris-L29B
All of the following
Huawei Princeton-al10b Firmware<10.0.0.194\(c00e61r4p11\)
Huawei Princeton-AL10B
All of the following
Huawei Sydney-al00 Firmware<9.1.0.237\(c00e80r1p7t8\)
Huawei Sydney-AL00
All of the following
Huawei Sydney-tl00 Firmware<9.1.0.237\(c01e80r1p7t8\)
Huawei Sydney-tl00
All of the following
Huawei Sydneym-al00 Firmware<10.0.0.159\(c00e64r1p5\)
Huawei SydneyM-AL00
All of the following
Huawei Tony-al00b Firmware<10.1.0.137\(c00e137r2p11\)
Huawei Tony-AL00B
All of the following
Huawei Tony-tl00b Firmware<10.0.0.196\(c01e65r2p11\)
Huawei Tony-TL00B
All of the following
Huawei Yale-al00a Firmware<10.0.0.196\(c00e62r8p12\)
Huawei Yale-al00a
All of the following
Huawei Yale-l21a Firmware<10.0.0.202\(c10e3r3p2\)
Huawei Yale-L21A
All of the following
Huawei Yalep-al10b Firmware<10.0.0.194\(c00e62r8p12\)
Huawei YaleP-AL10B
All of the following
Huawei Columbia-l29d Firmware<10.0.0.177\(c432e3r1p4\)
Huawei Columbia-L29D
All of the following
Huawei Honor 20 Pro Firmware<10.0.0.202\(c10e3r3p2\)
Huawei HONOR 20 PRO
All of the following
Huawei Y6 2019 Firmware<9.1.0.290\(c431e1r1p8\)
Huawei Y6 2019
All of the following
Huawei Y6 2019 Firmware<9.1.0.290\(c605e6r1p6\)
Huawei Y6 2019
All of the following
Huawei Y6 2019 Firmware<9.1.0.295\(c431e5r2p2\)
Huawei Y6 2019
All of the following
Huawei Honor 8a Firmware<9.1.0.291\(c432e5r2p1\)
Huawei Honor 8A
All of the following
Huawei Honor 8a Firmware<9.1.0.291\(c636e4r4p1\)
Huawei Honor 8A
All of the following
Huawei Honor 8a Firmware<9.1.0.297\(c605e4r4p2\)
Huawei Honor 8A
All of the following
Huawei Honor View 20 Firmware<10.0.0.200\(c185e3r3p3\)
Huawei Honor View 20
All of the following
Huawei Honor View 20 Firmware<10.0.0.201\(c10e5r4p3\)
Huawei Honor View 20

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Implement SELinux (SEAndroid) policy rules to restrict which processes can invoke the MediaTek Command Queue driver's ioctl handlers. Specifically, create/modify SELinux rules to limit access to the driver/device nodes for the Mediatek Command Queue driver so only trusted system components can call its ioctls, mitigating the out-of-bounds write and local privilege escalation.

Event History

Mar 2, 2020
CVE Published
via Android·12:00 AM
Mar 10, 2020
CVE Published
via MITRE·07:56 PM
Data Sourced
via MITRE·07:56 PM
DescriptionWeakness
Data Sourced
via NVD·08:15 PM
DescriptionSeverityWeaknessAffected Software
Nov 3, 2021
Known Exploited
via CISA·12:00 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2020-0069?

The severity of CVE-2020-0069 is classified as critical due to the potential for local escalation of privilege.

2

How do I fix CVE-2020-0069?

To fix CVE-2020-0069, update the affected Mediatek Command Queue driver to the latest version that includes proper input sanitization and SELinux restrictions.

3

Who is affected by CVE-2020-0069?

CVE-2020-0069 affects devices running specific versions of Google Android and Mediatek multiple chipsets.

4

What types of devices are vulnerable to CVE-2020-0069?

Vulnerable devices include a variety of Huawei smartphones utilizing specific chipsets and firmware versions.

5

Is user interaction required to exploit CVE-2020-0069?

No, user interaction is not required to exploit CVE-2020-0069 as it allows for local privilege escalation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203