ieasytec vulnerabilities

Products

• itrack easy 2
• itrackeasy 2

Latest ieasytec CVEs

Newest publication first

1. CVE-2016-6545 iTrack Easy does not use session cookies to maintain sessions and POSTs the users password over HTTPS for each request

   Published 2018-07-13

   Critical·CVSS 9.8 EPSS 3.0%

   Session cookies are not used for maintaining valid sessions in iTrack Easy. The user's password is passed as a POST parameter over HTTPS using a base64 encoded passwd field on every request. In this implementation, sessions can only be terminated when the user changes the associa...

2. CVE-2016-6544 iTrack Easy's getgps data can be modified without authentication

   Published 2018-07-13

   High·CVSS 7.5 EPSS 3.3%

   getgps data in iTrack Easy 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.

3. CVE-2016-6543 A captured MAC/device ID of an iTrack Easy can be registered under multiple user accounts allowing access to getgps GPS data

   Published 2018-07-13

   Medium·CVSS 5.9 EPSS 2.1%

   A captured MAC/device ID of an iTrack Easy can be registered under multiple user accounts allowing access to getgps GPS data, which can allow unauthenticated parties to track the device.

4. CVE-2016-6542 The MAC address/device tracking ID of an iTrack Easy can be obtained within range of the device

   Published 2018-07-13

   Low·CVSS 3.7 EPSS 1.7%

   The iTrack device tracking ID number, also called "LosserID" in the web API, can be obtained by being in the range of an iTrack device. The tracker ID is the device's BLE MAC address.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.