# CVE-2016-6542: The MAC address/device tracking ID of an iTrack Easy can be obtained within range of the device

> An attacker within range can obtain the iTrack Easy device's MAC address and tracking ID, exposing unique device identifiers.

- **Severity:** Low 3.7 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xhgf-3v3f-px6x

## What is CVE-2016-6542?

CVE-2016-6542 is a low-severity vulnerability in iTrack Easy, published on 13 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-20 (Improper Input Validation), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Ieasytec Itrackeasy.

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

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

## Is CVE-2016-6542 being exploited?

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

## Other vulnerabilities in iTrack Easy

- [CVE-2016-6545](https://insights.sbomify.com/CVE-2016-6545/): iTrack Easy does not use session cookies to maintain sessions and POSTs the users password over HTTPS for each request (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-6542 is a low-severity vulnerability in iTrack Easy, published on 13 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-6542 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-6542/ (Markdown: https://insights.sbomify.com/CVE-2016-6542/index.md)
```

## Sources

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

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