Remote code execution via incorrect AAC buffer deallocation
Published May 14, 2020 · Updated Aug 4, 2024
Invalid free in Android 9 and 10 allows remote attackers to execute code in a privileged process via a crafted Bluetooth AAC transmission. The a2dp_aac_decoder_cleanup function passes buffers allocated by osi_malloc to free rather than the required osi_free routine for canary-protected allocations. No authentication or user interaction is required; successful delivery corrupts decoder memory and grants code execution in the Bluetooth service's privileged context.
Summary
What happened
Invalid free in Android 9 and 10 allows remote attackers to execute code in a privileged process via a crafted Bluetooth AAC transmission. The a2dp_aac_decoder_cleanup function passes buffers allocated by osi_malloc to free rather than the required osi_free routine for canary-protected allocations. No authentication or user interaction is required; successful delivery corrupts decoder memory and grants code execution in the Bluetooth service's privileged context.
The record
- CVE
- CVE-2020-0103
- Published
- May 14, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-763, CWE-787, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 14, 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 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