Bluetooth 2.1 is designed to, among other things, be more secure than Bluetooth 2.0. And it is ... if you properly implement it using a one-time-password scheme. But that requirement is buried deep within a 1,400-page protocol document, and most manufacturers aren't even aware it exists.
Fortunately, there are almost no existing Bluetooth 2.1 implementations.
Why "fortunately"? Well, because if you don't know about and follow that one-time-password requirement, a Bluetooth 2.1 session can be hijacked and the password stolen in less than one second with a man-in-the-middle attack.
"Good protocol should be hard to get wrong and easy to get right," [Andrew Lindell, chief cryptographer for Aladdin Knowledge Systems Ltd.] said Wednesday at the Black Hat briefings. "Even the best protocols can be badly implemented; in Bluetooth it is the opposite. Unless you really know what you are doing, it's easy to get wrong."