How severe is CVE-2020-0069?

CVE-2020-0069 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2020-0069 being actively exploited?

Yes. CVE-2020-0069 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2021-11-03, which means active exploitation has been confirmed. It should be prioritised for remediation.

What products are affected by CVE-2020-0069?

CVE-2020-0069 primarily affects Google Android. In total, 29 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2020-0069?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.

Does CVE-2020-0069 have an EU (EUVD) identifier?

Yes. CVE-2020-0069 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2020-1576. It is also flagged as exploited in the EUVD (since 2021-11-03).

When was CVE-2020-0069 published?

CVE-2020-0069 was published on 2020-03-10 and last updated on 2026-06-17.

CVE-2020-0069

CVE-2020-0069 is a high-severity vulnerability in Google Android with a CVSS 3.x base score of 7.8. It is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, confirming it has been exploited in the wild (added 2021-11-03). The underlying weakness is classified as CWE-787.

Key facts

Severity: High (CVSS 3.x base score 7.8)
CVSS v2: 7.2
EPSS exploit prediction: 1% (67th percentile)
Actively exploited: Yes — listed in CISA KEV (added 2021-11-03)
EU (EUVD) id: EUVD-2020-1576
EU exploitation: Flagged exploited in the ENISA EU Vulnerability Database (since 2021-11-03)
Weakness: CWE-787
Affected product: Google Android
Published: 2020-03-10
Last modified: 2026-06-17

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

Frequently asked questions

What is CVE-2020-0069?: 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
How severe is CVE-2020-0069?: CVE-2020-0069 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2020-0069 being actively exploited?: Yes. CVE-2020-0069 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2021-11-03, which means active exploitation has been confirmed. It should be prioritised for remediation.
What products are affected by CVE-2020-0069?: CVE-2020-0069 primarily affects Google Android. In total, 29 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2020-0069?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.
Does CVE-2020-0069 have an EU (EUVD) identifier?: Yes. CVE-2020-0069 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2020-1576. It is also flagged as exploited in the EUVD (since 2021-11-03).
When was CVE-2020-0069 published?: CVE-2020-0069 was published on 2020-03-10 and last updated on 2026-06-17.

References

Affected products (29)

cpe:2.3:o:google:android:-:*:*:*:*:*:*:*
cpe:2.3:o:huawei:berkeley-l09_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:columbia-al10b_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:columbia-l29d_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:columbia-tl00b_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:columbia-tl00d_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:cornell-al00a_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:cornell-tl10b_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:dura-al00a_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:honor_20_pro_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:y6_2019_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:nova_3_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:nova_4_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:honor_8a_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:honor_view_20_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:jakarta-al00a_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:katyusha-al00a_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:katyusha-al10a_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:madrid-al00a_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:paris-l29b_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:princeton-al10b_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:sydney-al00_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:sydney-tl00_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:sydneym-al00_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:tony-al00b_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:tony-tl00b_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:yale-al00a_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:yale-l21a_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:huawei:yalep-al10b_firmware:*:*:*:*:*:*:*:*

More vulnerabilities in Google Android

CVE-2026-0092 — Critical (CVSS 10.0): In Package Manager, there is a possible device lock controller bypass due to a missing permission check. This could…
CVE-2025-48611 — Critical (CVSS 10.0): In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead…
CVE-2015-8073 — Critical (CVSS 10.0): mediaserver in Android 4.4 and 5.1 before 5.1.1 LMY48X allows remote attackers to execute arbitrary code or cause a…
CVE-2015-8072 — Critical (CVSS 10.0): mediaserver in Android 4.4 through 5.x before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to execute…
CVE-2015-6610 — Critical (CVSS 10.0): libstagefright in Android before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows attackers to gain privileges or cause a…
CVE-2015-6609 — Critical (CVSS 10.0): libutils in Android before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to execute arbitrary code or…

All CVEs affecting Google Android →

Other CWE-787 (Out-of-bounds Write) vulnerabilities

CVE-2026-42369 — Critical (CVSS 10.0): GV-VMS V20 is a Video Monitoring Software used to gather the feeds of many surveillance cameras and manage other…
CVE-2026-4746 — Critical (CVSS 10.0): Out-of-bounds Write vulnerability in timeplus-io proton (base/poco/Foundation/src‎ modules). This vulnerability is…
CVE-2025-43300 — Critical (CVSS 10.0): An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in iOS 15.8.5 and iPadOS…
CVE-2025-24201 — Critical (CVSS 10.0): An out-of-bounds write issue was addressed with improved checks to prevent unauthorized actions. This issue is fixed in…
CVE-2024-42479 — Critical (CVSS 10.0): llama.cpp provides LLM inference in C/C++. The unsafe `data` pointer member in the `rpc_tensor` structure can cause…
CVE-2024-39791 — Critical (CVSS 10.0): Stack-based buffer overflow vulnerabilities affecting Vonets industrial wifi bridge relays and wifi bridge…

Browse all CWE-787 (Out-of-bounds Write) vulnerabilities →