dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 May 2022.
AndroidOperating system · Google

CVE-2020-0069

HIGH · 7.8 CVSS v3.1 Published 2020-03-10
Fix available
A fix is available. Upgrade to 9.1.0.340 / 10.0.0.177 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Out of bounds write vulnerability in the Mediatek Command Queue driver's ioctl handlers due to insufficient input sanitization, combined with missing SELinux restrictions, allowing local privilege escalation without user interaction or additional execution privileges.

MitigationApply Android kernel security patches that address the Mediatek Command Queue driver vulnerability (A-147882143) and ensure SELinux policies are properly configured to restrict driver ioctl access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:all versions
Berkeley L09 FirmwareOperating system
Affected:< 10.0.0.177\(c10e3r1p4\)
Columbia Al10b FirmwareOperating system
Affected:< 10.0.0.178\(c00e178r1p4\)
Columbia L29d FirmwareOperating system
Affected:< 10.0.0.177\(c10e4r1p4\)< 10.0.0.177\(c432e3r1p4\)
Columbia Tl00b FirmwareOperating system
Affected:< 10.0.0.178\(c01e178r1p4\)
Columbia Tl00d FirmwareOperating system
Affected:< 10.0.0.178\(c01e178r1p4\)
Cornell Al00a FirmwareOperating system
Affected:< 9.1.0.340\(c00e333r1p1t8\)
Cornell Tl10b FirmwareOperating system
Affected:< 9.1.0.340\(c01e333r1p1t8\)

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Mediatek chipset usage
    Check system information or /proc/cpuinfo for Mediatek MTK processor identifier, or check /sys/class/socinfo for mediatek platform
    Affected if Device contains a Mediatek chipset and the vulnerable driver is present
  2. Verify Android version
    Check Settings > About Phone > Android version or run 'getprop ro.build.version.release'
    Affected if Android version is any version (all versions affected per CVE)
  3. Confirm Huawei firmware version
    Check Settings > About Phone > Version or run 'getprop ro.build.display.id' and compare against the specific build numbers for your model (e.g., < 10.0.0.177 for Berkeley L09)
    Affected if Running a Huawei model listed in affected products with firmware below the specified patch version
  4. Check if Mediatek Command Queue driver is loaded
    Run 'lsmod | grep cmdq' or check /sys/module/ for mtk_cmdq or cmdq modules
    Affected if The mtk_cmdq driver module is loaded in memory
  5. Inspect SELinux policy restrictions on cmdq driver
    Run 'getenforce' to check SELinux status, then review /sys/fs/selinux/policy or use 'sestatus' to verify driver ioctl access restrictions
    Affected if SELinux is disabled, permissive, or the cmdq driver lacks proper SELinux policy constraints

The device is affected if it uses a Mediatek chipset with the Command Queue driver and either runs any Android version on Huawei firmware below the patched versions or has SELinux restrictions missing on the cmdq driver.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.1.0.340 / 10.0.0.177 / 10.0.0.178 or later
Fixed in 9.1.0.34010.0.0.17710.0.0.178
Interim mitigation

Apply Android kernel security patches that address the Mediatek Command Queue driver vulnerability (A-147882143) and ensure SELinux policies are properly configured to restrict driver ioctl access.

Recommended fix Moderate confidence

Android: March 2020 Security Patch Level or later; Huawei: Firmware versions specified above (10.0.0.177/178 or 9.1.0.340 depending on model)

  1. 1. For Android devices: Update to the latest Android security patch level (March 2020 or later) which contains the fix for CVE-2020-0069
  2. 2. For Huawei devices: Update firmware to version 10.0.0.177(c10e3r1p4) or later for Berkeley L09
  3. 3. For Huawei devices: Update firmware to version 10.0.0.178(c00e178r1p4) or later for Columbia Al10b, Columbia Tl00b, Columbia Tl00d
  4. 4. For Huawei devices: Update firmware to version 10.0.0.177(c10e4r1p4) or later for Columbia L29d
  5. 5. For Huawei devices: Update firmware to version 9.1.0.340(c00e333r1p1t8) or later for Cornell Al00a
  6. 6. For Huawei devices: Update firmware to version 9.1.0.340(c01e333r1p1t8) or later for Cornell Tl10b
  7. 7. After updating, verify the security patch level in Settings > About Phone > Security Patch Level
Caveat Users should ensure backup of important data before firmware update; some older devices may not receive updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-0069 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-0069 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data