Headline
CVE-2020-0258: Android Security Bulletin—August 2020 | Android Open Source Project
In stopZygoteLocked of AppZygote.java, there is an insufficient cleanup. This could lead to local information disclosure in the application that is started next with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10Android ID: A-157598956
Published August 3, 2020 | Updated August 10, 2020
The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Security patch levels of 2020-08-05 or later address all of these issues. To learn how to check a device’s security patch level, see Check and update your Android version.
Android partners are notified of all issues at least a month before publication. Source code patches for these issues have been released to the Android Open Source Project (AOSP) repository and linked from this bulletin. This bulletin also includes links to patches outside of AOSP.
The most severe of these issues is a high security vulnerability in the Framework component that could enable a remote attacker using a specially crafted file to execute arbitrary code within the context of an unprivileged 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.
Refer to the Android and Google Play Protect mitigations section for details on the Android security platform protections and Google Play Protect, which improve the security of the Android platform.
Android and Google service mitigations
This is a summary of the mitigations 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. We encourage all users 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.
2020-08-01 security patch level vulnerability details
In the sections below, we provide details for each of the security vulnerabilities that apply to the 2020-08-01 patch level. Vulnerabilities are grouped under the component they affect. Issues are described in the tables below and include CVE ID, associated references, type of vulnerability, severity, and updated AOSP versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID. Devices with Android 10 and later may receive security updates as well as Google Play system updates.
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 an unprivileged process.
CVE
References
Type
Severity
Updated AOSP versions
CVE-2020-0240
A-150706594
RCE
High
10
CVE-2020-0238
A-150946634
EoP
High
8.0, 8.1, 9, 10
CVE-2020-0257
A-156741968
EoP
High
10
CVE-2020-0239
A-151095863
ID
High
9, 10
CVE-2020-0249
A-154719656
ID
High
8.0, 8.1, 9, 10
CVE-2020-0258
A-157598956
ID
High
10
CVE-2020-0247
A-156087409
DoS
High
8.0, 8.1, 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-0241
A-151456667
EoP
High
8.0, 8.1, 9, 10
CVE-2020-0242
A-151643722
EoP
High
8.0, 8.1, 9, 10
CVE-2020-0243
A-151644303
EoP
High
8.0, 8.1, 9, 10
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-0108
A-140108616 [2] [3] [4]
EoP
High
8.1, 9, 10
CVE-2020-0256
A-152874864
EoP
High
8.0, 8.1, 9, 10
CVE-2020-0248
A-154627439
ID
High
10
CVE-2020-0250
A-154934934
ID
High
10
Google Play system updates
There are no security issues addressed in Google Play system updates (Project Mainline) this month.
2020-08-05 security patch level vulnerability details
In the sections below, we provide details for each of the security vulnerabilities that apply to the 2020-08-05 patch level. Vulnerabilities are grouped under the component they affect. Issues are described in the tables below and include CVE ID, associated references, type of vulnerability, severity, and updated AOSP versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.
AMLogic components
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-0259
A-157941353 *
EoP
High
dm-verity
Kernel components
The most severe vulnerability in this section could enable a local attacker to bypass user interaction requirements in order to gain access to additional permissions.
CVE
References
Type
Severity
Component
CVE-2020-10751
A-155485360
Upstream kernel
EoP
High
SELinux
CVE-2020-12464
A-156071259
Upstream kernel
EoP
High
Linux USB Subsystem
CVE-2019-16746
A-145728612
Upstream kernel
ID
High
Linux Wireless Subsystem
MediaTek components
The severity assessment of these issues is provided directly by MediaTek.
CVE
References
Type
Severity
Component
CVE-2020-0252
A-152236803
ALPS05098839 *
EoP
High
Multimedia Processing Driver
CVE-2020-0253
A-152647365
ALPS05098839 *
EoP
High
Multimedia Processing Driver
CVE-2020-0260
A-152225183
ALPS05098839 *
EoP
High
Multimedia Processing Driver
CVE-2020-0251
A-152647626
ALPS05098839 *
ID
High
Multimedia Processing Driver
CVE-2020-0254
A-152647751
ALPS05098839 *
ID
High
Multimedia Processing 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-2020-11116
A-155654321
QC-CR#2575144
QC-CR#2616225
QC-CR#2616227
N/A
Critical
WLAN
CVE-2020-11115
A-155653491
QC-CR#2573329
QC-CR#2617004
QC-CR#2617005
N/A
High
WLAN
CVE-2020-11118
A-155654263
QC-CR#2626729
QC-CR#2635664
QC-CR#2635666
N/A
High
WLAN
CVE-2020-11120
A-155652795
QC-CR#2556613
N/A
High
WLAN
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-10562
A-147102924 *
N/A
Critical
Closed-source component
CVE-2019-10615
A-147102844 *
N/A
Critical
Closed-source component
CVE-2019-13998
A-147102225 *
N/A
Critical
Closed-source component
CVE-2020-3619
A-148815858 *
N/A
Critical
Closed-source component
CVE-2020-3667
A-150696660 *
N/A
Critical
Closed-source component
CVE-2018-5886
A-63165064 *
N/A
High
Closed-source component
CVE-2018-13903
A-145546313 *
N/A
High
Closed-source component
CVE-2019-13999
A-147104231 *
N/A
High
Closed-source component
CVE-2019-14025
A-145546440 *
N/A
High
Closed-source component
CVE-2019-14052
A-147103610 *
N/A
High
Closed-source component
CVE-2019-14056
A-147101659 *
N/A
High
Closed-source component
CVE-2019-14065
A-147102925 *
N/A
High
Closed-source component
CVE-2019-14089
A-147104726 *
N/A
High
Closed-source component
CVE-2019-14115
A-147104255 *
N/A
High
Closed-source component
CVE-2019-14119
A-147103020 *
N/A
High
Closed-source component
CVE-2020-3611
A-148816870 *
N/A
High
Closed-source component
CVE-2020-3624
A-148816990 *
N/A
High
Closed-source component
CVE-2020-3636
A-148816708 *
N/A
High
Closed-source component
CVE-2020-3640
A-148816993 *
N/A
High
Closed-source component
CVE-2020-3643
A-148816294 *
N/A
High
Closed-source component
CVE-2020-3644
A-148817069 *
N/A
High
Closed-source component
CVE-2020-3666
A-150697811 *
N/A
High
Closed-source component
CVE-2020-3668
A-150697381 *
N/A
High
Closed-source component
CVE-2020-3669
A-150848722 *
N/A
High
Closed-source component
CVE-2020-3675
A-150696996 *
N/A
High
Closed-source component
CVE-2020-11122
A-155653312 *
N/A
High
Closed-source component
CVE-2020-11128
A-155654284 *
N/A
High
Closed-source component
Common questions and answers
This section answers common questions that may occur after reading this bulletin.
1. How do I determine if my device is updated to address these issues?
To learn how to check a device’s security patch level, see Check and update your Android version.
- Security patch levels of 2020-08-01 or later address all issues associated with the 2020-08-01 security patch level.
- Security patch levels of 2020-08-05 or later address all issues associated with the 2020-08-05 security patch level and all previous patch levels.
Device manufacturers that include these updates should set the patch string level to:
- [ro.build.version.security_patch]:[2020-08-01]
- [ro.build.version.security_patch]:[2020-08-05]
For some devices on Android 10 or later, the Google Play system update will have a date string that matches the 2020-08-01 security patch level. Please see this article for more details on how to install security updates.
2. Why does this bulletin have two security patch levels?
This bulletin has two security patch levels so that Android partners have the flexibility to fix a subset of vulnerabilities that are similar across all Android devices more quickly. Android partners are encouraged to fix all issues in this bulletin and use the latest security patch level.
- Devices that use the 2020-08-01 security patch level must include all issues associated with that security patch level, as well as fixes for all issues reported in previous security bulletins.
- Devices that use the security patch level of 2020-08-05 or newer must include all applicable patches in this (and previous) security bulletins.
Partners are encouraged to bundle the fixes for all issues they are addressing in a single update.
3. What do the entries in the Type column mean?
Entries in the Type column of the vulnerability details table reference the classification of the security vulnerability.
Abbreviation
Definition
RCE
Remote code execution
EoP
Elevation of privilege
ID
Information disclosure
DoS
Denial of service
N/A
Classification not available
4. What do the entries in the References column mean?
Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.
Prefix
Reference
A-
Android bug ID
QC-
Qualcomm reference number
M-
MediaTek reference number
N-
NVIDIA reference number
B-
Broadcom reference number
5. What does an * next to the Android bug ID in the References column mean?
Issues that are not publicly available have an * next to the corresponding reference ID. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.
6. Why are security vulnerabilities split between this bulletin and device / partner security bulletins, such as the Pixel bulletin?
Security vulnerabilities that are documented in this security bulletin are required to declare the latest security patch level on Android devices. Additional security vulnerabilities that are documented in the device / partner security bulletins are not required for declaring a security patch level. Android device and chipset manufacturers may also publish security vulnerability details specific to their products, such as Google, Huawei, LGE, Motorola, Nokia, or Samsung.
Versions
Version
Date
Notes
1.0
August 3, 2020
Bulletin published
1.1
August 4, 2020
Bulletin revised to include AOSP links
1.2
August 10, 2020
Revised CVE table