Remote heap disclosure via uninitialized AVRCP responses
Published Apr 13, 2021 · Updated Aug 3, 2024
Improper initialization in Android 8.1 through 11 allows remote attackers to read heap data through a crafted Bluetooth AVRCP command. In avrc_proc_vendor_command in stack/avrc/avrc_api.cc, AVRCP response buffers allocated without zeroing retain reserved bytes that are returned remotely. No authentication or user interaction is required, and exposure is limited to process heap contents; no integrity or availability impact is reported.
Summary
What happened
Improper initialization in Android 8.1 through 11 allows remote attackers to read heap data through a crafted Bluetooth AVRCP command. In avrc_proc_vendor_command in stack/avrc/avrc_api.cc, AVRCP response buffers allocated without zeroing retain reserved bytes that are returned remotely. No authentication or user interaction is required, and exposure is limited to process heap contents; no integrity or availability impact is reported.
The record
- CVE
- CVE-2021-0435
- Published
- Apr 13, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-665
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 13, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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-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.
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