Headline
CVE-2023-45781: Android Security Bulletin—December 2023
In parse_gap_data of utils.cc, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with User execution privileges needed. User interaction is not needed for exploitation.
Published December 4, 2023
The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Security patch levels of 2023-12-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 (proximal/adjacent) 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-12-01 security patch level vulnerability details
In the sections below, we provide details for each of the security vulnerabilities that apply to the 2023-12-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 remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
CVE
References
Type
Severity
Updated AOSP versions
CVE-2023-40077
A-298057702
EoP
Critical
11, 12, 12L, 13, 14
CVE-2023-40076
A-303835719
ID
Critical
14
CVE-2023-40079
A-278722815
EoP
High
14
CVE-2023-40089
A-294228721
EoP
High
14
CVE-2023-40091
A-283699145
EoP
High
11, 12, 12L, 13, 14
CVE-2023-40094
A-288896339
EoP
High
11, 12, 12L, 13, 14
CVE-2023-40095
A-273729172
EoP
High
11, 12, 12L, 13, 14
CVE-2023-40096
A-268724205
EoP
High
11, 12, 12L, 13, 14
CVE-2023-40103
A-197260547
EoP
High
14
CVE-2023-45774
A-288113797
EoP
High
11, 12, 12L, 13, 14
CVE-2023-45777
A-299930871
EoP
High
13, 14
CVE-2023-21267
A-218495634
ID
High
11, 12, 12L, 13, 14
CVE-2023-40073
A-287640400
ID
High
11, 12, 12L, 13, 14
CVE-2023-40081
A-284297452
ID
High
11, 12, 12L, 13, 14
CVE-2023-40092
A-288110451
ID
High
11, 12, 12L, 13, 14
CVE-2023-40074
A-247513680
DoS
High
11, 12, 12L, 13
CVE-2023-40075
A-281061287
DoS
High
11, 12, 12L, 13, 14
System
The most severe vulnerability in this section could lead to remote (proximal/adjacent) code execution with no additional execution privileges needed. User interaction is not needed for exploitation.
CVE
References
Type
Severity
Updated AOSP versions
CVE-2023-40088
A-291500341
RCE
Critical
11, 12, 12L, 13, 14
CVE-2023-40078
A-275626001
EoP
High
14
CVE-2023-40080
A-275057843
EoP
High
13, 14
CVE-2023-40082
A-290909089
EoP
High
14
CVE-2023-40084
A-272382770
EoP
High
11, 12, 12L, 13, 14
CVE-2023-40087
A-275895309
EoP
High
11, 12, 12L, 13, 14
CVE-2023-40090
A-274478807
EoP
High
11, 12, 12L, 13, 14
CVE-2023-40097
A-295334906
EoP
High
11, 12, 12L, 13
CVE-2023-45773
A-275057847
EoP
High
13, 14
CVE-2023-45775
A-275340684
EoP
High
14
CVE-2023-45776
A-282234870
EoP
High
14
CVE-2023-21394
A-296915211
ID
High
11, 12, 12L, 13
CVE-2023-35668
A-283962802
ID
High
11, 12, 12L, 13
CVE-2023-40083
A-277590580
ID
High
12, 12L, 13, 14
CVE-2023-40098
A-288896269
ID
High
12, 12L, 13, 14
CVE-2023-45781
A-275553827
ID
High
12, 12L, 13, 14
Google Play system updates
There are no security issues addressed in Google Play system updates (Project Mainline) this month.
2023-12-05 security patch level vulnerability details
In the sections below, we provide details for each of the security vulnerabilities that apply to the 2023-12-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.
System
The vulnerability in this section could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
CVE
References
Type
Severity
Updated AOSP versions
CVE-2023-45866
A-294854926
EoP
Critical
11, 12, 12L, 13, 14
Arm components
These vulnerabilities affect Arm components and further details are available directly from Arm. The severity assessment of these issues is provided directly by Arm.
CVE
References
Severity
Subcomponent
CVE-2023-3889
A-295942985 *
High
Mali
CVE-2023-4272
A-296910715 *
High
Mali
CVE-2023-32804
A-272772567 *
High
Mali
Imagination Technologies
These vulnerabilities affect Imagination Technologies components and further details are available directly from Imagination Technologies. The severity assessment of these issues is provided directly by Imagination Technologies.
CVE
References
Severity
Subcomponent
CVE-2023-21162
A-292004168 *
High
PowerVR-GPU
CVE-2023-21163
A-292003338 *
High
PowerVR-GPU
CVE-2023-21164
A-292002918 *
High
PowerVR-GPU
CVE-2023-21166
A-292002163 *
High
PowerVR-GPU
CVE-2023-21215
A-291982610 *
High
PowerVR-GPU
CVE-2023-21216
A-291999952 *
High
PowerVR-GPU
CVE-2023-21217
A-292087506 *
High
PowerVR-GPU
CVE-2023-21218
A-292000190 *
High
PowerVR-GPU
CVE-2023-21228
A-291999439 *
High
PowerVR-GPU
CVE-2023-21263
A-305095406 *
High
PowerVR-GPU
CVE-2023-21401
A-305091236 *
High
PowerVR-GPU
CVE-2023-21402
A-305093885 *
High
PowerVR-GPU
CVE-2023-21403
A-305096969 *
High
PowerVR-GPU
CVE-2023-35690
A-305095935 *
High
PowerVR-GPU
CVE-2023-21227
A-291998937 *
High
PowerVR-GPU
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-32818
A-294770901
M-ALPS08013430, M-ALPS08163896 *
High
vdec
CVE-2023-32847
A-302982512
M-ALPS08241940 *
High
audio
CVE-2023-32848
A-302982513
M-ALPS08163896 *
High
vdec
CVE-2023-32850
A-302983201
M-ALPS08016659 *
High
decoder
CVE-2023-32851
A-302986375
M-ALPS08016652 *
High
decoder
Misc OEM
This vulnerability affects Misc OEM components and further details are available directly from Misc OEM. The severity assessment of this issue is provided directly by Misc OEM.
CVE
References
Severity
Subcomponent
CVE-2023-45779
A-301094654 *
High
System UI
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-48456
A-300376910
U-1914157 *
High
Kernel
CVE-2022-48461
A-300368868
U-1905646 *
High
Kernel
CVE-2022-48454
A-300382178
U-2220123 *
High
Android
CVE-2022-48455
A-300385151
U-2220123 *
High
Android
CVE-2022-48457
A-300368872
U-2161952 *
High
Android
CVE-2022-48458
A-300368874
U-2161952 *
High
Android
CVE-2022-48459
A-300368875
U-2161952 *
High
Android
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-2023-28588
A-285902729
QC-CR#3417458
High
Bluetooth
CVE-2023-33053
A-299146326
QC-CR#3453941
High
Kernel
CVE-2023-33063
A-266568298
QC-CR#3447219 [2]
High
Kernel
CVE-2023-33079
A-299146464
QC-CR#3446191
High
Audio
CVE-2023-33087
A-299146536
QC-CR#3508356 [2]
High
Kernel
CVE-2023-33092
A-299146537
QC-CR#3507292
High
Bluetooth
CVE-2023-33106
A-300941008
QC-CR#3612841
High
Display
CVE-2023-33107
A-299649795
QC-CR#3611296
High
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
Severity
Subcomponent
CVE-2022-40507
A-261468680 *
Critical
Closed-source component
CVE-2022-22076
A-261469325 *
High
Closed-source component
CVE-2023-21652
A-268059928 *
High
Closed-source component
CVE-2023-21662
A-271879599 *
High
Closed-source component
CVE-2023-21664
A-271879160 *
High
Closed-source component
CVE-2023-28546
A-285902568 *
High
Closed-source component
CVE-2023-28550
A-280341535 *
High
Closed-source component
CVE-2023-28551
A-280341572 *
High
Closed-source component
CVE-2023-28585
A-285902652 *
High
Closed-source component
CVE-2023-28586
A-285903022 *
High
Closed-source component
CVE-2023-28587
A-285903202 *
High
Closed-source component
CVE-2023-33017
A-285902412 *
High
Closed-source component
CVE-2023-33018
A-285902728 *
High
Closed-source component
CVE-2023-33022
A-285903201 *
High
Closed-source component
CVE-2023-33054
A-295020170 *
High
Closed-source component
CVE-2023-33080
A-299147105 *
High
Closed-source component
CVE-2023-33081
A-299145668 *
High
Closed-source component
CVE-2023-33088
A-299146964 *
High
Closed-source component
CVE-2023-33089
A-299146027 *
High
Closed-source component
CVE-2023-33097
A-299147106 *
High
Closed-source component
CVE-2023-33098
A-299146466 *
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-12-01 or later address all issues associated with the 2023-12-01 security patch level.
- Security patch levels of 2023-12-05 or later address all issues associated with the 2023-12-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-12-01]
- [ro.build.version.security_patch]:[2023-12-05]
For some devices on Android 10 or later, the Google Play system update will have a date string that matches the 2023-12-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-12-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-12-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
December 4, 2023
Bulletin published
Related news
Why the company took so long to address the issue is not known given that most other stakeholders had a fix out for the issue months ago.
A coalition of dozens of countries, including France, the U.K., and the U.S., along with tech companies such as Google, MDSec, Meta, and Microsoft, have signed a joint agreement to curb the abuse of commercial spyware to commit human rights abuses. The initiative, dubbed the Pall Mall Process, aims to tackle the proliferation and irresponsible use of commercial cyber intrusion tools by
Gentoo Linux Security Advisory 202401-3 - Multiple vulnerabilities have been discovered in Bluez, the worst of which can lead to privilege escalation. Versions greater than or equal to 5.70-r1 are affected.
Plus: Apple shuts down a Flipper Zero Attack, Microsoft patches more than 30 vulnerabilities, and more critical updates for the last month of 2023.
Debian Linux Security Advisory 5584-1 - It was reported that the BlueZ's HID profile implementation is not inline with the HID specification which mandates the use of Security Mode 4. The HID profile configuration option ClassicBondedOnly now defaults to "true" to make sure that input connections only come from bonded device connections.
Apple Security Advisory 12-11-2023-4 - macOS Sonoma 14.2 addresses code execution, out of bounds read, and spoofing vulnerabilities.
Apple Security Advisory 12-11-2023-2 - iOS 17.2 and iPadOS 17.2 addresses code execution and spoofing vulnerabilities.
Apple on Monday released security patches for iOS, iPadOS, macOS, tvOS, watchOS, and Safari web browser to address multiple security flaws, in addition to backporting fixes for two recently disclosed zero-days to older devices. This includes updates for 12 security vulnerabilities in iOS and iPadOS spanning AVEVideoEncoder, ExtensionKit, Find My, ImageIO, Kernel, Safari
Multiple memory corruption issues were addressed with improved input validation. This issue is fixed in macOS Sonoma 14.2. Processing a maliciously crafted file may lead to unexpected app termination or arbitrary code execution.
A privacy issue was addressed with improved private data redaction for log entries. This issue is fixed in macOS Sonoma 14.2, iOS 17.2 and iPadOS 17.2, watchOS 10.2. An app may be able to access sensitive user data.
By Waqas Another day, another Bluetooth vulnerability impacting billions of devices worldwide! This is a post from HackRead.com Read the original post: Bluetooth Vulnerability Enables Keystroke Injection on Android, Linux, macOS, iOS
Bluetooth HID Hosts in BlueZ may permit an unauthenticated Peripheral role HID Device to initiate and establish an encrypted connection, and accept HID keyboard reports, potentially permitting injection of HID messages when no user interaction has occurred in the Central role to authorize such access. An example affected package is bluez 5.64-0ubuntu1 in Ubuntu 22.04LTS. NOTE: in some cases, a CVE-2020-0556 mitigation would have already addressed this Bluetooth HID Hosts issue.
Ubuntu Security Notice 6540-1 - It was discovered that BlueZ did not properly restrict non-bonded devices from injecting HID events into the input subsystem. This could allow a physically proximate attacker to inject keystrokes and execute arbitrary commands whilst the device is discoverable.
Android phones are vulnerable to attacks that allow a remote execution of malicious code and it requires no user interaction.
A critical Bluetooth security flaw could be exploited by threat actors to take control of Android, Linux, macOS and iOS devices. Tracked as CVE-2023-45866, the issue relates to a case of authentication bypass that enables attackers to connect to susceptible devices and inject keystrokes to achieve code execution as the victim. "Multiple Bluetooth stacks have authentication bypass
Chipmaker Qualcomm has released more information about three high-severity security flaws that it said came under "limited, targeted exploitation" back in October 2023. The vulnerabilities are as follows - CVE-2023-33063 (CVSS score: 7.8) - Memory corruption in DSP Services during a remote call from HLOS to DSP. CVE-2023-33106 (CVSS score: 8.4) - Memory corruption in
Vulnerability of identity verification being bypassed in the face unlock module. Successful exploitation of this vulnerability will affect integrity and confidentiality.
In NFC, there is a possible way to setup a default contactless payment app without user consent due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Categories: Android Categories: News Tags: Google Tags: Android Tags: Qualcomm Tags: webp Tags: ARM Mali Tags: cve-2023-4863 Tags: cve-2023-4211 Tags: cve-2023-33106 Tags: cve-2023-33107 Tags: cve-2023-22071 Tags: cve-2023-33063 Tags: 2023-10-006 Tags: patch level Google has patched 53 vulnerabilities in its Android October security updates, two of which are known to be actively exploited. (Read more...) The post Update your Android devices now! Google patches two actively exploited vulnerabilities appeared first on Malwarebytes Labs.
Categories: Android Categories: News Tags: Google Tags: Android Tags: Qualcomm Tags: webp Tags: ARM Mali Tags: cve-2023-4863 Tags: cve-2023-4211 Tags: cve-2023-33106 Tags: cve-2023-33107 Tags: cve-2023-22071 Tags: cve-2023-33063 Tags: 2023-10-006 Tags: patch level Google has patched 53 vulnerabilities in its Android October security updates, two of which are known to be actively exploited. (Read more...) The post Update your Android devices now! Google patches two actively exploited vulnerabilities appeared first on Malwarebytes Labs.
Categories: Android Categories: News Tags: Google Tags: Android Tags: Qualcomm Tags: webp Tags: ARM Mali Tags: cve-2023-4863 Tags: cve-2023-4211 Tags: cve-2023-33106 Tags: cve-2023-33107 Tags: cve-2023-22071 Tags: cve-2023-33063 Tags: 2023-10-006 Tags: patch level Google has patched 53 vulnerabilities in its Android October security updates, two of which are known to be actively exploited. (Read more...) The post Update your Android devices now! Google patches two actively exploited vulnerabilities appeared first on Malwarebytes Labs.
Chipmaker Qualcomm has released security updates to address 17 vulnerabilities in various components, while warning that three other zero-days have come under active exploitation. Of the 17 flaws, three are rated Critical, 13 are rated High, and one is rated Medium in severity. "There are indications from Google Threat Analysis Group and Google Project Zero that CVE-2023-33106, CVE-2023-33107,
Chipmaker Qualcomm has released security updates to address 17 vulnerabilities in various components, while warning that three other zero-days have come under active exploitation. Of the 17 flaws, three are rated Critical, 13 are rated High, and one is rated Medium in severity. "There are indications from Google Threat Analysis Group and Google Project Zero that CVE-2023-33106, CVE-2023-33107,
Chipmaker Qualcomm has released security updates to address 17 vulnerabilities in various components, while warning that three other zero-days have come under active exploitation. Of the 17 flaws, three are rated Critical, 13 are rated High, and one is rated Medium in severity. "There are indications from Google Threat Analysis Group and Google Project Zero that CVE-2023-33106, CVE-2023-33107,
DoS vulnerability in the PMS module. Successful exploitation of this vulnerability may cause the system to restart.
In doKeyguardLocked of KeyguardViewMediator.java, there is a possible way to bypass lockdown mode with screen pinning due to a logic error in the code. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.