Local privilege escalation via receiver-registration bypass
Published May 15, 2023 · Updated Jan 31, 2025
Incorrect authorization in Google Cloud Android 13 allows local users to escalate privileges by registering a broadcast receiver. The method previously called enforceNotIsolatedCaller only when RECEIVER_NOT_EXPORTED was set, leaving another flag path open to isolated callers. An isolated local process needs no additional execution privileges or user interaction, and successful exploitation crosses its broadcast-receiver permission boundary.
Summary
What happened
Incorrect authorization in Google Cloud Android 13 allows local users to escalate privileges by registering a broadcast receiver. The method previously called enforceNotIsolatedCaller only when RECEIVER_NOT_EXPORTED was set, leaving another flag path open to isolated callers. An isolated local process needs no additional execution privileges or user interaction, and successful exploitation crosses its broadcast-receiver permission boundary.
The record
- CVE
- CVE-2023-21117
- Published
- May 15, 2023
- Updated
- Jan 31, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-863, T1404
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 15, 2023CVE publishedPublication date reported by the CVE source.
- Jan 31, 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=Android-13
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