ieasytec vulnerabilities
Recent CVEs affecting ieasytec products. 4 tracked.
ieasytec has 4 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2018-07-13. Highest priority: CVE-2016-6545 (score 61/100).
- CVE-2016-6545 CRITICAL 9.8 MITIGATE Session cookies are not used for maintaining valid sessions in iTrack Easy
- CVE-2016-6544 HIGH 7.5 MITIGATE getgps data in iTrack Easy can be modified without authentication by setting the data using the parametercmd:s
- CVE-2016-6543 MEDIUM 5.9 MITIGATE A captured MAC/device ID of an iTrack Easy can be registered under multiple user accounts allowing access to g
- CVE-2016-6542 LOW 3.7 MITIGATE The iTrack device tracking ID number, also called "LosserID" in the web API, can be obtained by being in the r
FAQ
How do I fix ieasytec vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is ieasytec being exploited right now?
None of the tracked ieasytec CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which ieasytec CVE should I patch first?
CVE-2016-6545 currently ranks highest (61/100): Session cookies are not used for maintaining valid sessions in iTrack Easy.