itrackeasy vulnerabilities and fixes
Recent CVEs affecting itrackeasy, with upgrade or downgrade steps. 3 tracked.
itrackeasy has 3 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-6546 HIGH 7.8 MITIGATE The iTrack Easy mobile application stores the account password used to authenticate to the cloud API in base64
- CVE-2016-6545 CRITICAL 9.8 MITIGATE Session cookies are not used for maintaining valid sessions in iTrack Easy
- 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 itrackeasy 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 itrackeasy being exploited right now?
None of the tracked itrackeasy CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which itrackeasy 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.