CVE-2020-0069Exploited in the wildNVD status: Analyzed
Mediatek Multiple Chipsets Insufficient Input Validation
CVE-2020-0069 is a high-severity out-of-bounds write vulnerability in Android, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected Android versions: Android kernel. The record does not name a fixed version, so check the vendor advisory. CISA added it to the Known Exploited Vulnerabilities catalogue on November 3, 2021, which means attacks have been observed in the wild.
Patch now
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Update Berkeley-l09 Firmware to 10.0.0.177\(c10e3r1p4\) or a later version.
- Update Columbia-al10b Firmware to 10.0.0.178\(c00e178r1p4\) or a later version.
- Update Columbia-l29d Firmware to 10.0.0.177\(c10e4r1p4\) or 10.0.0.177\(c432e3r1p4\), whichever matches your release line, or a later version.
- CISA's required action: Apply updates per vendor instructions.
- Read the advisory on huawei.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Android | Android | Android kernel | Not stated |
| Huawei | Berkeley-l09 Firmware | before 10.0.0.177\(c10e3r1p4\) | 10.0.0.177\(c10e3r1p4\) |
| Huawei | Columbia-al10b Firmware | before 10.0.0.178\(c00e178r1p4\) | 10.0.0.178\(c00e178r1p4\) |
| Huawei | Columbia-l29d Firmware | before 10.0.0.177\(c10e4r1p4\); before 10.0.0.177\(c432e3r1p4\) | 10.0.0.177\(c10e4r1p4\), 10.0.0.177\(c432e3r1p4\) |
| Huawei | Columbia-tl00b Firmware | before 10.0.0.178\(c01e178r1p4\) | 10.0.0.178\(c01e178r1p4\) |
| Huawei | Columbia-tl00d Firmware | before 10.0.0.178\(c01e178r1p4\) | 10.0.0.178\(c01e178r1p4\) |
| Huawei | Cornell-al00a Firmware | before 9.1.0.340\(c00e333r1p1t8\) | 9.1.0.340\(c00e333r1p1t8\) |
| Huawei | Cornell-tl10b Firmware | before 9.1.0.340\(c01e333r1p1t8\) | 9.1.0.340\(c01e333r1p1t8\) |
| Huawei | Dura-al00a Firmware | before 1.0.0.190\(c00\) | 1.0.0.190\(c00\) |
| Huawei | Honor 20 Pro Firmware | before 10.0.0.194\(c636e3r3p1\); before 10.0.0.202\(c10e3r3p2\) | 10.0.0.194\(c636e3r3p1\), 10.0.0.202\(c10e3r3p2\) |
| Huawei | Y6 2019 Firmware | before 9.1.0.290\(c185e5r4p1\); before 9.1.0.290\(c431e1r1p8\); before 9.1.0.290\(c605e6r1p6\); before 9.1.0.295\(c431e5r2p2\) | 9.1.0.290\(c185e5r4p1\), 9.1.0.290\(c431e1r1p8\), 9.1.0.290\(c605e6r1p6\), 9.1.0.295\(c431e5r2p2\) |
| Huawei | Nova 3 Firmware | before 9.1.0.338\(c00e333r1p1t8\) | 9.1.0.338\(c00e333r1p1t8\) |
| Huawei | Nova 4 Firmware | before 10.0.0.160\(c01e32r2p4\) | 10.0.0.160\(c01e32r2p4\) |
| Huawei | Honor 8a Firmware | before 9.1.0.291\(c185e3r4p1\); before 9.1.0.291\(c432e5r2p1\); before 9.1.0.291\(c636e4r4p1\); before 9.1.0.297\(c605e4r4p2\) | 9.1.0.291\(c185e3r4p1\), 9.1.0.291\(c432e5r2p1\), 9.1.0.291\(c636e4r4p1\), 9.1.0.297\(c605e4r4p2\) |
| Huawei | Honor View 20 Firmware | before 10.0.0.198\(c432e10r3p4\); before 10.0.0.200\(c185e3r3p3\); before 10.0.0.201\(c10e5r4p3\) | 10.0.0.198\(c432e10r3p4\), 10.0.0.200\(c185e3r3p3\), 10.0.0.201\(c10e5r4p3\) |
| Huawei | Jakarta-al00a Firmware | before 9.1.0.251\(c00e106r2p2\) | 9.1.0.251\(c00e106r2p2\) |
| Huawei | Katyusha-al00a Firmware | before 9.1.0.146\(c00e131r2p2\) | 9.1.0.146\(c00e131r2p2\) |
| Huawei | Katyusha-al10a Firmware | before 9.1.0.160\(c00e150r1p7\) | 9.1.0.160\(c00e150r1p7\) |
| Huawei | Madrid-al00a Firmware | before 9.1.0.261\(c00e120r4p1\) | 9.1.0.261\(c00e120r4p1\) |
| Huawei | Paris-l29b Firmware | before 9.1.0.380\(c636e1r1p3t8\) | 9.1.0.380\(c636e1r1p3t8\) |
| Huawei | Princeton-al10b Firmware | before 10.0.0.194\(c00e61r4p11\) | 10.0.0.194\(c00e61r4p11\) |
| Huawei | Sydney-al00 Firmware | before 9.1.0.237\(c00e80r1p7t8\) | 9.1.0.237\(c00e80r1p7t8\) |
| Huawei | Sydney-tl00 Firmware | before 9.1.0.237\(c01e80r1p7t8\) | 9.1.0.237\(c01e80r1p7t8\) |
| Huawei | Sydneym-al00 Firmware | before 10.0.0.159\(c00e64r1p5\) | 10.0.0.159\(c00e64r1p5\) |
| Huawei | Tony-al00b Firmware | before 10.1.0.137\(c00e137r2p11\) | 10.1.0.137\(c00e137r2p11\) |
Version data comes from the organisation that assigned the CVE; 4 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | NVD |
| CVSS 3.1 | 7.8 | High | CISA (ADP) |
| CVSS 2.0 | 7.2 | High | NVD |
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
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Write
The product writes data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
Timeline
- CVE record published.
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- Deadline for US federal agencies to remediate, set by CISA.
- CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Third-party and government advisories
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-0069Third Party Advisory, US Government Resource
Other vulnerabilities in Android
- 5.5 Medium severity
Android Pixel Information Disclosure Exploited
- 7.5 High severity
- 7.8 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Recent Out-of-bounds Write vulnerabilities
- 7.8 High severity
- 8.8 High severity
- 7.8 High severity
Apple iOS Memory Corruption Exploited
- 7.8 High severity
- 9.8 Critical severity
- 6.5 Medium severity
Google Chromium V8 Out-of-Bounds Write Exploited
Spotted an error? Tell us.