HomeLatest UpdatesAndroid Security Bulletin—January 2024  |  Android Open Source Project

Android Security Bulletin—January 2024  |  Android Open Source Project


Published January 3, 2024

The Android Security Bulletin contains details of security vulnerabilities
affecting Android devices. Security patch levels of
2024-01-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 high security vulnerability in the
Framework component that could lead to local escalation of privilege 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.

2024-01-01
security patch level vulnerability details

In the sections below, we provide details for each of the security
vulnerabilities that apply to the 2024-01-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 with no additional execution privileges needed.

CVE References Type Severity Updated AOSP versions
CVE-2023-21245 A-222446076 EoP High 11, 12, 12L, 13, 14
CVE-2024-0015 A-300090204 EoP High 11, 12, 12L, 13
CVE-2024-0018 A-300476626 EoP High 11, 12, 12L, 13, 14
CVE-2024-0023 A-283099444 EoP High 11, 12, 12L, 13, 14
CVE-2024-0019 A-294104969 ID High 12, 12L, 13, 14

System

The most severe vulnerability in this section could lead to local
escalation
of privilege with no additional execution privileges needed.

CVE References Type Severity Updated AOSP versions
CVE-2024-0021 A-282934003 EoP High 13, 14
CVE-2023-40085 A-269271098 ID High 12, 12L, 13
CVE-2024-0016 A-279169188 ID High 11, 12, 12L, 13, 14
CVE-2024-0017 A-285142084 ID High 11, 12, 12L, 13, 14
CVE-2024-0020 A-299614635 ID High 11, 12, 12L, 13, 14

Google Play system updates

The following issues are included in Project Mainline components.

Subcomponent CVE
Media Codecs CVE-2024-0018

2024-01-05
security patch level vulnerability details

In the sections below, we provide details for each of the security
vulnerabilities that apply to the 2024-01-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.

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-4295 A-275619408
*
High Mali
CVE-2023-5427 A-308188337
*
High Mali

Imagination Technologies

This vulnerability affects Imagination Technologies components and further
details are available directly from Imagination Technologies.
The severity assessment of this issue is provided directly by Imagination
Technologies.

CVE References Severity Subcomponent
CVE-2023-21165 A-292001469
*
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-32874 A-309364195

M-MOLY01161803
*
High Modem IMS Stack
CVE-2023-32872 A-309367791

M-ALPS08308607
*
High keyInstall

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-2023-48340 A-311290655

U-2228010
*
High Android
CVE-2023-48341 A-311288752

U-2227052
*
High Android
CVE-2023-48342 A-311288747

U-2227689
*
High Android
CVE-2023-48343 A-311290653

U-2227689
*
High Android
CVE-2023-48344 A-311282174

U-2266624
*
High Android
CVE-2023-48348 A-311279656

U-2227052
*
High Android
CVE-2023-48349 A-311279652

U-2219058
*
High Android
CVE-2023-48350 A-311279655

U-2219062
*
High Android
CVE-2023-48351 A-311273934

U-2219064
*
High Android
CVE-2023-48352 A-311273933

U-2153501
*
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.

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-2023-21651 A-268059825
*
Critical Closed-source component
CVE-2023-33025 A-290061199
*
Critical Closed-source component
CVE-2023-33036 A-290061245
*
Critical Closed-source component
CVE-2022-33275 A-280342403
*
High Closed-source component
CVE-2023-28544 A-280342360
*
High Closed-source component
CVE-2023-28548 A-280342264
*
High Closed-source component
CVE-2023-28557 A-280342461
*
High Closed-source component
CVE-2023-28558 A-280342364
*
High Closed-source component
CVE-2023-28559 A-280342379
*
High Closed-source component
CVE-2023-28560 A-280342458
*
High Closed-source component
CVE-2023-28564 A-280342073
*
High Closed-source component
CVE-2023-28565 A-280341573
*
High Closed-source component
CVE-2023-28567 A-280341537
*
High Closed-source component
CVE-2023-33014 A-290060890
*
High Closed-source component
CVE-2023-33030 A-290061201
*
High Closed-source component
CVE-2023-33032 A-290061658
*
High Closed-source component
CVE-2023-33033 A-290060591
*
High Closed-source component
CVE-2023-33037 A-290061062
*
High Closed-source component
CVE-2023-33040 A-290061061
*
High Closed-source component
CVE-2023-33043 A-295039021
*
High Closed-source component
CVE-2023-33044 A-295039321
*
High Closed-source component
CVE-2023-33062 A-303101463
*
High Closed-source component
CVE-2023-33109 A-303102144
*
High Closed-source component
CVE-2023-33112 A-303101016
*
High Closed-source component
CVE-2023-43511 A-303101323
*
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 2024-01-01 or later address
    all issues associated with the 2024-01-01 security patch
    level.
  • Security patch levels of 2024-01-05 or later address
    all issues associated with the 2024-01-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]:[2024-01-01]
  • [ro.build.version.security_patch]:[2024-01-05]

For some devices on Android 10 or later, the Google Play system update
will have a date string that matches the 2024-01-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 2024-01-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 2024-01-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 January 3, 2024 Bulletin published.



Source link

RELATED ARTICLES

Most Popular

Recent Comments