dbcve.org
BluezApplication

CVE-2024-8805

HIGH · 8.8 CVSS v3.1 Published 2024-11-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
BlueZ HID over GATT Profile Improper Access Control Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of BlueZ. Authentication is not required to exploit this vulnerability. The specific flaw exists within the implementation of the HID over GATT Profile. The issue results from the lack of authorization prior to allowing access to functionality. An attacker can leverage this vulnerability to execute code in the context of the current user. Was ZDI-CAN-25177.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

BlueZ's HID over GATT Profile implementation lacks proper authorization checks before allowing access to sensitive functionality, allowing unauthenticated network-adjacent attackers within Bluetooth range to execute arbitrary code in the context of the current user. This is a critical access control failure in the Bluetooth stack used by Linux systems.

MitigationUpdate BlueZ to the latest patched version addressing this vulnerability; if immediate patching is not feasible, restrict Bluetooth exposure by disabling unused Bluetooth adapters and limiting device pairing to trusted devices only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BluezApplication
Affected:= 5.77

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed BlueZ version
    Run 'bluetoothd --version' or 'apt-cache policy bluez' to determine the installed version of the BlueZ Bluetooth stack
    Affected if The installed version equals 5.77 exactly, as this is the only affected version listed
  2. Verify Bluetooth service is active
    Run 'systemctl status bluetooth' to confirm the Bluetooth daemon is running
    Affected if Bluetooth service is active and running, enabling the vulnerable HID over GATT Profile to be accessible
  3. Confirm HID over GATT Profile is configured
    Run 'bluetoothctl list' or inspect /etc/bluetooth/ directory for configuration files that enable HID GATT services. Check for any registered HID or GATT profiles with 'bluetoothctl info' on paired devices
    Affected if HID over GATT Profile is enabled or any HID GATT service is registered and advertised by the BlueZ instance
  4. Check Bluetooth accessibility
    Use 'hciconfig' to verify Bluetooth adapters are up and in discoverable/connectable state. Confirm the device is within Bluetooth range of potential attackers
    Affected if Bluetooth adapters are powered on and set to connectable mode, allowing unauthenticated adjacent attackers to reach the vulnerable service

A user is affected if BlueZ version 5.77 is installed AND the Bluetooth service is running with HID over GATT Profile enabled and accessible to adjacent attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update BlueZ to the latest patched version addressing this vulnerability; if immediate patching is not feasible, restrict Bluetooth exposure by disabling unused Bluetooth adapters and limiting device pairing to trusted devices only.

Recommended fix Moderate confidence

Latest stable BlueZ release (newer than 5.77)

  1. Check the current installed BlueZ version using: dpkg -l | grep bluez or rpm -qa | grep bluez
  2. Update the package repository and upgrade BlueZ to the latest available version using the system's package manager (e.g., apt update && apt install --only-upgrade bluez or dnf update bluez)
  3. Alternatively, download and install the latest BlueZ source from the official BlueZ repository at https://git.kernel.org/pub/scm/bluetooth/bluez.git
  4. After upgrading, verify the new version is installed: bluetoothd --version
  5. Ensure the Bluetooth service is restarted: systemctl restart bluetooth
  6. Confirm the system is running a version newer than 5.77
Caveat Major BlueZ upgrades may require changes to configuration files or dependent services; review release notes for any breaking changes before applying in production environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bluez Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8805 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-8805 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data