dbcve.org
AndroidOperating system · Google

CVE-2024-0014

HIGH · 7.8 CVSS v3.1 Published 2024-02-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In startInstall of UpdateFetcher.java, there is a possible way to trigger a malicious config update due to a logic error. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A logic error in the startInstall method of UpdateFetcher.java in Android's system update component allows a local attacker to trigger malicious configuration updates, resulting in local privilege escalation without requiring user interaction.

MitigationApply Android system updates promptly as this vulnerability is patched at the framework level; organizations should prioritize mobile device patch management.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:= 11.0= 12.0= 12.1= 13.0= 14.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check the Android OS version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if The version matches exactly 11.0, 12.0, 12.1, 13.0, or 14.0
  2. Verify system update component is present
    Check for the presence of UpdateFetcher.java or the UpdateFetcher system service via 'pm list packages -f | grep update' or by inspecting /system/framework/ services via ADB
    Affected if The UpdateFetcher component exists and is executable on the device
  3. Confirm security patch level
    Go to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB
    Affected if The security patch level is earlier than the March 2024 Android security bulletin (date before 2024-03-01)
  4. Check if system updates are enabled
    Navigate to Settings > System > System Update, or run 'settings get system system_update_auto_update_enabled' via ADB
    Affected if System update functionality is enabled and the device has not received the framework-level patch

A device is affected if it runs Android 11.0, 12.0, 12.1, 13.0, or 14.0 and has not received the March 2024 Android security update patch.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Android system updates promptly as this vulnerability is patched at the framework level; organizations should prioritize mobile device patch management.

Recommended fix Moderate confidence

Android 14 or later, or the latest Android Security Patch Level for your device

  1. 1. Apply the Android security update that addresses CVE-2024-0014. This vulnerability was patched in the Android Security Patch Level released after the affected versions.
  2. 2. Check for system updates on the affected device by navigating to Settings > Security > Security update > Check for update, or Settings > System > System update > Check for update.
  3. 3. Install any available security updates. The patch is delivered through the monthly Android security bulletin.
  4. 4. If the device no longer receives security updates from the OEM, consider upgrading to a newer Android version or replacing the device with a supported model.
Caveat May require device OEM support; some older devices may not receive patches

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0014 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-0014 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data