Local privilege escalation via unsynchronized ShellSubscriber initialization
Published Mar 10, 2020 · Updated Aug 4, 2024
Local privilege escalation in Android 10's StatsService allows local users with System privileges to gain elevated execution privileges. StatsService::command lazily initializes a shared ShellSubscriber pointer without thread-safe synchronization, allowing concurrent calls to corrupt memory. A null ResultReceiver can repeatedly crash statsd until the race is won; exploitation requires System-level execution and no user interaction.
Summary
What happened
Local privilege escalation in Android 10's StatsService allows local users with System privileges to gain elevated execution privileges. StatsService::command lazily initializes a shared ShellSubscriber pointer without thread-safe synchronization, allowing concurrent calls to corrupt memory. A null ResultReceiver can repeatedly crash statsd until the race is won; exploitation requires System-level execution and no user interaction.
The record
- CVE
- CVE-2020-0045
- Published
- Mar 10, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-362, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 10, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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-10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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