# CVE-2016-6546: iTrack Easy mobile application stores the user password in base-64 encoding/cleartext

> The iTrack Easy mobile app stores user passwords in base64 encoding, allowing attackers with device access to retrieve credentials and take over accounts.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4fv4-f7m5-w88w

## What is CVE-2016-6546?

CVE-2016-6546 is a high-severity vulnerability in iTrack Easy, published on 13 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-255, CWE-313 (Cleartext Storage in a File or on Disk)

## Which versions are affected by CVE-2016-6546?

It affects 1 product.


Products: Kkmcn Itrackeasy.

## How do I fix CVE-2016-6546?

No fix has been published for CVE-2016-6546 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-6546 being exploited?

There is no known exploitation of CVE-2016-6546 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6546 and fix it if it is affected.

What it is: CVE-2016-6546 is a high-severity vulnerability in iTrack Easy, published on 13 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-6546 in the wild and no public exploit code.

Affected product: iTrack Easy. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-6546/ (Markdown: https://insights.sbomify.com/CVE-2016-6546/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-6546
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-6546
- OSV: https://osv.dev/vulnerability/CVE-2016-6546

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-6546/
Summaries are generated and may contain mistakes; the official description above is the record.