CVE-2023-32882: Medium severity Google Android vulnerability
Published Jan 2, 2024
·Updated
In battery, there is a possible memory corruption 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: ALPS08308070; Issue ID: ALPS08308616.
Affected Software
23 affected components
All of the following
Any of the following
Google Android=12.0
Google Android=13.0
Any of the following
MediaTek Mt6762
MediaTek Mt6765
MediaTek Mt6833
MediaTek Mt6879
MediaTek Mt6883
MediaTek Mt6885
MediaTek Mt6983
MediaTek Mt8167
MediaTek Mt8168
MediaTek Mt8188
MediaTek Mt8321
MediaTek Mt8765
MediaTek Mt8766
MediaTek Mt8768
MediaTek Mt8781
MediaTek Mt8786
MediaTek Mt8788
MediaTek Mt8789
MediaTek Mt8791t
MediaTek Mt8797
MediaTek Mt8798
Event History
Jan 2, 2024
CVE Published
via MITRE·02:49 AM
Data Sourced
via MITRE·02:49 AM
DescriptionWeakness
Data Sourced
via NVD·03:15 AM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2023-32882?
CVE-2023-32882 is considered to have a high severity due to the potential for local privilege escalation.
2
How do I fix CVE-2023-32882?
To mitigate CVE-2023-32882, users should apply the available patch identified as ALPS08308070.
3
What versions of Android are affected by CVE-2023-32882?
CVE-2023-32882 affects Android versions 12.0 and 13.0.
4
Does CVE-2023-32882 require user interaction for exploitation?
No, exploitation of CVE-2023-32882 does not require user interaction.
5
What could be the consequences of exploiting CVE-2023-32882?
Exploitation of CVE-2023-32882 could lead to local escalation of privileges which may allow unauthorized system execution.