iTrack Easy contains multiple vulnerabilities
Original Release date: 25 Oct 2016 | Last revised: 25 Oct 2016
iTrack Easy contains multiple vulnerabilities including sensitive information exposure and missing authentication.
CWE-200: Information Exposure – CVE-2016-6542
The iTrack device tracking ID number is the device’s BLE MAC address.
It can be obtained by being in range of the device.CWE-799: Improper Control of Interaction Frequency – CVE-2016-6543A captured MAC/device ID can be registered under multiple user accounts allowing access to getgps GPS data, which can allow unauthenticated parties to track the device.CWE-306: Missing Authentication for Critical Function – CVE-2016-6544getgps data can be modified without authentication by setting the data using the parametercmd:setothergps.
This vulnerability can be exploited to alter the GPS data of a lost device.CWE-613: Insufficient Session Expiration – CVE-2016-6545Session cookies are not used for maintaining valid sessions.
The user’s password is passed as a POST parameter over HTTPS using a base64 encoded passwd field on every request.CWE-313: Cleartext Storage in a File or on Disk – CVE-2016-6546The iTrack Easy mobile application stores the account password used to authenticate to the cloud API in base64-encoding in the cache.db file.
The base64 encoding format is considered equivalent to cleartext.The CVSS Score below represents CVE-2016-6544
These vulnerabilities may allow an unauthenticated, remote attacker to track a user’s location without their consent.
The CERT/CC is currently unaware of a practical solution to this problem.
Use with cautionUntil the vendor supplies a patch, the user should practice caution as to where these devices are used.
Vendor Information (Learn More)
13 Sep 2016
25 Oct 2016
If you are a vendor and your product is affected, let us know.
CVSS Metrics (Learn More)
Thanks to Deral Heiland and Adam Compton of Rapid7, Inc. for reporting this vulnerability.
This document was written by Trent Novelly.
If you have feedback, comments, or additional information about this vulnerability, please send us email.