search menu icon-carat-right cmu-wordmark

CERT Coordination Center

CalAmp LMU-3030 devices may not authenticate SMS interface

Vulnerability Note VU#251927

Original Release Date: 2017-06-08 | Last Revised: 2017-06-14

Overview

OBD-II devices are used to provide telematics information for managers of fleets of vehicles. One type of device, manufactured by CalAmp, has an SMS (text message) interface. We have found multiple deployments where no password was configured for this interface by the integrator / reseller. Companies using the CalAmp hardware should be aware that they need to set a password or disable SMS. Vendors were notified and the SMS interface was disabled or password-protected by all vendors known to be affected.

Description

CWE-306: Missing Authentication for Critical Function - CVE-2017-3217

The CalAmp LMU 3030 series of devices includes an SMS interface on both CDMA and GSM versions of the device. This interface must be password protected, otherwise, the attacker only needs to know the phone number of the device (via an IMSI Catcher, for example) to send administrative commands to the device. These commands can be used to provide ongoing, real-time access to the device and can configure parameters such as IP addresses, firewall rules, and passwords.

Impact

The devices provide vehicle tracking via GPS coordinates, heading, and speed, as well as maintenance information. Older versions of the firmware could be remotely updated with malicious code that could affect the CAN bus of the vehicle.

Solution

Configure SMS password

Vendors that were known to be affected have been contacted and have password-protected or disabled the SMS interface. Other vendors that use the CalAmp LMU-3030 in their system should do the same.

Update device firmware

We recommend upgrading to the latest firmware from CalAmp in order to provide “defense in depth”. These devices can have complex supply chains so the reseller may need to work with a service provider or systems integrator to make these changes.

Vendor Information

251927
 
Affected   Unknown   Unaffected

AT&T

Notified:  April 17, 2017 Updated:  June 08, 2017

Status

  Affected

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

We are not aware of further vendor information regarding this vulnerability.

CalAmp Inc.

Notified:  April 17, 2017 Updated:  June 14, 2017

Statement Date:   June 13, 2017

Status

  Affected

Vendor Statement

CalAmp takes the security of our telematics devices very seriously. Our security commitment extends to providing customers with best-in-class security feature enhancements, and world-class applications support to combat any system level security vulnerabilities.


The CERT vulnerability note (VU#251927) highlights a potential vulnerability for customers who have chosen not to use passwords. These customers are advised to comply with the CERT recommended solutions including the use of passwords, and to update to the latest device firmware to take advantage of enhanced security features.

In addition to recommending the use of passwords and the use of security features that CalAmp builds into its products, CalAmp continually monitors the latest security trends and works with experts and authorities to ensure that we meet or exceed industry standards for protection.

Vendor Information

We are not aware of further vendor information regarding this vulnerability.

GPS Insight

Notified:  April 17, 2017 Updated:  June 08, 2017

Status

  Affected

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

We are not aware of further vendor information regarding this vulnerability.


CVSS Metrics

Group Score Vector
Base 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C
Temporal 8.3 E:F/RL:OF/RC:C
Environmental 6.7 CDP:MH/TD:M/CR:H/IR:H/AR:H

References

Acknowledgements

We would like to thank all of the affected vendors for addressing this quickly

This document was written by Dan Klinedinst.

Other Information

CVE IDs: CVE-2017-3217
Date Public: 2017-06-08
Date First Published: 2017-06-08
Date Last Updated: 2017-06-14 15:22 UTC
Document Revision: 17

Sponsored by the Department of Homeland Security Office of Cybersecurity and Communications.