1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
|
.TH UBERTOOTH\-RX 1 "March 2017" "Project Ubertooth" "User Commands"
.SH NAME
ubertooth-rx \- Classic Bluetooth discovery, sniffing, and decoding
.SH SYNOPSIS
.PP
.RS
.nf
ubertooth\-rx [ \-l <lap> [ \-u <uap ] ]
ubertooth\-rx \-z
.fi
.RE
.SH DESCRIPTION
.PP
ubertooth\-rx(1) is the primary interface into Classic Bluetooth (BR)
functionality provided by Ubertooth. It has two main modes of operation:
piconet following and survey mode. In either mode, ubertooth\-rx(1) is
able to discover undiscoverable devices. See [DISCOVERING UNDISCOVERABLE
DEVICES][].
.PP
In piconet following mode, the tool will follow the first piconet it
fully identifies. In survey mode the device will attempt to identify all
piconets in a given area and display them after either a timeout or
manual interruption.
.PP
Piconet following is the main mode entered when no arguments are passed
to the command or a LAP and optionally a UAP are provided. If no
arguments are passed, the tool will attempt to calculate the UAP for any
observed LAPs. If a LAP is passed, the UAP will be calculated for that
specific LAP. Once a LAP and UAP have been recovered, the tool will
attempt to recover the clock value, and if that succeeds it will follow
that piconet.
.PP
Survey mode, entered using \fB\fC\-z\fR, will record all LAPs and attempt to
calculate the UAPs for any observed LAPs. This mode can be combined with
a timeout using \fB\fC\-t\fR, and it can be interrupted at any time using
\fB\fCctrl\-C\fR\&.
.SH EXAMPLES
.PP
Follow the first piconet whose LAP, UAP, and clock are recovered from
the air:
.PP
.RS
.nf
ubertooth\-rx
.fi
.RE
.PP
For a given LAP, calculate the UAP and recover the clock, then follow:
.PP
.RS
.nf
ubertooth\-rx \-l 112233
.fi
.RE
.PP
For a given LAP and UAP, recover the clock then follow:
.PP
.RS
.nf
ubertooth\-rx \-l 112233 \-u ab
.fi
.RE
.PP
Enter survey mode for 20 seconds, and print out the BD ADDRs of all
observed piconets:
.PP
.RS
.nf
ubertooth\-rx \-z \-t 20
.fi
.RE
.SH OPTIONS
.PP
Major modes:
.IP \(bu 2
.PP
\fB\fC\-l <lap>\fR :
Limit UAP recovery, clock recovery, and piconet following to a given
LAP. Format is 3 bytes / 6 hex characters.
.IP \(bu 2
.PP
\fB\fC\-u <uap>\fR :
Limit clock recovery and piconet following to a given UAP. Must be
used in conjunction with \fB\fC\-l\fR\&. Format is 1 byte / 2 hex characters.
.IP \(bu 2
.PP
\fB\fC\-z\fR :
Survey mode: recover all LAP and UAP pairs and display them. Will run
indefinitely until interrupted with \fB\fCctrl\-C\fR unless paired with \fB\fC\-t\fR\&.
.PP
Options:
.IP \(bu 2
.PP
\fB\fC\-i <input>\fR :
Input file. If not specified will perform live capture using
Ubertooth.
.IP \(bu 2
.PP
\fB\fC\-c <0\-79>\fR :
Fixed channel for all major modes. If not specified will sweep
through all channels.
.IP \(bu 2
.PP
\fB\fC\-e <0\-4>\fR :
Maximum access code bit errors. [Default: 2]
.IP \(bu 2
.PP
\fB\fC\-t <seconds>\fR :
Timeout in seconds. If not specified will run indefinitely. Suggested
values for \fB\fC\-z\fR: 20\-60 seconds.
.PP
Output options:
.IP \(bu 2
\fB\fC\-r <file.pcapng>\fR :
Capture packets to PcapNG
.IP \(bu 2
\fB\fC\-q <file.pcap>\fR :
Capture packets to PCAP
.IP \(bu 2
\fB\fC\-d <file.bin>\fR :
Capture packets to binary file suitable for use with \fB\fC\-i\fR\&.
.PP
Miscellaneous:
.IP \(bu 2
.PP
\fB\fC\-V\fR :
Version information
.IP \(bu 2
.PP
\fB\fC\-U<0\-7>\fR :
Which Ubertooth device to use
.SH DISCOVERING UNDISCOVERABLE DEVICES
.PP
Classic Bluetooth piocnets are defined by the Lower Address Part (LAP)
and Upper Address Part (UAP) of the master device. These are elements
of the master device's Bluetooth Address (BD ADDR).
.PP
Consider the following BD ADDR:
.PP
.RS
.nf
22:44:66:88:AA:BB
.fi
.RE
.PP
The lower address part (LAP) is the lower 24 bits, so \fB\fC88:AA:BB\fR\&. In the
context of this tool, the value is written \fB\fC88AABB\fR\&. The upper address
part is the next 8 bits, so \fB\fC66\fR\&. The \fB\fC22:44\fR is called the
Non\-significant Address Part (NAP) and as you might imagine it is not
significant.
.PP
In piconet following mode, the tool will recover LAP values from the air
and attempt to calculate the UAP from those. It will go on to follow the
piconet if it can recover the clock value. In survey mode, the tool will
simply recover LAP and UAP values.
.PP
To convert LAP + UAP pairs back into Bluetooth addresses, do the reverse
of the above. For example, if the tool recovers a LAP of 36A2B4 and a
UAP of 98, the associated Bluetooth address is \fB\fC??:??:98:36:A2:B4\fR\&. Any
value can be substituted into the ?? slots and most Bluetooth tools will
still work. For example, \fB\fChcitool name 00:00:98:36:A2:B4\fR will establish
a connection to the device and return its name.
.PP
This attack works against discoverable and undiscoverable devices alike.
.SH SEE ALSO
.PP
ubertooth\-scan(1): active device scanning and inquiry using Ubertooth
and BlueZ
.PP
ubertooth(7): overview of Project Ubertooth
.PP
D. Spill and A. Bittau. "BlueSniff: Eve Meets Alice and Bluetooth."
USENIX WOOT 2007.
.SH AUTHOR
.PP
This manual page was written by Mike Ryan.
.SH COPYRIGHT
.PP
ubertooth\-rx(1) is Copyright (c) 2010\-2017 Michael Ossmann, Dominic
Spill, and others. This tool is released under the GPLv2. Refer to
\fB\fCCOPYING\fR for further details.
|
