dbcve.org
AndroidOperating system · Google

CVE-2024-49724

HIGH · 7.0 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 →
72/100
Remediation priority · Elevated
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 multiple functions of AccountManagerService.java, there is a possible way to bypass permissions and launch protected activities due to a race condition. 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 race condition in multiple functions of AccountManagerService.java allows attackers to bypass permission checks and launch protected activities. By exploiting timing windows between permission validation and activity launch, a malicious local application can achieve privilege escalation without additional execution privileges, though user interaction is required.

MitigationImplement proper synchronization and atomic operations in AccountManagerService.java to eliminate race conditions in permission checks. Use explicit locking or re-order operations to ensure permission validation cannot be circumvented through timing manipulation.

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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. Identify Android OS version
    Go to Settings > About Phone > Android version (or use 'getprop ro.build.version.release' via ADB shell)
    Affected if The installed version is 12.0, 12.1, 13.0, 14.0, or 15.0 exactly
  2. Verify AccountManagerService presence
    Check if the AccountManager system service is accessible on the device - examine /system/bin/ or the framework jar for AccountManagerService classes
    Affected if The device runs an affected Android version and has the AccountManager framework available
  3. Confirm device is not patched
    Check for the latest Google Android security patch level in Settings > About Phone > Security Patch Level
    Affected if The security patch level is older than the fix for CVE-2024-49724 (no specific patch date was provided in the CVE data)

A device is affected if it runs Android 12.0, 12.1, 13.0, 14.0, or 15.0 and has not received the security update addressing the race condition in AccountManagerService.

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

Implement proper synchronization and atomic operations in AccountManagerService.java to eliminate race conditions in permission checks. Use explicit locking or re-order operations to ensure permission validation cannot be circumvented through timing manipulation.

Recommended fix Moderate confidence

Android 15.0 (API 35) or later monthly security patch (November 2024 security bulletin and later)

  1. 1. Check current Android version by going to Settings > About Phone > Android version
  2. 2. Verify the current Android security patch level in Settings > About Phone > Security patch level
  3. 3. Update to Android 15.0 or later if your device is supported, as this vulnerability is fixed in later Android releases
  4. 4. If Android 15 is not available for your device, check for and install the latest monthly security update from your device manufacturer
  5. 5. After updating, verify the security patch level includes the fix for this CVE (typically November 2024 or later security bulletins)
  6. 6. Confirm the fix by checking Settings > About Phone > Security patch level shows a date after the CVE fix release
Caveat Android 15 upgrade may introduce behavior changes in apps; verify critical apps are compatible with Android 15 before full deployment

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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