Google has released the October 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 October 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-10-2020: Partial security patch level string. This security patch level string indicates that all issues associated with 01-09-2020 (and all previous security patch level strings) are addressed.
- 05-10-2020: Complete security patch level string. This security patch level address all issues associated with the 05-09-2020 security patch level and all previous patch levels.
The most severe of these issues is a high security vulnerability in the System component that could enable a remote attacker using a specially crafted transmission to gain access to additional permissions. 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 October 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-10-2020 security patch level—Vulnerability details
Android runtime
The vulnerability in this section could enable a local attacker to execute arbitrary code within the context of an application that uses the library.
| CVE | References | Type | Severity | Updated AOSP versions |
|---|---|---|---|---|
| CVE-2020-0408 | A-156999009 | EoP | High | 8.0, 8.1, 9, 10, 11 |
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-0420 | A-162383705 | EoP | High | 11 |
| CVE-2020-0421 | A-161894517 | EoP | High | 8.0, 8.1, 9, 10, 11 |
| CVE-2020-0246 | A-159062405 | ID | High | 10, 11 |
| CVE-2020-0412 | A-160390416 | ID | High | 8.0, 8.1, 9, 10, 11 |
| CVE-2020-0419 | A-142125338 | ID | High | 8.1, 9, 10, 11 |
Media Framework
The most severe vulnerability in this section could lead to remote information disclosure with no additional execution privileges needed.
| CVE | References | Type | Severity | Updated AOSP versions |
|---|---|---|---|---|
| CVE-2020-0213 | A-143464314 | ID | High | 10, 11 |
| CVE-2020-0411 | A-142641801 | ID | High | 10, 11 |
| CVE-2020-0414 | A-157708122 | ID | High | 10, 11 |
| CVE-2019-2194 | A-137284057 | EoP | Moderate | 9 |
System
The most severe vulnerability in this section could enable a remote attacker using a specially crafted transmission to gain access to additional permissions.
| CVE | References | Type | Severity | Updated AOSP versions |
|---|---|---|---|---|
| CVE-2020-0215 | A-140417248 | EoP | High | 8.0, 8.1, 9, 10, 11 |
| CVE-2020-0416 | A-155288585 | EoP | High | 8.0, 8.1, 9, 10, 11 |
| CVE-2020-0377 | A-158833854 | ID | High | 8.0, 8.1, 9, 10, 11 |
| CVE-2020-0378 | A-157748906 | ID | High | 9, 10, 11 |
| CVE-2020-0398 | A-154323381 | ID | High | 10, 11 |
| CVE-2020-0400 | A-153356561 | ID | High | 10, 11 |
| CVE-2020-0410 | A-156021269 | ID | High | 8.0, 8.1, 9, 10, 11 |
| CVE-2020-0413 | A-158778659 | ID | High | 8.0, 8.1, 9, 10, 11 |
| CVE-2020-0415 | A-156020795 | ID | High | 8.0, 8.1, 9, 10, 11 |
| CVE-2020-0422 | A-161718556 | ID | High | 8.0, 8.1, 9, 10, 11 |
Google Play system updates
The following issues are included in Project Mainline components.
| Component | CVE |
|---|---|
| Media Codecs | CVE-2020-0213 |
| Media Framework components | CVE-2020-0411 |
05-10-2020 security patch level—Vulnerability details
Kernel
The vulnerability in this section 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 | Component |
|---|---|---|---|---|
| CVE-2020-0423 | A-161151868 | EoP | High | Binder |
MediaTek components
These vulnerabilities affect MediaTek components and further details are available directly from MediaTek. The severity assessment of these issues is provided directly by MediaTek.
| CVE | References | Severity | Component |
|---|---|---|---|
| CVE-2020-0283 | A-163008257 M-ALPS05229282 | High | KeyInstall |
| CVE-2020-0339 | A-162980705 M-ALPS05194445 | High | Widevine |
| CVE-2020-0367 | A-162980455 M-ALPS05194445 | High | Widevine |
| CVE-2020-0371 | A-163008256 M-ALPS05229226 | High | KeyInstall |
| CVE-2020-0376 | A-163003156 M-ALPS05194415 | High | ISP |
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 | Severity | Component |
|---|---|---|---|
| CVE-2020-11125 | A-160605820 QC-CR#2617422 QC-CR#2673763 | High | Kernel |
| CVE-2020-11162 | A-160605604 QC-CR#2677376 | High | Kernel |
| CVE-2020-11173 | A-160605709 QC-CR#2646001 | High | Kernel |
| CVE-2020-11174 | A-160605900 QC-CR#2636449 | High | Kernel |
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 | Severity | Component |
|---|---|---|---|
| CVE-2020-3654 | A-153346045 | Critical | Closed-source component |
| CVE-2020-3657 | A-153344684 | Critical | Closed-source component |
| CVE-2020-3673 | A-153345154 | Critical | Closed-source component |
| CVE-2020-3692 | A-153345116 | Critical | Closed-source component |
| CVE-2020-11154 | A-160605708 | Critical | Closed-source component |
| CVE-2020-11155 | A-160605404 | Critical | Closed-source component |
| CVE-2020-3638 | A-153346253 | High | Closed-source component |
| CVE-2020-3670 | A-153345118 | High | Closed-source component |
| CVE-2020-3678 | A-153345398 | High | Closed-source component |
| CVE-2020-3684 | A-153346047 | High | Closed-source component |
| CVE-2020-3690 | A-153344723 | High | Closed-source component |
| CVE-2020-3703 | A-160605749 | High | Closed-source component |
| CVE-2020-3704 | A-160605508 | High | Closed-source component |
| CVE-2020-11141 | A-160606016 | High | Closed-source component |
| CVE-2020-11156 | A-160605294 | High | Closed-source component |
| CVE-2020-11157 | A-160605864 | High | Closed-source component |
| CVE-2020-11164 | A-160605595 | High | Closed-source component |
| CVE-2020-11169 | A-160605405 | High | Closed-source component |
Full details of the October 2020 Android Security Bulletin are available here.
