Vulnerability Note VU#615456
Lemur Vehicle Monitors BlueDriver LSB2 does not authenticate users for Bluetooth access
Original Release date: 07 Apr 2016 | Last revised: 20 Apr 2016

Overview
The Lemur Vehicle Monitors BlueDriver is an aftermarket automotive device that connects to a vehicle’s OBD-II port and provides information about the vehicle’s performance.

The BlueDriver does not require a PIN for Bluetooth access, which allows anyone in range to send arbitrary commands to the vehicle’s CAN bus.

Description
CWE-306: Missing Authentication for Critical Function – CVE-2016-2354
The CERT Coordination Center has determined that the Lemur BlueDriver does not require a PIN to connect to it via Bluetooth.

This allows anyone within Bluetooth range to access standard OBD-II diagnostic information about the car, including gas mileage, Diagnostic Trouble codes, speed, emissions, etc.
It also allows an attacker to create a serial connection directly to the CAN (Controller Area Network) bus in the vehicle.

Any valid CAN command can be sent to the vehicle.

Depending on the vehicle, this may allow attackers to affect safety critical systems such as steering or braking.

Impact
The attack is limited to short (Bluetooth) range, but it could be launched from a compromised device inside the car (e.g., cell phone).

Depending on the car make and model, impact could range from information disclosure to life-threatening.

Solution
Apply an Update
Lemur Vehicle Monitors has released a firmware update to address this vulnerability:

BlueDriver scan tool users can update their sensor Firmware (F/W) by opening
their BlueDriver App and tapping ‘More’ > ‘Update Sensor F/W’ > ‘Check for
Updates’ and following the instructions.

The latest F/W for BlueDriver limits Bluetooth discoverability to 1 minute
after plug in. This added feature limits discovering (and then pairing) to
your BlueDriver to those who first plug in the sensor.

For clarification, the vendor has stated that discoverability is now limited to only when the device is plugged in, not every time the vehicle is turned on.

Vendor Information (Learn More)

VendorStatusDate NotifiedDate UpdatedLemur Vehicle MonitorsAffected03 Feb 201607 Apr 2016If you are a vendor and your product is affected, let
us know.

CVSS Metrics (Learn More)

Group
Score
Vector

Base
8.0
AV:A/AC:L/Au:N/C:P/I:C/A:C

Temporal
7.6
E:F/RL:U/RC:C

Environmental
6.7
CDP:H/TD:M/CR:L/IR:H/AR:L

References

http://www.lemurmonitors.com/
https://cwe.mitre.org/data/definitions/306.html

Credit

Thanks to Dan Klinedinst of the CERT/CC for reporting this vulnerability.
This document was written by Dan Klinedinst.

Other Information

CVE IDs:
CVE-2016-2354

Date Public:
07 Apr 2016

Date First Published:
07 Apr 2016

Date Last Updated:
20 Apr 2016

Document Revision:
25

FeedbackIf you have feedback, comments, or additional information about this vulnerability, please send us email.