Google has released the March 2020 Android Security Bulletin, giving carriers and device makers a fresh set of patches to install.
Though Google puts out the Android security patches each month, the job of actually getting the fixes to end users falls on the telcos and/or device manufacturers themselves. Those partners vary in their ability to release the patches in a timely fashion.
The March bulletin has two security patch levels to provide Android partners with the flexibility to more quickly fix a subset of vulnerabilities that are similar across all Android devices.
- 01-03-2020: Partial security patch level string. This security patch level string indicates that all issues associated with 01-03-2020 (and all previous security patch level strings) are addressed.
- 05-03-2020: Complete security patch level string. This security patch level address all issues associated with the 05-03-2020 security patch level and all previous patch levels.
There are 12 issues resolved in the March security patch dated March 1, 2020 and 60 for March 5, 2020. Vulnerabilities range from high to critical, with the most severe relating to the media framework and a remote attacker possibly executing arbitrary code through a crafted file. Finally, Google has fixed a security exploit for MediaTek chipsets said to have been affecting millions of devices for months.
The most severe of these issues is a critical security vulnerability in the media framework that could enable a remote attacker using a specially crafted file to execute arbitrary code within the context of a privileged process. The severity assessment is based on the effect that exploiting the vulnerability would possibly have on an affected device, assuming the platform and service mitigations are turned off for development purposes or if successfully bypassed.
The only critical flaws in the March 5, 2020 patch group were in closed source components from chip vendor Qualcomm, which accounted for 48 of the bugs in the Android bulletin overall. These 16 critical bugs included several buffer overflow errors. Several of these critical bugs were remotely exploitable flaws in WLAN firmware (CVE-2019-10546, 14031, 14083, 14086, 14097, and 14098), while another five (CVE-2019-10586, 10587, 10593, 10594, and 2317) affected the Qualcomm chip’s data modem.
Alongside the bulletin, Google have released a security update to Google devices through an over-the-air (OTA) update. The Google device firmware images have also been released to the Google Developer site. Security patch levels of March 5, 2020 or later address all of these issues.
The tables below contains a list of security vulnerabilities, the Common Vulnerability and Exposures ID (CVE), the assessed severity, and whether or not Google devices are affected. The severity assessment is based on the effect that exploiting the vulnerability would possibly have on an affected device, assuming the platform and service mitigations are disabled for development purposes or if successfully bypassed.
Android and Google Service Mitigation’s
This is a summary of the mitigation’s provided by the Android security platform and service protections such as Google Play Protect. These capabilities reduce the likelihood that security vulnerabilities could be successfully exploited on Android.
- Exploitation for many issues on Android is made more difficult by enhancements in newer versions of the Android platform. All users are encouraged to update to the latest version of Android where possible.
- The Android security team actively monitors for abuse through Google Play Protect and warns users about Potentially Harmful Applications. Google Play Protect is enabled by default on devices with Google Mobile Services, and is especially important for users who install apps from outside of Google Play.
- Android 10 introduces Google Play system updates (Project Mainline) which expedites how updates can be delivered to Android devices with Google Mobile Services. The Android Security Bulletin identifies security issues which are remediated through Google Play system updates
Terminology
You will find different types of vulnerabilities listed. Possible types include:
- RCE—Remote code execution
- EoP—Elevation of privilege
- ID—Information disclosure
- DoS—Denial of service
01-03-2020 security patch level—Vulnerability details
Framework
The vulnerability in this section could enable a local malicious application to bypass operating system protections that isolate application data from other applications.
| CVE | References | Type | Severity | Updated AOSP versions |
|---|---|---|---|---|
| CVE-2020-0031 | A-141703197 | ID | High | 10 |
Media framework
The most severe vulnerability in this section could enable a remote attacker using a specially crafted file to execute arbitrary code within the context of a privileged process.
| CVE | References | Type | Severity | Updated AOSP versions |
|---|---|---|---|---|
| CVE-2020-0032 | A-145364230 | RCE | Critical | 8.0, 8.1, 9, 10 |
| CVE-2020-0033 | A-144351324 | EoP | High | 8.0, 8.1, 9, 10 |
| CVE-2020-0034 | A-62458770 | ID | High | 8.0, 8.1 |
System
The most severe vulnerability in this section could enable a local malicious application to bypass user interaction requirements in order to gain access to additional permissions.
| CVE | References | Type | Severity | Updated AOSP versions |
|---|---|---|---|---|
| CVE-2020-0036 | A-144679405 | EoP | High | 8.0, 8.1, 9, 10 |
| CVE-2019-2194 | A-137284057 | EoP | High | 9 |
| CVE-2020-0035 | A-140622024 | ID | High | 8.0, 8.1, 9 |
| CVE-2020-0029 | A-140065828 | ID | High | 10 |
| CVE-2020-0037 | A-143106535 | ID | High | 8.0, 8.1, 9, 10 |
| CVE-2020-0038 | A-143109193 | ID | High | 8.0, 8.1, 9, 10 |
| CVE-2020-0039 | A-143155861 | ID | High | 8.0, 8.1, 9, 10 |
Google Play system updates
The following issue is included in Project Mainline components.
| Component | CVE |
|---|---|
| Media codecs | CVE-2020-0032 |
05-03-2020 security patch level—Vulnerability details
System
The vulnerability in the following sections could enable a local attacker using a specially crafted file to execute arbitrary code within the context of a privileged process.
| CVE | References | Type | Severity | Updated AOSP versions |
|---|---|---|---|---|
| CVE-2019-2194 | A-137284057 | EoP | High | 9 |
Kernel components
The most severe vulnerability in this section could enable a local attacker using a specially crafted USB device to execute arbitrary code within the context of a privileged process.
| CVE | References | Type | Severity | Component |
|---|---|---|---|---|
| CVE-2019-19527 | A-146257915 Upstream kernel | EoP | High | USB |
| CVE-2019-19537 | A-146258055 Upstream kernel | EoP | High | USB |
| CVE-2020-0040 | A-143009752 Upstream kernel | EoP | High | Networking |
| CVE-2020-0041 | A-145988638 Upstream kernel | EoP | High | Binder |
FPC components
The most severe vulnerability in this section could enable a local malicious application to bypass user interaction requirements in order to gain access to additional permissions.
| CVE | References | Type | Severity | Component |
|---|---|---|---|---|
| CVE-2020-0010 | A-137014293 | EoP | High | FPC Fingerprint TEE |
| CVE-2020-0011 | A-137648045 | EoP | High | FPC Fingerprint TEE |
| CVE-2020-0012 | A-137648844 | EoP | High | FPC Fingerprint TEE |
| CVE-2020-0042 | A-137649599 | ID | Moderate | FPC Fingerprint TEE |
| CVE-2020-0043 | A-137650218 | ID | Moderate | FPC Fingerprint TEE |
| CVE-2020-0044 | A-137650219 | ID | Moderate | FPC Fingerprint TEE |
MediaTek components
| CVE | References | Type | Severity | Component |
|---|---|---|---|---|
| CVE-2020-0069 | A-147882143 M-ALPS04356754 | EoP | High | Mediatek Command Queue driver |
Qualcomm components
These vulnerabilities affect Qualcomm components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm.
| CVE | References | Type | Severity | Component |
|---|---|---|---|---|
| CVE-2019-14079 | A-138848422 QC-CR#2521001 | N/A | High | USB |
| CVE-2018-11838 | A-145545090 QC-CR#221457 | N/A | High | WLAN |
| CVE-2019-10526 | A-145544085 QC-CR#2232526 QC-CR#2541970 | N/A | High | WLAN |
| CVE-2019-10569 | A-145545820 QC-CR#2315791 | N/A | High | Audio |
| CVE-2019-14029 | A-145546793 QC-CR#2528795 | N/A | High | Graphics |
| CVE-2019-14032 | A-145546652 QC-CR#2537311 | N/A | High | Audio |
| CVE-2019-14068 | A-145546435 QC-CR#2507653 [2] | N/A | High | Audio |
| CVE-2019-14072 | A-145545251 QC-CR#2509391 | N/A | High | Graphics |
Qualcomm closed-source components
These vulnerabilities affect Qualcomm closed-source components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm.
| CVE | References | Type | Severity | Component |
|---|---|---|---|---|
| CVE-2019-2317 | A-134436812 | N/A | Critical | Closed-source component |
| CVE-2019-10586 | A-140423909 | N/A | Critical | Closed-source component |
| CVE-2019-10587 | A-140423816 | N/A | Critical | Closed-source component |
| CVE-2019-10593 | A-140424165 | N/A | Critical | Closed-source component |
| CVE-2019-10594 | A-140424564 | N/A | Critical | Closed-source component |
| CVE-2019-10612 | A-140423161 | N/A | Critical | Closed-source component |
| CVE-2019-14031 | A-142271912 | N/A | Critical | Closed-source component |
| CVE-2019-14045 | A-140973418 | N/A | Critical | Closed-source component |
| CVE-2019-14071 | A-145545489 | N/A | Critical | Closed-source component |
| CVE-2019-14083 | A-140973259 | N/A | Critical | Closed-source component |
| CVE-2019-14086 | A-140973417 | N/A | Critical | Closed-source component |
| CVE-2019-14030 | A-145546515 | N/A | Critical | Closed-source component |
| CVE-2019-14097 | A-145546003 | N/A | Critical | Closed-source component |
| CVE-2019-14098 | A-145546314 | N/A | Critical | Closed-source component |
| CVE-2019-10546 | A-145545250 | N/A | Critical | Closed-source component |
| CVE-2019-14095 | A-142843397 | N/A | Critical | Closed-source component |
| CVE-2018-11970 | A-114042111 | N/A | High | Closed-source component |
| CVE-2019-10603 | A-140424074 | N/A | High | Closed-source component |
| CVE-2019-10616 | A-140423338 | N/A | High | Closed-source component |
| CVE-2019-10549 | A-140423162 | N/A | High | Closed-source component |
| CVE-2019-10550 | A-140423702 | N/A | High | Closed-source component |
| CVE-2019-10552 | A-140423817 | N/A | High | Closed-source component |
| CVE-2019-10553 | A-140423081 | N/A | High | Closed-source component |
| CVE-2019-10554 | A-140424012 | N/A | High | Closed-source component |
| CVE-2019-10577 | A-140424166 | N/A | High | Closed-source component |
| CVE-2019-14026 | A-142271986 | N/A | High | Closed-source component |
| CVE-2019-14027 | A-142271756 | N/A | High | Closed-source component |
| CVE-2019-14028 | A-142271831 | N/A | High | Closed-source component |
| CVE-2019-2300 | A-142271659 | N/A | High | Closed-source component |
| CVE-2019-2311 | A-142271967 | N/A | High | Closed-source component |
| CVE-2019-14050 | A-143902706 | N/A | High | Closed-source component |
| CVE-2019-14081 | A-143902882 | N/A | High | Closed-source component |
| CVE-2019-14082 | A-140974589 | N/A | High | Closed-source component |
| CVE-2019-14085 | A-143902807 | N/A | High | Closed-source component |
| CVE-2019-14048 | A-145545282 | N/A | High | Closed-source component |
| CVE-2019-14061 | A-145545758 | N/A | High | Closed-source component |
| CVE-2019-10604 | A-145545725 | N/A | High | Closed-source component |
| CVE-2019-10591 | A-145545283 | N/A | High | Closed-source component |
| CVE-2019-14000 | A-145546434 | N/A | High | Closed-source component |
| CVE-2019-14015 | A-145545650 | N/A | High | Closed-source component |
Full details of the March 2020 Android Security Bulletin are available here.
