Remote code execution via unchecked AVRCP attribute count
Published Dec 2, 2024 · Updated Dec 3, 2024
Out-of-bounds write in Android 7 through 8.1 allows remote attackers to execute code through a crafted Bluetooth AVRCP response. The AVRCP parser trusts num_attr in an application-setting-change notification and writes that many attribute pairs into fixed-size arrays. Exploitation requires a Bluetooth peer and user interaction; successful corruption executes code with the Bluetooth process privileges.
Summary
What happened
Out-of-bounds write in Android 7 through 8.1 allows remote attackers to execute code through a crafted Bluetooth AVRCP response. The AVRCP parser trusts num_attr in an application-setting-change notification and writes that many attribute pairs into fixed-size arrays. Exploitation requires a Bluetooth peer and user interaction; successful corruption executes code with the Bluetooth process privileges.
The record
- CVE
- CVE-2018-9413
- Published
- Dec 2, 2024
- Updated
- Dec 3, 2024
- Vendor
- Product
- Google Pixel
- Classifications
- CWE-787, T1203
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 2, 2024CVE publishedPublication date reported by the CVE source.
- Dec 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=0 <2018-07-05
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.
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