ASLR bypass via protected Parcel object reads
Published Jan 17, 2025 · Updated Mar 24, 2025
Information disclosure in Android 6.0 through 8.1 allows local users to bypass ASLR through protected Binder Parcel object reads. Parcel.cpp permits non-object read methods to consume protected Binder or file-descriptor object data, and failed protected reads do not advance the parcel position. A local low-privileged process can reuse those reads to expose address-layout information; the flaw does not itself execute code or require user interaction.
Summary
What happened
Information disclosure in Android 6.0 through 8.1 allows local users to bypass ASLR through protected Binder Parcel object reads. Parcel.cpp permits non-object read methods to consume protected Binder or file-descriptor object data, and failed protected reads do not advance the parcel position. A local low-privileged process can reuse those reads to expose address-layout information; the flaw does not itself execute code or require user interaction.
The record
- CVE
- CVE-2018-9434
- Published
- Jan 17, 2025
- Updated
- Mar 24, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-276, T1404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 17, 2025CVE publishedPublication date reported by the CVE source.
- Mar 24, 2025Record 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?
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