Local privilege escalation via shared-pointer use-after-free
Published Jan 11, 2021 · Updated Aug 3, 2024
Use-after-free memory corruption in Android 11 LazyServiceRegistrar allows local users to elevate privileges without user interaction. LazyServiceRegistrar and ServiceManager share ownership of a callback object incorrectly, permitting its lifetime to end while it remains referenced. A malicious local application needs no additional execution privileges and can gain higher privileges on the device.
Summary
What happened
Use-after-free memory corruption in Android 11 LazyServiceRegistrar allows local users to elevate privileges without user interaction. LazyServiceRegistrar and ServiceManager share ownership of a callback object incorrectly, permitting its lifetime to end while it remains referenced. A malicious local application needs no additional execution privileges and can gain higher privileges on the device.
The record
- CVE
- CVE-2021-0310
- Published
- Jan 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-416, T1404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 11, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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-11
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.
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