Local RAM disclosure via shared cryptographic key
Published Apr 17, 2020 · Updated Aug 4, 2024
Information disclosure in the Android 10 Framework allows local users to read RAM through an improperly shared cryptographic key. The nonpublic Framework implementation reuses a cryptographic key in a way that exposes memory contents; Google has not published the affected function or data path. A local application with ordinary execution privileges can obtain sensitive data without user interaction, while integrity and availability remain unaffected.
Summary
What happened
Information disclosure in the Android 10 Framework allows local users to read RAM through an improperly shared cryptographic key. The nonpublic Framework implementation reuses a cryptographic key in a way that exposes memory contents; Google has not published the affected function or data path. A local application with ordinary execution privileges can obtain sensitive data without user interaction, while integrity and availability remain unaffected.
The record
- CVE
- CVE-2019-2056
- Published
- Apr 17, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- T1533
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 17, 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
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