CVE-2018-10910

Publication date 24 July 2018

Last updated 24 July 2024

Ubuntu priority

Cvss 3 Severity Score

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.

Read the notes from the security team

Status

Show unmaintained releases

Package	Ubuntu Release	Status
bluez	19.10 eoan	Ignored
	19.04 disco	Ignored
	18.10 cosmic	Ignored
	18.04 LTS bionic	Ignored
	16.04 LTS xenial	Ignored
	14.04 LTS trusty	Not in release
gnome-bluetooth	19.10 eoan	Not affected
	19.04 disco	Not affected
	18.10 cosmic	Not affected
	18.04 LTS bionic	Fixed 3.28.0-2ubuntu0.1
	16.04 LTS xenial	Not affected
	14.04 LTS trusty	Not in release

Notes

mdeslaur

actual bug in bluez, but there is a work-around in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/commit/6b5086d42ea64d46277f3c93b43984f331d12f89 gnome-bluetooth <=3.26 used synchronous d-bus calls, so the issue doesn't present itself the bluez patches add new functionnality that newer versions of gnome-bluetooth can use to fix this issue. Since the workaround was applied to gnome-bluetooth, we aren't going to add these commits to bluez. Marking as ignored.

Patch details

For informational purposes only. We recommend not to cherry-pick updates. How can I get the fixes?

Package	Patch details
bluez	Upstream: ?id=279 Upstream: ?id=ee8 Upstream: ?id=632 Upstream: ?id=459 Upstream: ?id=bbf Upstream: ?id=d04 Upstream: ?id=170 Upstream: ?id=9a5 Upstream: ?id=4f1

Severity score breakdown

Parameter	Value
Base score	3.3 · Low
Attack vector	Local
Attack complexity	Low
Privileges required	Low
User interaction	None
Scope	Unchanged
Confidentiality	Low
Integrity impact	None
Availability impact	None
Vector	CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N