Headline
CVE-2022-20467: Android Security Bulletin—March 2023
In isBluetoothShareUri of BluetoothOppUtility.java, there is a possible incorrect file read due to a confused deputy. This could lead to local information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-11 Android-12 Android-12L Android-13Android ID: A-225880741
Published March 6, 2023 | Updated March 8, 2023
The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Security patch levels of 2023-03-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 critical security vulnerability in the System component that could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation. 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.
2023-03-01 security patch level vulnerability details
In the sections below, we provide details for each of the security vulnerabilities that apply to the 2023-03-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 escalation of privilege after updating an app to a higher Target SDK with no additional execution privileges needed. User interaction is not needed for exploitation.
CVE
References
Type
Severity
Updated AOSP versions
CVE-2023-20906
A-221040577
EoP
High
11, 12, 12L, 13
CVE-2023-20911
A-242537498
EoP
High
11, 12, 12L, 13
CVE-2023-20917
A-242605257 [2]
EoP
High
11, 12, 12L, 13
CVE-2023-20947
A-237405974
EoP
High
12, 12L, 13
CVE-2023-20963
A-220302519
EoP
High
11, 12, 12L, 13
CVE-2023-20956
A-240140929
ID
High
12, 12L, 13
CVE-2023-20958
A-254803162
ID
High
13
CVE-2023-20964
A-238177121 [2]
DoS
High
12, 12L, 13
System
The most severe vulnerability in this section could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.
CVE
References
Type
Severity
Updated AOSP versions
CVE-2023-20951
A-258652631
RCE
Critical
11, 12, 12L, 13
CVE-2023-20954
A-261867748
RCE
Critical
11, 12, 12L, 13
CVE-2023-20926
A-253043058
EoP
High
12, 12L, 13
CVE-2023-20931
A-242535997
EoP
High
11, 12, 12L, 13
CVE-2023-20936
A-226927612
EoP
High
11, 12, 12L, 13
CVE-2023-20953
A-251778420
EoP
High
13
CVE-2023-20955
A-258653813
EoP
High
11, 12, 12L, 13
CVE-2023-20957
A-258422561
EoP
High
11, 12, 12L
CVE-2023-20959
A-249057848
EoP
High
13
CVE-2023-20960
A-250589026 [2] [3]
EoP
High
12L, 13
CVE-2023-20966
A-242299736
EoP
High
11, 12, 12L, 13
CVE-2022-4452
A-251802307
ID
High
13
CVE-2022-20467
A-225880741
ID
High
11, 12, 12L, 13
CVE-2023-20929
A-234442700
ID
High
13
CVE-2023-20952
A-186803518
ID
High
11, 12, 12L, 13
CVE-2023-20962
A-256590210
ID
High
13
CVE-2022-20499
A-246539931
DoS
High
12, 12L, 13
CVE-2023-20910
A-245299920
DoS
High
11, 12, 12L, 13
Google Play system updates
The following issues are included in Project Mainline components.
Subcomponent
CVE
Media Codecs
CVE-2023-20956
Permission Controller
CVE-2023-20947
Tethering
CVE-2023-20929
WiFi
CVE-2022-20499, CVE-2023-20910
2023-03-05 security patch level vulnerability details
In the sections below, we provide details for each of the security vulnerabilities that apply to the 2023-03-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.
Kernel
The vulnerability in this section could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
CVE
References
Type
Severity
Subcomponent
CVE-2021-33655
A-240019719
Upstream kernel [2] [3]
EoP
High
Frame Buffer
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
Subcomponent
CVE-2023-20620
A-264149248
M-ALPS07554558 *
High
adsp
CVE-2023-20621
A-264208866
M-ALPS07664755*
High
tinysys
CVE-2023-20623
A-264209787
M-ALPS07559778 *
High
ion
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
Subcomponent
CVE-2022-47459
A-264598465
U-2032124 *
High
Kernel
CVE-2022-47461
A-264834026
U-2066617 *
High
system
CVE-2022-47462
A-264834568
U-2066754 *
High
system
CVE-2022-47460
A-264831217
U-2044606 *
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
Subcomponent
CVE-2022-22075
A-193434313
QC-CR#3129138
QC-CR#3112398 [2] [3]
High
Display
CVE-2022-40537
A-261468700
QC-CR#3278869 [2] [3] [4]
High
Bluetooth
CVE-2022-40540
A-261470730
QC-CR#3280498
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
Subcomponent
CVE-2022-33213
A-238106224 *
Critical
Closed-source component
CVE-2022-33256
A-245402790 *
Critical
Closed-source component
CVE-2022-25655
A-261469326 *
High
Closed-source component
CVE-2022-25694
A-235102547 *
High
Closed-source component
CVE-2022-25705
A-235102507 *
High
Closed-source component
CVE-2022-25709
A-235102420 *
High
Closed-source component
CVE-2022-33242
A-245402503 *
High
Closed-source component
CVE-2022-33244
A-245402728 *
High
Closed-source component
CVE-2022-33250
A-245403450 *
High
Closed-source component
CVE-2022-33254
A-245403473 *
High
Closed-source component
CVE-2022-33272
A-245403311 *
High
Closed-source component
CVE-2022-33278
A-245402730 *
High
Closed-source component
CVE-2022-33309
A-261468683 *
High
Closed-source component
CVE-2022-40515
A-261469638 *
High
Closed-source component
CVE-2022-40527
A-261470448 *
High
Closed-source component
CVE-2022-40530
A-261471028 *
High
Closed-source component
CVE-2022-40531
A-261469091 *
High
Closed-source component
CVE-2022-40535
A-261470732 *
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 2023-03-01 or later address all issues associated with the 2023-03-01 security patch level.
- Security patch levels of 2023-03-05 or later address all issues associated with the 2023-03-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]:[2023-03-01]
- [ro.build.version.security_patch]:[2023-03-05]
For some devices on Android 10 or later, the Google Play system update will have a date string that matches the 2023-03-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 2023-03-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 2023-03-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
U-
UNISOC 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
March 6, 2023
Bulletin Published
1.1
March 8, 2023
Bulletin revised to include AOSP links
Related news
Insufficient data validation in crosvm in Google Chrome prior to 107.0.5304.62 allowed a remote attacker to potentially exploit object corruption via a crafted HTML page. (Chromium security severity: High)
In SettingsHomepageActivity.java, there is a possible way to launch arbitrary activities via Settings due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.
Logging Subsystem 5.7.2 - Red Hat OpenShift Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.This content is licensed under the Creative Commons Attribution 4.0 International License (https://creativecommons.org/licenses/by/4.0/). If you distribute this content, or a modified version of it, you must provide attribution to Red Hat Inc. and provide a link to the original. Related CVEs: * CVE-2022-41723: A flaw was found in golang. A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests. * CVE-2023-27539: A denial of service vulnerability was found in rubygem-rack in how it parses headers. A carefully crafted input can cause header parsing to take an unexpe...
The hwPartsDFR module has a vulnerability in API calling verification. Successful exploitation of this vulnerability may affect device confidentiality.
An update for kernel-rt is now available for Red Hat Enterprise Linux 8. Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.This content is licensed under the Creative Commons Attribution 4.0 International License (https://creativecommons.org/licenses/by/4.0/). If you distribute this content, or a modified version of it, you must provide attribution to Red Hat Inc. and provide a link to the original. Related CVEs: * CVE-2021-26341: A flaw was found in hw. This issue can cause AMD CPUs to transiently execute beyond unconditional direct branches. * CVE-2021-33655: An out-of-bounds write flaw was found in the Linux kernel’s framebuffer-based console driver functionality in the way a user triggers ioctl FBIOPUT_VSCREENINFO with malicious data. This flaw allows a local user t...
Red Hat Security Advisory 2023-2148-01 - The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements. Issues addressed include buffer overflow, bypass, denial of service, double free, memory leak, null pointer, out of bounds read, privilege escalation, traversal, and use-after-free vulnerabilities.
An update for kernel-rt is now available for Red Hat Enterprise Linux 9. Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.This content is licensed under the Creative Commons Attribution 4.0 International License (https://creativecommons.org/licenses/by/4.0/). If you distribute this content, or a modified version of it, you must provide attribution to Red Hat Inc. and provide a link to the original. Related CVEs: * CVE-2021-26341: A flaw was found in hw. This issue can cause AMD CPUs to transiently execute beyond unconditional direct branches. * CVE-2021-33655: An out-of-bounds write flaw was found in the Linux kernel’s framebuffer-based console driver functionality in the way a user triggers ioctl FBIOPUT_VSCREENINFO with malicious data. This flaw allows a local user t...
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added two vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog, based on evidence of active exploitation. The two flaws are listed below - CVE-2023-20963 (CVSS score: 7.8) - Android Framework Privilege Escalation Vulnerability CVE-2023-29492 (CVSS score: TBD) - Novi Survey Insecure Deserialization Vulnerability
Categories: Android Categories: News Tags: Android Tags: 2023-03-05 Tags: RCE Tags: EoP Tags: CVE-2023-20951 Tags: CVE-2023-20954 Tags: CVE-2022-33213 Tags: CVE-2022-33256 Tags: CVE-2021-33655 The March security updates for Android include fixes for two critical remote code execution (RCE) vulnerabilities. Update as soon as you can! (Read more...) The post Update Android now! Two critical vulnerabilities patched appeared first on Malwarebytes Labs.
Categories: Android Categories: News Tags: Android Tags: 2023-03-05 Tags: RCE Tags: EoP Tags: CVE-2023-20951 Tags: CVE-2023-20954 Tags: CVE-2022-33213 Tags: CVE-2022-33256 Tags: CVE-2021-33655 The March security updates for Android include fixes for two critical remote code execution (RCE) vulnerabilities. Update as soon as you can! (Read more...) The post Update Android now! Two critical vulnerabilities patched appeared first on Malwarebytes Labs.
Categories: Android Categories: News Tags: Android Tags: 2023-03-05 Tags: RCE Tags: EoP Tags: CVE-2023-20951 Tags: CVE-2023-20954 Tags: CVE-2022-33213 Tags: CVE-2022-33256 Tags: CVE-2021-33655 The March security updates for Android include fixes for two critical remote code execution (RCE) vulnerabilities. Update as soon as you can! (Read more...) The post Update Android now! Two critical vulnerabilities patched appeared first on Malwarebytes Labs.
Categories: Android Categories: News Tags: Android Tags: 2023-03-05 Tags: RCE Tags: EoP Tags: CVE-2023-20951 Tags: CVE-2023-20954 Tags: CVE-2022-33213 Tags: CVE-2022-33256 Tags: CVE-2021-33655 The March security updates for Android include fixes for two critical remote code execution (RCE) vulnerabilities. Update as soon as you can! (Read more...) The post Update Android now! Two critical vulnerabilities patched appeared first on Malwarebytes Labs.
In apu, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07629576; Issue ID: ALPS07629576.
In apu, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07629576; Issue ID: ALPS07629576.
In apu, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07629576; Issue ID: ALPS07629576.
Improper Authentication vulnerability in the encrypted volumes and auto mount features of Western Digital My Cloud devices allows insecure direct access to the drive information in the case of a device reset. This issue affects: Western Digital My Cloud My Cloud versions prior to 5.25.124 on Linux.
Ubuntu Security Notice 5655-1 - It was discovered that the framebuffer driver on the Linux kernel did not verify size limits when changing font or screen size, leading to an out-of- bounds write. A local attacker could use this to cause a denial of service or possibly execute arbitrary code. Duoming Zhou discovered that race conditions existed in the timer handling implementation of the Linux kernel's Rose X.25 protocol layer, resulting in use-after-free vulnerabilities. A local attacker could use this to cause a denial of service.
Ubuntu Security Notice 5654-1 - It was discovered that the framebuffer driver on the Linux kernel did not verify size limits when changing font or screen size, leading to an out-of- bounds write. A local attacker could use this to cause a denial of service or possibly execute arbitrary code. Moshe Kol, Amit Klein and Yossi Gilad discovered that the IP implementation in the Linux kernel did not provide sufficient randomization when calculating port offsets. An attacker could possibly use this to expose sensitive information.
Ubuntu Security Notice 5648-1 - It was discovered that the framebuffer driver on the Linux kernel did not verify size limits when changing font or screen size, leading to an out-of- bounds write. A local attacker could use this to cause a denial of service or possibly execute arbitrary code. Duoming Zhou discovered that race conditions existed in the timer handling implementation of the Linux kernel's Rose X.25 protocol layer, resulting in use-after-free vulnerabilities. A local attacker could use this to cause a denial of service.
Ubuntu Security Notice 5640-1 - It was discovered that the framebuffer driver on the Linux kernel did not verify size limits when changing font or screen size, leading to an out-of- bounds write. A local attacker could use this to cause a denial of service or possibly execute arbitrary code. Duoming Zhou discovered that race conditions existed in the timer handling implementation of the Linux kernel's Rose X.25 protocol layer, resulting in use-after-free vulnerabilities. A local attacker could use this to cause a denial of service.
Ubuntu Security Notice 5635-1 - It was discovered that the framebuffer driver on the Linux kernel did not verify size limits when changing font or screen size, leading to an out-of- bounds write. A local attacker could use this to cause a denial of service or possibly execute arbitrary code. Duoming Zhou discovered that race conditions existed in the timer handling implementation of the Linux kernel's Rose X.25 protocol layer, resulting in use-after-free vulnerabilities. A local attacker could use this to cause a denial of service.
Ubuntu Security Notice 5633-1 - It was discovered that the framebuffer driver on the Linux kernel did not verify size limits when changing font or screen size, leading to an out-of-bounds write. A local attacker could use this to cause a denial of service or possibly execute arbitrary code. Duoming Zhou discovered that race conditions existed in the timer handling implementation of the Linux kernel's Rose X.25 protocol layer, resulting in use-after-free vulnerabilities. A local attacker could use this to cause a denial of service.
Ubuntu Security Notice 5624-1 - It was discovered that the framebuffer driver on the Linux kernel did not verify size limits when changing font or screen size, leading to an out-of- bounds write. A local attacker could use this to cause a denial of service or possibly execute arbitrary code. Duoming Zhou discovered that race conditions existed in the timer handling implementation of the Linux kernel's Rose X.25 protocol layer, resulting in use-after-free vulnerabilities. A local attacker could use this to cause a denial of service.
Ubuntu Security Notice 5622-1 - It was discovered that the framebuffer driver on the Linux kernel did not verify size limits when changing font or screen size, leading to an out-of- bounds write. A local attacker could use this to cause a denial of service or possibly execute arbitrary code. Moshe Kol, Amit Klein and Yossi Gilad discovered that the IP implementation in the Linux kernel did not provide sufficient randomization when calculating port offsets. An attacker could possibly use this to expose sensitive information.
Ubuntu Security Notice 5621-1 - It was discovered that the framebuffer driver on the Linux kernel did not verify size limits when changing font or screen size, leading to an out-of- bounds write. A local attacker could use this to cause a denial of service or possibly execute arbitrary code. Domingo Dirutigliano and Nicola Guerrera discovered that the netfilter subsystem in the Linux kernel did not properly handle rules that truncated packets below the packet header size. When such rules are in place, a remote attacker could possibly use this to cause a denial of service.