How severe is CVE-2020-0069?

CVE-2020-0069 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-0069?

Affected package information for CVE-2020-0069 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2020-0069?

No fixed release is recorded for CVE-2020-0069 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2020-0069 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2020-0069 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is CVE-2020-0069 actively exploited in the wild?

Yes. There are 9 known exploit references for CVE-2020-0069, including 5 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2020-0069?

CVE-2020-0069 has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 72th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2020-0069 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2020-0069 (Mediatek Multiple Chipsets Insufficient Input Validation Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-03. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2020-0069?

CVE-2020-0069 is classified as Out-of-bounds Write (CWE-787). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2020-0069 published, and has it been updated?

CVE-2020-0069 was published on March 10, 2020 and was last updated on October 21, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

HIGH severity

CVE-2020-0069

HIGH

CVE-2020-0069 is a high-severity (CVSS 7.8) Out-of-bounds Write vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2021-11-03) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

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…

Published

Mar 10, 2020

Updated

Oct 21, 2025

Affected

29 products

Patched

See advisory

Exploits

9 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2021-11-03. Federal agencies were required to remediate by 2022-05-03.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2020-0069.

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2020-0069 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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

Affected Products

29 products · 39 configurations

androidgoogle

all

berkeley-l09 firmwarehuawei

< 10.0.0.177\(c10e3r1p4\)

range

columbia-al10b firmwarehuawei

< 10.0.0.178\(c00e178r1p4\)

range

columbia-l29d firmwarehuawei

< 10.0.0.177\(c432e3r1p4\)

range

columbia-tl00b firmwarehuawei

< 10.0.0.178\(c01e178r1p4\)

range

columbia-tl00d firmwarehuawei

< 10.0.0.178\(c01e178r1p4\)

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.