Local privilege escalation via writable ashmem remapping
Published Jan 8, 2020 · Updated Aug 4, 2024
Privilege escalation in the Android kernel ashmem component allows local users to corrupt memory shared between processes. ashmem_mmap stores the backing shmem file in vm_file without preserving its protection checks, so remap_file_pages can restore VM_MAYWRITE. A local process holding an ashmem file descriptor can make a read-only mapping writable without added privileges or user interaction.
Summary
What happened
Privilege escalation in the Android kernel ashmem component allows local users to corrupt memory shared between processes. ashmem_mmap stores the backing shmem file in vm_file without preserving its protection checks, so remap_file_pages can restore VM_MAYWRITE. A local process holding an ashmem file descriptor can make a read-only mapping writable without added privileges or user interaction.
The record
- CVE
- CVE-2020-0009
- Published
- Jan 8, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-276, T1404
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 8, 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
- Android ashmem read-only bypass reproducerproof of concept · demonstrated
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