Paired-device privilege escalation via undersized vendor-message bounds check
Published Sep 4, 2025 · Updated Feb 26, 2026
Heap buffer overflow in Android 13 and 14 Bluetooth allows attackers with a paired device to escalate privileges without user interaction. The avrc_vendor_msg function validates vendor_len with a minimum command length that omits the three-byte company ID before writing into a fixed-size buffer. A Bluetooth device must already be paired; exploitation needs no additional execution privileges and can corrupt heap memory to gain higher privileges.
Summary
What happened
Heap buffer overflow in Android 13 and 14 Bluetooth allows attackers with a paired device to escalate privileges without user interaction. The avrc_vendor_msg function validates vendor_len with a minimum command length that omits the three-byte company ID before writing into a fixed-size buffer. A Bluetooth device must already be paired; exploitation needs no additional execution privileges and can corrupt heap memory to gain higher privileges.
The record
- CVE
- CVE-2024-49714
- Published
- Sep 4, 2025
- Updated
- Feb 26, 2026
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-122, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 4, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record 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=13
- Affected versionversion=14
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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