# CVE-2024-0044: Privilege escalation in Android

> Local attackers can escalate privileges to run as any app due to improper input validation in the Android Package Installer Service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Mar 2024
- **Updated:** 28 Jan 2025
- **Also known as:** A-307532206, ASB-A-307532206

## What is CVE-2024-0044?

CVE-2024-0044 is a high-severity vulnerability in Google Android, published on 11 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In createSessionInternal of PackageInstallerService.java, there is a possible run-as any app due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-75 (Failure to Sanitize Special Elements into a Different Plane)

## Which versions are affected by CVE-2024-0044?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2024-0044?

Apply the vendor's patch.

## Is CVE-2024-0044 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-0044 exists.

Public exploit code:

- CVE-2024-0044:  a "run-as any app" high-severity vulnerability affecting Android versions 12 and 13 (github_poc): https://github.com/0xbinder/CVE-2024-0044
- RunAsAnyone: PoC and writeup for bypassing the initial patch of CVE-2024-0044, Android run-as any app vulnerability allowing privilege escalation from adb to installed app (github_poc): https://github.com/canyie/CVE-2024-0044
- Exfiltrate sensitive user data from apps on Android 12 and 13 using CVE-2024-0044 vulnerability remotely (github_poc): https://github.com/scs-labrat/android_autorooter
- EvilDroid automates the exploitation of CVE-2024-0044, installing malicious payloads on a target device and extracting sensitive data. It features automated ADB connection checks, APK pushing, UID extraction, payload generation, and real-time progress updates, providing a seamless and professional user experience. (github_poc): https://github.com/sridhar-sec/EvilDroid
- 利用 CVE-2024-0044 Android 权限提升下载任意目标App沙箱文件。 (github_poc): https://github.com/Re13orn/CVE-2024-0044-EXP
- CVE-2024-0044 (github_poc): https://github.com/MrW0l05zyn/cve-2024-0044

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-0044 and fix it if it is affected.

What it is: CVE-2024-0044 is a high-severity vulnerability in Google Android, published on 11 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-0044 exists.

Affected product: Google Android. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-0044/ (Markdown: https://insights.sbomify.com/CVE-2024-0044/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-0044
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-0044
- OSV: https://osv.dev/vulnerability/CVE-2024-0044

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-0044/
Summaries are generated and may contain mistakes; the official description above is the record.