Local information disclosure via unverified embedded buffer
Published Aug 17, 2021 · Updated Feb 25, 2026
Out-of-bounds read in Android 8.1, 9, 10, and 11 allows local users to disclose data through a crafted Parcel buffer object. Parcel.cpp's verifyBufferObject accepted an embedded child buffer without confirming that its address matched the pointer stored at the parent offset, so a null child object prevented kernel fixup and left the embedded pointer unchanged. A local malicious application needs no additional execution privileges or user interaction and can read data isolated from other applications.
Summary
What happened
Out-of-bounds read in Android 8.1, 9, 10, and 11 allows local users to disclose data through a crafted Parcel buffer object. Parcel.cpp's verifyBufferObject accepted an embedded child buffer without confirming that its address matched the pointer stored at the parent offset, so a null child object prevented kernel fixup and left the embedded pointer unchanged. A local malicious application needs no additional execution privileges or user interaction and can read data isolated from other applications.
The record
- CVE
- CVE-2021-0584
- Published
- Aug 17, 2021
- Updated
- Feb 25, 2026
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-125, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 17, 2021CVE publishedPublication date reported by the CVE source.
- Feb 25, 2026Record 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 Android-8.1 Android-9 Android-10
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