
CVE-2024-49749
https://notcve.org/view.php?id=CVE-2024-49749
21 Jan 2025 — In DGifSlurp of dgif_lib.c, there is a possible out of bounds write due to an integer overflow. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation. • https://source.android.com/security/bulletin/2025-01-01 • CWE-787: Out-of-bounds Write •

CVE-2024-49748
https://notcve.org/view.php?id=CVE-2024-49748
21 Jan 2025 — In gatts_process_primary_service_req of gatt_sr.cc, there is a possible out of bounds write due to a heap buffer overflow. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation. • https://source.android.com/security/bulletin/2025-01-01 • CWE-787: Out-of-bounds Write •

CVE-2024-49747
https://notcve.org/view.php?id=CVE-2024-49747
21 Jan 2025 — In gatts_process_read_by_type_req of gatt_sr.cc, there is a possible out of bounds write due to a logic error in the code. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation. • https://source.android.com/security/bulletin/2025-01-01 • CWE-94: Improper Control of Generation of Code ('Code Injection') •

CVE-2024-49745
https://notcve.org/view.php?id=CVE-2024-49745
21 Jan 2025 — In growData of Parcel.cpp, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. • https://source.android.com/security/bulletin/2025-01-01 • CWE-787: Out-of-bounds Write •

CVE-2024-49744
https://notcve.org/view.php?id=CVE-2024-49744
21 Jan 2025 — In checkKeyIntentParceledCorrectly of AccountManagerService.java, there is a possible way to bypass parcel mismatch mitigation due to unsafe deserialization. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation. • https://source.android.com/security/bulletin/2025-01-01 • CWE-276: Incorrect Default Permissions •

CVE-2024-49742
https://notcve.org/view.php?id=CVE-2024-49742
21 Jan 2025 — In onCreate of NotificationAccessConfirmationActivity.java , there is a possible way to hide an app with notification access in Settings due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation. • https://source.android.com/security/bulletin/2025-01-01 • CWE-269: Improper Privilege Management •

CVE-2024-49738
https://notcve.org/view.php?id=CVE-2024-49738
21 Jan 2025 — In writeInplace of Parcel.cpp, there is a possible out of bounds write. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. • https://source.android.com/security/bulletin/2025-01-01 • CWE-787: Out-of-bounds Write •

CVE-2024-49737
https://notcve.org/view.php?id=CVE-2024-49737
21 Jan 2025 — In applyTaskFragmentOperation of WindowOrganizerController.java, there is a possible way to launch arbitrary activities as the system UID 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 not needed for exploitation. • https://source.android.com/security/bulletin/2025-01-01 • CWE-276: Incorrect Default Permissions •

CVE-2024-49736
https://notcve.org/view.php?id=CVE-2024-49736
21 Jan 2025 — In onClick of MainClear.java, there is a possible way to trigger factory reset without explicit user consent due to a logic error in the code. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation. • https://source.android.com/security/bulletin/2025-01-01 • CWE-783: Operator Precedence Logic Error •

CVE-2024-49735
https://notcve.org/view.php?id=CVE-2024-49735
21 Jan 2025 — In multiple locations, there is a possible failure to persist permissions settings due to resource exhaustion. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. • https://source.android.com/security/bulletin/2025-01-01 • CWE-276: Incorrect Default Permissions •