Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-0046 Overview
CVE-2024-0046 is a local privilege escalation vulnerability in the Android installExistingPackageAsUser method of InstallPackageHelper.java. A logic error in the package installation flow allows a local attacker to bypass carrier restrictions and install packages that should otherwise be blocked. Exploitation requires no user interaction and no additional execution privileges beyond those already held by the calling process. The flaw is categorized under CWE-269: Improper Privilege Management and affects Android versions 12, 12L, 13, and 14. Google addressed the issue in the Android Security Bulletin March 2024.
Critical Impact
A local app can bypass carrier-imposed package restrictions to escalate privileges on affected Android devices without user interaction.
Affected Products
- Google Android 12.0
- Google Android 12.1
- Google Android 13.0
- Google Android 14.0
Discovery Timeline
- 2024-03-01 - Google releases security patch in the Android Security Bulletin
- 2024-03-11 - CVE-2024-0046 published to NVD
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-0046
Vulnerability Analysis
The vulnerability resides in the installExistingPackageAsUser method of InstallPackageHelper.java, part of the Android framework's package management subsystem. This method installs an existing package for a specified user without re-downloading the APK. Carrier restrictions normally gate which packages can be installed or enabled on a device based on operator policy. A logic error in the code path fails to enforce these restrictions in all execution branches. The result is a local privilege escalation: an unprivileged app can cause the system to install packages that carrier policy was intended to block.
Root Cause
The root cause is improper privilege management (CWE-269) in the install helper logic. The method does not consistently verify carrier restriction state before performing the install operation. This allows restricted packages to transit through a code path that assumes the caller is authorized. The upstream fix in AOSP commit d68cab5 corrects the restriction check.
Attack Vector
The attack vector is local. An attacker needs code execution on the device, typically through a malicious or compromised application installed by the user. Once running, the attacker invokes the vulnerable package installation path to install or enable a package subject to carrier restriction. No user interaction is required to trigger the flaw. The resulting installed package can then operate with privileges that violate the device's intended carrier policy, enabling further escalation.
No public proof-of-concept exploit is available for CVE-2024-0046 at the time of writing. Technical details of the fix are documented in the AOSP source change.
Detection Methods for CVE-2024-0046
Indicators of Compromise
- Unexpected packages installed on managed Android devices that should be blocked by carrier policy.
- Package installer activity originating from non-system apps targeting restricted package names.
- Mobile Device Management (MDM) telemetry showing installed app inventory drift from the baseline policy.
Detection Strategies
- Compare device application inventory against the carrier-approved baseline and alert on deviations.
- Monitor Android PackageManager events in enterprise mobility logs for installExistingPackageAsUser invocations by unprivileged callers.
- Use mobile threat defense (MTD) tooling to flag devices running patch levels earlier than the March 2024 security bulletin.
Monitoring Recommendations
- Enforce minimum Android security patch level (2024-03-01 or later) through MDM compliance policies.
- Collect application install events from enrolled devices into a central SIEM for anomaly review.
- Review third-party app installations on devices with carrier-restricted software baselines on a regular cadence.
How to Mitigate CVE-2024-0046
Immediate Actions Required
- Apply the Android security patch dated 2024-03-01 or later to all affected devices.
- Audit the fleet for devices running Android 12, 12L, 13, or 14 without the March 2024 patch level.
- Remove or quarantine untrusted applications on devices that cannot be patched immediately.
Patch Information
Google released the fix in the Android Security Bulletin March 2024. The code change is published in AOSP commit d68cab5ac1aa294ec4d0419bc0803a5577e4e43c. Device OEMs integrate the fix into vendor security patch level 2024-03-05 or later. Verify the patch level in Settings under About phone, Android version, Android security update.
Workarounds
- Restrict installation of apps from unknown sources through MDM policy on managed devices.
- Enforce Google Play Protect scanning to reduce exposure to malicious apps that could invoke the vulnerable path.
- Limit the number of users and work profiles on shared devices to reduce the local attack surface.
# Verify Android security patch level on a connected device via adb
adb shell getprop ro.build.version.security_patch
# Expected output for a patched device: 2024-03-01 or later
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

