Local heap-memory disclosure via uninitialized alignment padding
Published Jan 8, 2020 · Updated Aug 4, 2024
Information disclosure in Android System 8.0 through 10 allows local users to read heap memory through a malicious application. Sensor.cpp's flattenString8 advances over four-byte alignment padding without initializing it, allowing stale heap bytes to enter flattened sensor data. Exploitation requires local application execution but needs no additional execution privileges or user interaction; confidentiality is the only reported impact.
Summary
What happened
Information disclosure in Android System 8.0 through 10 allows local users to read heap memory through a malicious application. Sensor.cpp's flattenString8 advances over four-byte alignment padding without initializing it, allowing stale heap bytes to enter flattened sensor data. Exploitation requires local application execution but needs no additional execution privileges or user interaction; confidentiality is the only reported impact.
The record
- CVE
- CVE-2020-0007
- Published
- Jan 8, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-908
- 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-10
- Affected versionversion=Android-8.0
- Affected versionversion=Android-8.1
- Affected versionversion=Android-9
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