Security Resilience

CVE-2024-0044

Google Android 12.0 … 14.0

Public PoC
Published
11 March 2024
Modified
28 January 2025
Patch / advisory
CVSS Score v3.1 6.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.015 73th percentile
Risk Priority 58 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-0044 is a medium-severity Injection (CWE-74) vulnerability in Google Android. Its CVSS base score is 6.7 (Medium).

Operationally, ranked in the top 27% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-0044 is an improper input validation flaw in the createSessionInternal method of PackageInstallerService.java within the Android frameworks/base component. The vulnerability permits an attacker to invoke run-as functionality against any installed application, resulting in local privilege escalation on the device.

A local attacker with existing high-privileged access, such as an ADB shell or system-level component, can exploit the issue without user interaction or additional permissions to execute code or access data under the identity of arbitrary apps. This yields full control over the targeted application's files, permissions, and runtime behavior on the affected Android system.

Public advisories reference multiple upstream patches committed to the Android framework repository and note inclusion in the October 2024 Android security bulletin, directing administrators to apply the corresponding monthly updates or cherry-pick the listed commits to close the validation gap. The associated EPSS score has remained essentially flat near 0.09 with no material post-disclosure rise.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-27533Shared CWE-74, CWE-75
CVE-2024-39227Shared CWE-74, CWE-75
CVE-2024-39243Shared CWE-74, CWE-75
CVE-2024-27708Shared CWE-74, CWE-75
CVE-2024-23268Shared CWE-74, CWE-75
CVE-2023-0302Shared CWE-74, CWE-75
CVE-2024-23274Shared CWE-74, CWE-75
CVE-2020-17496Shared CWE-74
CVE-2025-20281Shared CWE-74
CVE-2023-43835Shared CWE-74

Affected Assets

google
android
12.0, 12.1, 13.0, 14.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 directly requires validation of information inputs to reject malformed or special-element content before it reaches downstream parsers.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.15 Logging partial match
finds

Logging supports detection of injection attempts but does not prevent the weakness.

finds

Monitoring activities can identify active injection attacks after they occur.

blocks

A.8.25 mandates a secure SDLC process that includes secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training to reduce injection flaws, but does not itself enforce or guarantee neutralization of special elements at runtime.

blocks

Application security requirements explicitly call for controls against injection attacks in software design.

blocks

A.8.27 mandates security-by-design principles (including distrust external input, data validation/sanitization, secure architecture layers, and design reviews against attack patterns) that reach injection when applied to output construction; this stops exploitation for a minority slice (e.g. where principles drive sanitization) but leaves most code-level injection defects untouched without further implementation rigor.

prevents

Secure coding standards require proper neutralization of special elements, directly addressing CWE-74.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-74, a class-level weakness, and none of its children carries one either.
  • No fine-grained STIG row for CWE-75, a class-level weakness, and none of its children carries one either.

References