Red Hat Bugzilla – Bug 166791
[CAN-2005-2547] Remote attackers can execute arbitrary commands with crafted Bluetooth device name
Last modified: 2007-04-18 13:30:52 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050719 Fedora/1.7.10-1.5.1 Description of problem: From <http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-2547>: "security.c in hcid for BlueZ 2.18 and earlier allows remote attackers to execute arbitrary commands via shell metacharacters in the Bluetooth device name when invoking the PIN helper." This is fixed in bluez-utils 2.19. From <http://www.bluez.org/>: "06.08.2005 Release of bluez-libs-2.19 and bluez-utils-2.19 These releases fixes a security problem when the remote device names contain shell escape characters and an off by one memory allocation bug. They also add preliminary support for device specific service records." I've prepared some updated packages, which you can find here: http://homepages.nildram.co.uk/~phekda/richdawe/fedora/FC3/bluez-libs-2.19-1richdawe.src.rpm It's unclear to me whether you need to update bluez-utils too, so I did: http://homepages.nildram.co.uk/~phekda/richdawe/fedora/FC3/bluez-utils-2.19-1richdawe.src.rpm I've tested this pair of packages by sending some images from a Sony Ericsson K750i mobile phone (cell phone) to my MSI USB Bluetooth dongle on my PC. Not exactly extensive testing. Version-Release number of selected component (if applicable): bluez-libs-2.10-2 How reproducible: Didn't try Steps to Reproduce: Additional info:
Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you!
It doesn't look like there's an update for bluez-libs 1.19 in Fedora Legacy. Since this is a security issue, I've reassigned this to Fedora Legacy.
Thanks!
According to the CVE-2005-2547, this only effects bluez verions 2.16, 2.17, and 2.18. FC3 and 4 shipped 2.15 and thus are not vulnerable.