Headline
CVE-2022-20238: Android Security Bulletin—July 2022 | Android Open Source Project
‘remap_pfn_range’ here may map out of size kernel memory (for example, may map the kernel area), and because the ‘vma->vm_page_prot’ can also be controlled by userspace, so userspace may map the kernel area to be writable, which is easy to be exploitedProduct: AndroidVersions: Android SoCAndroid ID: A-233154555
Published July 6, 2022 | Updated July 7, 2022
The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Security patch levels of 2022-07-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 will be released to the Android Open Source Project (AOSP) repository in the next 48 hours. We will revise this bulletin with the AOSP links when they are available.
The most severe of these issues is a critical security vulnerability in the System component that could lead to remote code execution with no additional execution privileges needed. 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.
2022-07-01 security patch level vulnerability details
In the sections below, we provide details for each of the security vulnerabilities that apply to the 2022-07-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 lead to local information disclosure with no additional execution privileges needed.
CVE
References
Type
Severity
Updated AOSP versions
CVE-2022-20219
A-224585613 [2] [3] [4] [5]
ID
High
10, 11, 12, 12L
CVE-2022-20228
A-213850092
ID
High
12, 12L
System
The most severe vulnerability in this section could lead to remote code execution with no additional execution privileges needed.
CVE
References
Type
Severity
Updated AOSP versions
CVE-2022-20222
A-228078096
RCE
Critical
12, 12L
CVE-2022-20229
A-224536184
RCE
Critical
10, 11, 12, 12L
CVE-2021-0981
A-191981182
EoP
High
10, 11
CVE-2022-20223
A-223578534
EoP
High
10, 11, 12, 12L
CVE-2022-20226
A-213644870 [2]
EoP
High
12, 12L
CVE-2022-20221
A-205571133
ID
High
10, 11, 12, 12L
CVE-2022-20224
A-220732646
ID
High
10, 11, 12, 12L
CVE-2022-20225
A-213457638
ID
High
10, 11, 12, 12L
CVE-2022-20230
A-221859869
ID
High
10, 11, 12, 12L
Google Play system updates
The following issues are included in Project Mainline components.
Component
CVE
Media Codecs, Media Framework components
CVE-2022-20228
2022-07-05 security patch level vulnerability details
In the sections below, we provide details for each of the security vulnerabilities that apply to the 2022-07-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.
Framework
The vulnerability in this section could lead to local escalation of privilege with User execution privileges needed.
CVE
References
Type
Severity
Updated AOSP versions
CVE-2022-20220
A-219015884
EoP
High
12, 12L
Kernel components
The most severe vulnerability in this section could lead to local information disclosure with no additional execution privileges needed.
CVE
References
Type
Severity
Component
CVE-2022-20227
A-216825460
Upstream kernel [2]
ID
High
Kernel
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-2022-20083
A-231275475
M-MOLY00803883*
High
Modem 2G/3G CC
CVE-2022-21744
A-231281131
M-MOLY00810064*
High
Modem 2G RR
CVE-2022-21767
A-231275476
M-ALPS06784430*
High
Bluetooth
CVE-2022-21768
A-231281132
M-ALPS06784351*
High
Bluetooth
CVE-2022-21763
A-231275473
M-ALPS07044717*
High
telecom service
CVE-2022-21764
A-231271468
M-ALPS07044717*
High
telecom service
Unisoc components
These vulnerabilities affect Unisoc components and further details are available directly from Unisoc. The severity assessment of these issues is provided directly by Unisoc.
CVE
References
Severity
Component
CVE-2022-20216
A-231911916
U-1867981*
High
Telephony
CVE-2022-20217
A-232441378
U-1882905*
High
Telephony
CVE-2022-20236
A-233124709
U-1883940*
High
gpu
CVE-2022-20238
A-233154555
U-1883892*
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
Severity
Component
CVE-2022-22096
A-213371834
QC-CR#3105585
Critical
Bluetooth
CVE-2022-22058
A-209075540
QC-CR#2747422
QC-CR#2338216
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-2022-25657
A-228101835*
High
Closed-source component
CVE-2022-25658
A-228101855*
High
Closed-source component
CVE-2022-25659
A-228101819*
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 2022-07-01 or later address all issues associated with the 2022-07-01 security patch level.
- Security patch levels of 2022-07-05 or later address all issues associated with the 2022-07-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]:[2022-07-01]
- [ro.build.version.security_patch]:[2022-07-05]
For some devices on Android 10 or later, the Google Play system update will have a date string that matches the 2022-07-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 2022-07-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 2022-07-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.
< /table>
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
Prefix
Reference
A-
Android bug ID
QC-
Qualcomm reference number
M-
MediaTek reference number
N-
NVIDIA reference number
B-
Broadcom reference number
U-
UNISOC reference number
Version
Date
Notes
1.0
July 6, 2022
Bulletin released
1.1
July 7, 2022
Bulletin revised to include AOSP links and revised CVE Table
Related news
In Boa, there is a possible escalation of privilege due to a stack buffer overflow. This could lead to remote escalation of privilege from a proximal attacker with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: A20210008; Issue ID: OSBNB00123241.
The HW_KEYMASTER module has a problem in releasing memory.Successful exploitation of this vulnerability may result in out-of-bounds memory access.
Uncaptured exceptions in the home screen module. Successful exploitation of this vulnerability may affect stability.
Out-of-bounds write vulnerability in the power consumption module. Successful exploitation of this vulnerability may cause the system to restart.
Memory corruption due to buffer overflow while parsing MKV clips with invalid bitmap size in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables
Vulnerability of writing data to an arbitrary address in the HW_KEYMASTER module. Successful exploitation of this vulnerability may affect confidentiality.
In audio DSP, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06558844; Issue ID: ALPS06558844.
In audio DSP, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06558844; Issue ID: ALPS06558844.
In audio DSP, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06558844; Issue ID: ALPS06558844.
In audio DSP, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06558844; Issue ID: ALPS06558844.
In audio DSP, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06558844; Issue ID: ALPS06558844.
In audio DSP, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06558844; Issue ID: ALPS06558844.
In multiple functions of AvatarPhotoController.java, there is a possible access to content owned by system content providers due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11Android ID: A-250637906