{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-51580 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-51580 is a medium-severity vulnerability in BlueZ, published on 3 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-51580 and fix it if it is affected.\n\nWhat it is: CVE-2023-51580 is a medium-severity vulnerability in BlueZ, published on 3 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-51580 in the wild and no public exploit code.\n\nAffected product: BlueZ. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-51580/ (Markdown: https://insights.sbomify.com/CVE-2023-51580/index.md)","id":"CVE-2023-51580","markdown":"https://insights.sbomify.com/CVE-2023-51580/index.md","name":"CVE-2023-51580","record":{"aliases":["AZL-40249","AZL-40253","DEBIAN-CVE-2023-51580","GHSA-wpgw-gr5r-5jqv","UBUNTU-CVE-2023-51580"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"BlueZ Bluetooth stack","requires_auth":"none","summary":"Network-adjacent attackers can disclose sensitive information via Bluetooth by exploiting an out-of-bounds read in BlueZ's AVRCP protocol handling.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"zdi","cpe":[{"product":"bluez","vendor":"bluez"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:L","version":"3.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"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.\n\nThe 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"BlueZ Audio Profile AVRCP avrcp_parse_attribute_list Out-Of-Bounds Read Information Disclosure Vulnerability","id":"CVE-2023-51580","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Voltronic Power ViewPower MacMonitorConsole Exposed Dangerous Method Remote Code Execution Vulnerability","id":"CVE-2023-51581"},"packages":[],"prev":{"headline":"Voltronic Power ViewPower Incorrect Permission Assignment Local Privilege Escalation Vulnerability","id":"CVE-2023-51579"},"products":["BlueZ"],"published":"2024-05-03","related":[{"cvss_score":9.1,"headline":"Use after free in n/a","id":"CVE-2021-43400","kev_date_added":null,"published":"2021-11-04"},{"cvss_score":8.8,"headline":"BlueZ HID over GATT Profile Improper Access Control Remote Code Execution Vulnerability","id":"CVE-2024-8805","kev_date_added":null,"published":"2024-11-22"},{"cvss_score":8.8,"headline":"Information disclosure in n/a","id":"CVE-2022-39176","kev_date_added":null,"published":"2022-09-02"},{"cvss_score":8.8,"headline":"Denial of service in n/a","id":"CVE-2022-39177","kev_date_added":null,"published":"2022-09-02"},{"cvss_score":8.8,"headline":"Memory corruption in bluez","id":"CVE-2022-0204","kev_date_added":null,"published":"2022-03-09"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2019-8922","kev_date_added":null,"published":"2021-11-29"},{"cvss_score":8.6,"headline":"Use after free in n/a","id":"CVE-2020-27153","kev_date_added":null,"published":"2020-10-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["BlueZ"]},"summary":"Network-adjacent attackers can disclose sensitive information via Bluetooth by exploiting an out-of-bounds read in BlueZ's AVRCP protocol handling.","url":"https://insights.sbomify.com/CVE-2023-51580/"}