Bug 2278967 (CVE-2023-51580) - CVE-2023-51580 bluez: avrcp_parse_attribute_list out-of-bounds read information disclosure vulnerability
Summary: CVE-2023-51580 bluez: avrcp_parse_attribute_list out-of-bounds read informati...
Keywords:
Status: NEW
Alias: CVE-2023-51580
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2278968
Blocks: 2278934
TreeView+ depends on / blocked
 
Reported: 2024-05-03 19:11 UTC by Robb Gatica
Modified: 2024-06-12 19:33 UTC (History)
0 users

Fixed In Version:
Doc Type: ---
Doc Text:
A flaw was found within the handling of the AVRCP protocol in BlueZ. This vulnerability allows network-adjacent attackers to disclose sensitive information via Bluetooth on affected installations of BlueZ. User interaction is required to exploit this vulnerability in that the target must connect to a malicious device.
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Robb Gatica 2024-05-03 19:11:53 UTC
BlueZ Audio Profile AVRCP avrcp_parse_attribute_list Out-Of-Bounds Read Information Disclosure Vulnerability. This vulnerability allows network-adjacent attackers to disclose sensitive information via Bluetooth on affected installations of BlueZ. User interaction is required to exploit this vulnerability in that the target must connect to a malicious device.

The specific flaw exists within the handling of the AVRCP protocol. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated buffer. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of root. Was ZDI-CAN-20852.

https://www.zerodayinitiative.com/advisories/ZDI-23-1903/

Comment 1 Robb Gatica 2024-05-03 19:13:05 UTC
Created bluez tracking bugs for this issue:

Affects: fedora-all [bug 2278968]


Note You need to log in before you can comment on or make changes to this bug.