Local memory disclosure via dangling Bluetooth pointer
Published Jan 8, 2020 · Updated Aug 4, 2024
Out-of-bounds read in Android 8.0 through 10 allows local users to disclose process memory through a Bluetooth callback race. LowEnergyClient::MtuChangedCallback stores a c_str() pointer from the temporary string returned by BtAddrString(), leaving a dangling pointer that can be read after the temporary is destroyed. Exploitation requires local low-privileged access and no user interaction; the bounded impact is disclosure of memory visible to the Bluetooth process.
Summary
What happened
Out-of-bounds read in Android 8.0 through 10 allows local users to disclose process memory through a Bluetooth callback race. LowEnergyClient::MtuChangedCallback stores a c_str() pointer from the temporary string returned by BtAddrString(), leaving a dangling pointer that can be read after the temporary is destroyed. Exploitation requires local low-privileged access and no user interaction; the bounded impact is disclosure of memory visible to the Bluetooth process.
The record
- CVE
- CVE-2020-0008
- Published
- Jan 8, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-125, CWE-362
- Attack vector
- local
- Privileges
- authenticated
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