# CVE-2018-10910: Auth bypass in bluez > Attackers can pair Bluetooth devices without authentication due to a bug in Bluez that enables discoverable mode without a registered agent. - **Severity:** Medium 4.5 (`CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 28 Jan 2019 - **Updated:** 5 Aug 2024 - **Also known as:** DEBIAN-CVE-2018-10910, GHSA-62rf-fp64-gxpc, RHSA-2020:1101, RHSA-2020:1912, UBUNTU-CVE-2018-10910, USN-3856-1 ## What is CVE-2018-10910? CVE-2018-10910 is a medium-severity authentication bypass vulnerability in Canonical Ubuntu Linux, published on 28 Jan 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description A bug in Bluez may allow for the Bluetooth Discoverable state being set to on when no Bluetooth agent is registered with the system. This situation could lead to the unauthorized pairing of certain Bluetooth devices without any form of authentication. Versions before bluez 5.51 are vulnerable. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2018-10910? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `bluez` | Red Hat:enterprise_linux:7::client | All versions | 0:5.44-6.el7 | | `bluez-cups` | Red Hat:enterprise_linux:7::client | All versions | 0:5.44-6.el7 | | `bluez-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:5.44-6.el7 | | `bluez-hid2hci` | Red Hat:enterprise_linux:7::client | All versions | 0:5.44-6.el7 | | `bluez-libs` | Red Hat:enterprise_linux:7::client | All versions | 0:5.44-6.el7 | | `bluez-libs-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:5.44-6.el7 | | `bluez` | Red Hat:enterprise_linux:7::computenode | All versions | 0:5.44-6.el7 | | `bluez-cups` | Red Hat:enterprise_linux:7::computenode | All versions | 0:5.44-6.el7 | | `bluez-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:5.44-6.el7 | | `bluez-hid2hci` | Red Hat:enterprise_linux:7::computenode | All versions | 0:5.44-6.el7 | | `bluez-libs` | Red Hat:enterprise_linux:7::computenode | All versions | 0:5.44-6.el7 | | `bluez-libs-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:5.44-6.el7 | | `bluez` | Red Hat:enterprise_linux:7::server | All versions | 0:5.44-6.el7 | | `bluez-cups` | Red Hat:enterprise_linux:7::server | All versions | 0:5.44-6.el7 | | `bluez-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:5.44-6.el7 | | `bluez-hid2hci` | Red Hat:enterprise_linux:7::server | All versions | 0:5.44-6.el7 | | `bluez-libs` | Red Hat:enterprise_linux:7::server | All versions | 0:5.44-6.el7 | | `bluez-libs-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:5.44-6.el7 | | `bluez` | Red Hat:enterprise_linux:7::workstation | All versions | 0:5.44-6.el7 | | `bluez-cups` | Red Hat:enterprise_linux:7::workstation | All versions | 0:5.44-6.el7 | | `bluez-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:5.44-6.el7 | | `bluez-hid2hci` | Red Hat:enterprise_linux:7::workstation | All versions | 0:5.44-6.el7 | | `bluez-libs` | Red Hat:enterprise_linux:7::workstation | All versions | 0:5.44-6.el7 | | `bluez-libs-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:5.44-6.el7 | | `bluez-cups` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.50-3.el8 | | `bluez-cups-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.50-3.el8 | | `bluez-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.50-3.el8 | | `bluez-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.50-3.el8 | | `bluez-hid2hci-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.50-3.el8 | | `bluez-libs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.50-3.el8 | | `bluez-obexd-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.50-3.el8 | | `bluez` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.50-3.el8 | | `bluez-cups-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.50-3.el8 | | `bluez-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.50-3.el8 | | `bluez-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.50-3.el8 | | `bluez-hid2hci` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.50-3.el8 | | `bluez-hid2hci-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.50-3.el8 | | `bluez-libs` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.50-3.el8 | | `bluez-libs-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.50-3.el8 | | `bluez-obexd` | Red Hat:enterprise_linux:8::baseos | All versions | 0:5.50-3.el8 | Products: Bluez Bluez, Canonical Ubuntu Linux. ## How do I fix CVE-2018-10910? Upgrade to a fixed version. ## Is CVE-2018-10910 being exploited? There is no known exploitation of CVE-2018-10910 in the wild and no public exploit code. ## Other vulnerabilities in Canonical Ubuntu Linux - [CVE-2021-43400](https://insights.sbomify.com/CVE-2021-43400/): Use after free in n/a (critical 9.1) - [CVE-2024-8805](https://insights.sbomify.com/CVE-2024-8805/): BlueZ HID over GATT Profile Improper Access Control Remote Code Execution Vulnerability (high 8.8) - [CVE-2022-39176](https://insights.sbomify.com/CVE-2022-39176/): Information disclosure in n/a (high 8.8) - [CVE-2022-39177](https://insights.sbomify.com/CVE-2022-39177/): Denial of service in n/a (high 8.8) - [CVE-2022-0204](https://insights.sbomify.com/CVE-2022-0204/): Memory corruption in bluez (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-10910 and fix it if it is affected. What it is: CVE-2018-10910 is a medium-severity authentication bypass vulnerability in Canonical Ubuntu Linux, published on 28 Jan 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2018-10910 in the wild and no public exploit code. Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2018-10910/ (Markdown: https://insights.sbomify.com/CVE-2018-10910/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-10910 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-10910 - OSV: https://osv.dev/vulnerability/CVE-2018-10910 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-10910/ Summaries are generated and may contain mistakes; the official description above is the record.