dbcve.org
AndroidOperating system · Google

CVE-2024-40676

HIGH · 7.7 CVSS v3.1 Published 2025-01-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
No privileges 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 checkKeyIntent of AccountManagerService.java, there is a possible way to bypass intent security check and install an unknown app due to a confused deputy. 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 confused deputy vulnerability in Android's AccountManagerService allows bypassing the checkKeyIntent validation to install unknown apps without user interaction. The AccountManagerService improperly validates intent parameters, enabling a malicious application to trigger privileged operations that should be restricted.

MitigationApply the vendor-provided security patch for CVE-2024-40676 to the Android framework/system service components. For devices receiving updates, ensure timely deployment of the monthly security bulletin containing this fix.

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:= 12.0= 12.1= 13.0= 14.0= 15.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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. Identify Android version
    Go to Settings > About Phone > Android version (or use 'getprop ro.build.version.release' via ADB)
    Affected if The version listed is 12.0, 12.1, 13.0, 14.0, or 15.0
  2. Verify security patch level
    Go to Settings > About Phone > Security patch level (or use 'getprop ro.build.version.security_patch' via ADB)
    Affected if The patch level is earlier than the vendor security update containing the CVE-2024-40676 fix - compare against the monthly security bulletin release date for your Android version
  3. Confirm third-party app installation capability
    Check if 'Install unknown apps' permission is granted to any third-party application in Settings > Apps > special access > Install unknown apps
    Affected if Any untrusted third-party app has permission to install unknown apps and your Android version is in the affected list
  4. Review AccountManagerService access
    Use 'dumpsys account' via ADB shell to inspect AccountManagerService running status and check if any untrusted apps have accounts registered
    Affected if Untrusted third-party applications have accounts registered and your Android version is in the affected list

You are affected if your device runs Android 12.0 through 15.0 and has not received the vendor security patch addressing CVE-2024-40676.

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 the vendor-provided security patch for CVE-2024-40676 to the Android framework/system service components. For devices receiving updates, ensure timely deployment of the monthly security bulletin containing this fix.

Recommended fix Moderate confidence

Android 15 (for devices that can upgrade) or latest Android Security Patch Level (2024-09-01 or later)

  1. Check the current Android Security Patch Level on the device under Settings > About Phone > Security Patch Level
  2. Ensure the device has the latest security updates installed from the device manufacturer
  3. If the device cannot receive further updates, consider upgrading to a device running Android 15 or later which contains the fix for this vulnerability
  4. For enterprise-managed devices, ensure MDM policies enforce installation of pending security updates
  5. Verify the fix by confirming the AccountManagerService.java in the system has the type confusion vulnerability addressed in checkKeyIntent method
Caveat Upgrading to Android 15 may introduce UI changes, deprecate older apps, or remove support for legacy features; verify app compatibility before deployment

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

Fix this in Android Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
42.0 hours of engineering $7,320
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-40676 — 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-40676 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