Google has released the June 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 June update fixes a total of 34 flaws. Two remote code execution issues ranked by Google’s Android security team as “critical” could allow attackers to use the vulnerabilities to target devices remotely using multiple methods such as email, web browsing, and MMS when processing media files.
Depending on the privileges associated with the application, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
Most of the 30 other vulnerabilities resolved in the patch affect smartphones with components from Qualcomm.
The June 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-06-2020: Partial security patch level string. This security patch level string indicates that all issues associated with 01-06-2020 (and all previous security patch level strings) are addressed.
- 05-06-2020: Complete security patch level string. This security patch level address all issues associated with the 05-06-2020 security patch level and all previous patch levels.
The most severe of these issues is a critical security vulnerability in the System component that could enable a remote attacker using a specially crafted transmission 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.
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 June 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-06-2020 security patch level—Vulnerability details
Framework
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-0114 | A-147606347 | EoP | High | 10 |
| CVE-2020-0115 | A-150038428 | EoP | High | 8.0, 8.1, 9, 10 |
| CVE-2020-0121 | A-148180766 | ID | High | 10 |
Media framework
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-0118 | A-150904694 | EoP | High | 10 |
| CVE-2020-0113 | A-150944913 | ID | High | 9, 10 |
System
The most severe vulnerability in this section could enable a remote attacker using a specially crafted transmission to execute arbitrary code within the context of a privileged process.
| CVE | References | Type | Severity | Updated AOSP versions |
|---|---|---|---|---|
| CVE-2020-0117 | A-151155194 | RCE | Critical | 8.0, 8.1, 9, 10 |
| CVE-2020-8597 | A-151153886 | RCE | Critical | 8.0, 8.1, 9, 10 |
| CVE-2020-0116 | A-151330809 | ID | High | 10 |
| CVE-2020-0119 | A-150500247 | ID | High | 10 |
Google Play system updates
There are no security issues addressed in Google Play system updates (Project Mainline) this month.
05-06-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-2019-2219 | A-119041698 | ID | High | 8.0, 8.1, 9, 10 |
System
The vulnerability in this section could enable a remote attacker to bypass user interaction requirements in order to gain access to additional permissions.
| CVE | References | Type | Severity | Updated AOSP versions |
|---|---|---|---|---|
| CVE-2019-9460 | A-62535446 | EoP | High | 10 |
Kernel components
The most severe vulnerability in this section could enable a local attacker using a specially crafted application to execute arbitrary code within the context of a privileged process.
| CVE | References | Type | Severity | Component |
|---|---|---|---|---|
| CVE-2020-8647 | A-149079134 Upstream kernel | EoP | High | Kernel TTY support |
| CVE-2020-8648 | A-149079230 Upstream kernel | EoP | High | Kernel TTY support |
| CVE-2020-8428 | A-148713787 Upstream kernel | ID | High | Kernel |
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-2017-9704 | A-35099636 QC-CR#2013052 QC-CR#2070526 QC-CR#2076578 | N/A | High | Camera |
| CVE-2020-3665 | A-150697775 QC-CR#2174506 | N/A | High | WLAN |
| CVE-2019-14047 | A-145545249 QC-CR#2279971 | N/A | High | Kernel |
| CVE-2019-9460 | A-66876469 QC-CR#2207338 | N/A | Moderate | Display |
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-14073 | A-145546513 | N/A | Critical | Closed-source component |
| CVE-2019-14080 | A-145545821 | N/A | Critical | Closed-source component |
| CVE-2020-3614 | A-140973436 | N/A | High | Closed-source component |
| CVE-2020-3626 | A-150697952 | N/A | High | Closed-source component |
| CVE-2020-3628 | A-150695508 | N/A | High | Closed-source component |
| CVE-2020-3635 | A-148817146 | N/A | High | Closed-source component |
| CVE-2020-3642 | A-150697435 | N/A | High | Closed-source component |
| CVE-2020-3658 | A-150697838 | N/A | High | Closed-source component |
| CVE-2020-3660 | A-150695050 | N/A | High | Closed-source component |
| CVE-2020-3661 | A-150695169 | N/A | High | Closed-source component |
| CVE-2020-3662 | A-150696661 | N/A | High | Closed-source component |
| CVE-2020-3663 | A-150697436 | N/A | High | Closed-source component |
| CVE-2020-3676 | A-152310294 | N/A | High | Closed-source component |
| CVE-2019-10597 | A-145545755 | N/A | High | Closed-source component |
| CVE-2019-14062 | A-145545091 | N/A | High | Closed-source component |
| CVE-2019-14076 | A-145545285 | N/A | High | Closed-source component |
Full details of the June 2020 Android Security Bulletin are available here.
