dbcve.org
AndroidOperating system · Google

CVE-2024-40653

HIGH · 7.3 CVSS v3.1 Published 2025-09-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated

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 ConnectionServiceWrapper.java, there is a possible way to retain a permission forever in the background due to a logic error in the code. 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 logic error in multiple functions of ConnectionServiceWrapper.java allows permissions to be retained permanently in the background, enabling local privilege escalation without additional execution privileges but requiring user interaction for exploitation.

MitigationThe logic error in ConnectionServiceWrapper.java must be corrected to ensure permissions are properly revoked when no longer needed, preventing permanent background retention.

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:= 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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 OS version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if The version is exactly 13.0, 14.0, or 15.0
  2. Identify apps using ConnectionService
    Search for apps that implement ConnectionService or TelephonyConnectionService in the codebase, or inspect installed apps for android.telecom.ConnectionService in their manifests
    Affected if An app with the android.telecom.ConnectionService permission is installed and uses the vulnerable ConnectionServiceWrapper component
  3. Review background permission state
    Check running services and background processes via 'adb shell dumpsys activity services' or device battery/permission monitoring for unexpected persistent service activity
    Affected if A ConnectionService-based app continues running in the background after it should have been terminated, retaining telephony permissions
  4. Check for unexpected telephony permissions
    Inspect app permissions via 'adb shell dumpsys package <package_name>' focusing on android.permission.MANAGE_ACTIONS, android.permission.ANSWER_PHONE_CALLS, or similar telephony-related permissions
    Affected if Permissions granted to a ConnectionService app persist longer than expected or remain active when the app is in background state

A user is affected if their Android device runs version 13.0, 14.0, or 15.0 AND has an app installed that implements ConnectionService with telephony permissions that exhibit persistent background retention behavior.

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

The logic error in ConnectionServiceWrapper.java must be corrected to ensure permissions are properly revoked when no longer needed, preventing permanent background retention.

Recommended fix Moderate confidence

Android 13.0: October 2024 security patch or later; Android 14.0: October 2024 security patch or later; Android 15.0: October 2024 security patch or later

  1. Check the Android Security Bulletin for the month this CVE was addressed (CVE-2024-40653 was fixed in the October 2024 Android Security Bulletin)
  2. Apply the latest Android security patch level for your Android version (13.0, 14.0, or 15.0)
  3. On Pixel devices: Go to Settings > Security > Security update and ensure the October 2024 patch or later is installed
  4. On other Android devices: Contact your device manufacturer for the specific security update containing this fix
  5. Verify the patch level by going to Settings > About Phone > Android version and checking the Security patch level shows October 2024 or later
Caveat Security updates are cumulative and backward-compatible; no breaking changes expected for this patch

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

Fix this in Android Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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