Privilege escalation via unbounded ioctl copy length
Published Jun 16, 2020 · Updated Aug 4, 2024
An out-of-bounds write in the Android kernel allows attackers to elevate privileges through crafted input to crus_sp_shared_ioctl. The handler copies four bytes into size, then trusts that unbounded value as copy_from_user's length, overwriting memory after static crus_sp_hdr. Exploitation requires access to the driver ioctl; the published record does not identify the reachable device node or resulting privilege level.
Summary
What happened
An out-of-bounds write in the Android kernel allows attackers to elevate privileges through crafted input to crus_sp_shared_ioctl. The handler copies four bytes into size, then trusts that unbounded value as copy_from_user's length, overwriting memory after static crus_sp_hdr. Exploitation requires access to the driver ioctl; the published record does not identify the reachable device node or resulting privilege level.
The record
- CVE
- CVE-2020-0235
- Published
- Jun 16, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-787, T1404
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 16, 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.
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