CVE-2016-2354
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Bluetooth functionality in Lemur Vehicle Monitors BlueDriver before 2016-04-07 supports unrestricted pairing without a PIN, which allows remote attackers to send arbitrary CAN commands by leveraging access to a device inside or adjacent to the vehicle, as demonstrated by a CAN command to disrupt braking or steering.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe BlueDriver Bluetooth OBD-II diagnostic device before the 2016-04-07 update allows unrestricted Bluetooth pairing without requiring a PIN. Any Bluetooth-capable device within range can connect and send arbitrary CAN (Controller Area Network) commands through the OBD-II port, potentially enabling manipulation of vehicle safety-critical systems including braking and steering.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 6.3.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if a BlueDriver OBD-II device is presentPhysically inspect the OBD-II port (typically under the dashboard) for a BlueDriver sensor, or check paired Bluetooth devices on your phone/tablet for a device named 'BlueDriver' or similarAffected if A BlueDriver Bluetooth OBD-II device is connected to the vehicle's OBD-II port
-
Check the BlueDriver firmware versionOpen the BlueDriver mobile app and navigate to Settings or Device Info to view the firmware version. Alternatively, check any documentation or packaging that came with the deviceAffected if The displayed firmware version is 6.3.2 or earlier, or if no version information is available and the device was purchased before April 2016
-
Verify if PIN authentication is required for Bluetooth pairingAttempt to pair a new Bluetooth device with the BlueDriver - observe whether a PIN prompt appears during the pairing process. On the BlueDriver app, check Settings for a PIN or security optionAffected if The device pairs without prompting for any PIN or security code, indicating the vulnerable firmware is in use
You are affected if a BlueDriver OBD-II device with firmware version 6.3.2 or earlier is installed and pairs via Bluetooth without requiring a PIN.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate BlueDriver firmware to version 2016-04-07 or later which implements PIN authentication for Bluetooth pairing. Until updated, physically secure the OBD-II port and limit Bluetooth device proximity to the vehicle.
- Consultation8.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-2354 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-2354 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data