Local privilege escalation via use-after-free corruption
Published Jun 11, 2020 · Updated Aug 4, 2024
Use-after-free memory corruption in Android 10's System component allows local users to gain elevated privileges without user interaction. The main function in main.cpp accesses an object after its storage has been freed, corrupting memory. Local access is required, and successful exploitation grants elevated privileges on the affected device without further user involvement.
Summary
What happened
Use-after-free memory corruption in Android 10's System component allows local users to gain elevated privileges without user interaction. The main function in main.cpp accesses an object after its storage has been freed, corrupting memory. Local access is required, and successful exploitation grants elevated privileges on the affected device without further user involvement.
The record
- CVE
- CVE-2020-0233
- Published
- Jun 11, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-416, CWE-787, T1404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 11, 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 kernel
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