iTrack Easy mobile application stores the user password in base-64 encoding/cleartext

published 2018-07-13 8 y ago modified 2026-06-17 4 mo ago also EUVD-2016-7467

cvss: 7.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 35%
public exploits: 0; none known

The 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.

Exploit prediction

0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

blog.rapid7.com https://blog.rapid7.com/2016/10/25/multiple-bluetooth-low-energy-ble-tracker-vulnerabilities/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.0	7.8	CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	2.1	AV:L/AC:L/Au:N/C:P/I:N/A:N

Affected products

iTrack Easy

Classification

Weakness

CWE-313 Cleartext Storage in a File or on Disk
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-255 Credentials Management Errors

References

blog.rapid7.com /2016/10/25/multiple-bluetooth-low-energy-ble-tracker-vulnerabilities/
exploit, third-party-advisory
kb.cert.org /vuls/id/974055
third-party-advisory, us-government-resource
securityfocus.com /bid/93875
vdb-entry, third-party-advisory

Sources

CVE List CVE-2016-6546
NVD CVE-2016-6546

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary