Local privilege escalation via retained call-screening service
Published Sep 11, 2024 · Updated Mar 18, 2025
Permissions bypass in Google Android 12, 12L, 13, and 14 allows local users to retain while-in-use permission in the background. CallScreeningServiceHelper.bindAndGetCallIdentification assumes screening completion will unbind ROLE_CALL_SCREENING services, but a plain service can remain bound until timeout. Exploitation requires user interaction and lets a default call-screening app keep its service alive with foreground-scoped access.
Summary
What happened
Permissions bypass in Google Android 12, 12L, 13, and 14 allows local users to retain while-in-use permission in the background. CallScreeningServiceHelper.bindAndGetCallIdentification assumes screening completion will unbind ROLE_CALL_SCREENING services, but a plain service can remain bound until timeout. Exploitation requires user interaction and lets a default call-screening app keep its service alive with foreground-scoped access.
The record
- CVE
- CVE-2024-40655
- Published
- Sep 11, 2024
- Updated
- Mar 18, 2025
- Vendor
- Product
- Android
- Classifications
- CWE-276, T1548
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 11, 2024CVE publishedPublication date reported by the CVE source.
- Mar 18, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=12
- Affected versionversion=12l
- Affected versionversion=12L
- Affected versionversion=13
- Affected versionversion=14
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo