dbcve.org
AndroidOperating system · Google

CVE-2024-49744

HIGH · 7.8 CVSS v3.1 Published 2025-01-21
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 checkKeyIntentParceledCorrectly of AccountManagerService.java, there is a possible way to bypass parcel mismatch mitigation due to unsafe deserialization. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is 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 vulnerability in Android's AccountManagerService.java (checkKeyIntentParceledCorrectly method) allows bypassing parcel mismatch mitigations through unsafe deserialization, enabling local privilege escalation without additional execution privileges. User interaction is required for exploitation.

MitigationApply the latest Android security patch from Google/device manufacturer. This is a framework-level vulnerability requiring source-level code changes to implement proper deserialization validation in AccountManagerService.

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
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 Android version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell. Compare the displayed version to 12.0, 12.1, 13.0, 14.0, or 15.0.
    Affected if The device runs Android 12.0, 12.1, 13.0, 14.0, or 15.0 exactly.
  2. Check security patch level
    Go to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB shell. Note the date of the installed patch.
    Affected if The security patch is older than the November 2024 Android security update.
  3. Verify AccountManagerService component
    Check if the AccountManagerService is accessible on the device by examining /system/framework/services.jar or searching for 'AccountManagerService' in the framework. Use 'dumpsys account' via ADB shell to list account manager service status.
    Affected if The AccountManagerService component exists and is active on the device (standard on all Android devices with Google Play services).

The device is likely affected if it runs Android 12.0 through 15.0 and lacks the November 2024 or later security patch, as the vulnerability resides in the framework-level AccountManagerService component.

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 latest Android security patch from Google/device manufacturer. This is a framework-level vulnerability requiring source-level code changes to implement proper deserialization validation in AccountManagerService.

Recommended fix Moderate confidence

Android 15 or the latest available Android security patch that addresses this vulnerability

  1. Check the Android Security Bulletin for CVE-2024-49744 to identify the specific security patch level that addresses this vulnerability
  2. Apply the latest Android security patch available for your device model
  3. If a security patch is not available for your current Android version, upgrade to a newer Android version (Android 15 or later) that includes the fix
  4. Verify the security patch level by going to Settings > About Phone > Android version and confirming the Security Patch level
Caveat Upgrading to a newer Android version may cause compatibility issues with existing apps or configurations; ensure backup of data and review app compatibility before upgrading

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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