CVE-2023-51589

What it actually does

Out-of-bounds read in AVRCP media element parsing allows disclosure of adjacent memory contents over Bluetooth without authentication.

Why it matters to the business

Nearby attackers can obtain sensitive data from affected systems; older unpatched deployments increase exposure window given nearly three years since disclosure.

How an attack unfolds

An attacker configures a malicious Bluetooth device advertising AVRCP services; when a victim device initiates pairing or connection, malformed media element data triggers the out-of-bounds read, leaking memory that may aid further exploitation toward root-level code execution when chained.

How to fix it

Upgrade googlecloudplatform/esp-v2 to commit 0bcdfc024ce96b34db4e1b4f2211b509d9be93cd; verify Bluetooth stack components are rebuilt against the patched source.

How to confirm the fix worked

Confirm running binary or container image contains the 0bcdfc024ce96b34db4e1b4f2211b509d9be93cd commit; test AVRCP parsing with malformed media elements to ensure no out-of-bounds access occurs.

Typical attack path

1. Position malicious Bluetooth peripheral within range
2. Advertise AVRCP profile to lure connection
3. Victim initiates pairing or media session
4. Send crafted media element PDU causing OOB read
5. Exfiltrate disclosed memory contents
6. Combine with additional vulnerabilities for code execution

How to detect it

Review Bluetooth daemon logs for unexpected AVRCP connections or parse errors; correlate with system logs showing memory access anomalies around media element handling.

What your security team should do

• Immediately update all esp-v2 deployments to the fixed commit
• Restrict Bluetooth discoverability and pairing to trusted devices only
• Monitor for unexpected Bluetooth connections from unknown sources
• Review downstream dependents for inherited exposure