S-314: Vulnerability in Bluetooth Stack


 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) S-314: Vulnerability in Bluetooth Stack
# 1  
Old 06-12-2008
S-314: Vulnerability in Bluetooth Stack

A remote code execution vulnerability exists in the Bluetooth stack in Microsoft Windows because the Bluetooth stack does not correctly handle a large nubmer of service description requests. The risk is MEDIUM. The vulnerability could allow an attacker to run code with elevated privileges. An attacker who successfully exploited this vulenrability could take complete contorl of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.


More...
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. Linux

Bluetooth

I have a bluetooth device, and when i search for a device it doesnt show anything,i have downloaded bluman blueberry bluedevil bluez but nothng worked,im using linux mint 18.2. (2 Replies)
Discussion started by: Lee win
2 Replies

2. UNIX for Dummies Questions & Answers

Kernel Stack vs User Mode Stack

Hi, I am new to the linux kernel development area. I want to know what is the difference between kernel mode stack and user mode stack? Does each process has a user mode stack and a kernel mode stack?? Or Each process has a user mode stack and there is only one kernel mode stack that is shared by... (4 Replies)
Discussion started by: saurabhkoar
4 Replies

3. Windows & DOS: Issues & Discussions

Bluetooth problem ...?

my bluetooth dongle (not branded ) is working fine with KDEBluetooth in opensuse 10.3 (linux) but it is not even detected in windows after installation of software given with dongle( IVT Bluesoleil) what is proble can any body give list of blue... (0 Replies)
Discussion started by: seshumohan
0 Replies

4. Red Hat

Bluetooth in fedora

My system has bluetooth enabled in it. I have fedora o.s.. I can send data from my system to any other external devices which are bluetooth enabled. But from external devices, I can not send data into my laptop system. What can be done. Please guide. (0 Replies)
Discussion started by: manoj.b
0 Replies

5. HP-UX

HP-UX to bluetooth printer

Wondering if anyone can point me in the right direction to get HP-UX (Ver 5.4 I believe) to send a print job to a bluetooth enabled printer. I can do it via TCP/IP but would like to have it also bluetooth capable when I don't have access to a network connection. Any idea? Thanks in advance. ... (0 Replies)
Discussion started by: RUNG41
0 Replies

6. Programming

what is stack winding and stack unwinding

helo can u tell me what do you mean by stack winding and stack unwinding Regards, Amit (2 Replies)
Discussion started by: amitpansuria
2 Replies
Login or Register to Ask a Question
CIPTOOL(1)																CIPTOOL(1)

NAME
ciptool - Bluetooth Common ISDN Access Profile (CIP) SYNOPSIS
ciptool [ options ] < command > DESCRIPTION
ciptool is used to set up, maintain, and inspect the CIP configuration of the Bluetooth subsystem in the Linux kernel. OPTIONS
-h Gives a list of possible commands. -i <hciX> | <bdaddr> The command is applied to device hciX , which must be the name or the address of an installed Bluetooth device. If not specified, the command will be use the first available Bluetooth device. COMMANDS
show Display information about the connected devices. search Search for Bluetooth devices and connect to first one that offers CIP support. connect <bdaddr> [psm] Connect the local device to the remote Bluetooth device on the specified PSM number. If no PSM is specified, it will use the SDP to retrieve it from the remote device. release [bdaddr] Release a connection to the specific device. If no address is given and only one device is connected this will be released. loopback <bdaddr> [psm] Create a connection to the remote device for Bluetooth testing. This command will not provide a CAPI controller, because it is only for testing the CAPI Message Transport Protocol. AUTHOR
Written by Marcel Holtmann <marcel@holtmann.org>. JUNE 6, 2003 CIPTOOL(1)