Ieasytec develops a small line of tracking and asset-management products, including iTrack Easy and related variants, that handle user authentication and data exposure across focused deployments. The recurrent vulnerability pattern centers on access-control, authentication, and input-validation weaknesses alongside exposure of sensitive information, reflecting the authentication and data-handling demands of user-facing management interfaces. Current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Ieasytec over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2016-6545CRITICAL 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 ever | Jul 13, 2018 | 9.8 | 31 | NO | NO |
CVE-2016-6544HIGH 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 | Jul 13, 2018 | 7.5 | 24 | NO | NO |
CVE-2016-6543MEDIUM 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 d | Jul 13, 2018 | 5.9 | 20 | NO | NO |
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 addre | Jul 13, 2018 | 3.7 | 16 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Ieasytec.
Media articles that mention a CVE ID that affects a product developed by Ieasytec — matched by CVE ID, not by vendor name.