Adjacent code execution via missing HOG authorization
Published Nov 22, 2024 · Updated Nov 3, 2025
Improper access control in BlueZ 5.77 allows network-adjacent attackers to execute code through unauthenticated Bluetooth access. The CNA identifies the HID over GATT Profile but does not disclose which function permits access without authorization. Ubuntu and Debian identify the cited flaw as a Linux kernel issue rather than a BlueZ defect, leaving the BlueZ assignment disputed.
Summary
What happened
Improper access control in BlueZ 5.77 allows network-adjacent attackers to execute code through unauthenticated Bluetooth access. The CNA identifies the HID over GATT Profile but does not disclose which function permits access without authorization. Ubuntu and Debian identify the cited flaw as a Linux kernel issue rather than a BlueZ defect, leaving the BlueZ assignment disputed.
The record
- CVE
- CVE-2024-8805
- Published
- Nov 22, 2024
- Updated
- Nov 3, 2025
- Vendor
- BlueZ Project
- Product
- BlueZ
- Classifications
- CWE-284
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 22, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record 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=5.77
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