# CVE-2016-6541: Auth bypass in Bravo Mobile Application

> Unauthenticated pairing allows attackers to modify device attributes on TrackR Bravo trackers, requiring users to update their mobile apps.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jul 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7cw5-6327-97r5

## What is CVE-2016-6541?

CVE-2016-6541 is a high-severity authentication bypass vulnerability in TrackR Bravo Mobile Application, published on 6 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

TrackR Bravo device allows unauthenticated pairing, which enables unauthenticated connected applications to write to various device attributes. Updated apps, version 5.1.6 for iOS and 2.2.5 for Android, have been released by the vendor to address the vulnerabilities in CVE-2016-6538, CVE-2016-6539, CVE-2016-6540 and CVE-2016-6541.

Weakness: CWE-287 (Improper Authentication), CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Thetrackr Trackr Bravo Firmware.

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

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

## Is CVE-2016-6541 being exploited?

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

## Other vulnerabilities in TrackR Bravo Mobile Application

- [CVE-2016-6538](https://insights.sbomify.com/CVE-2016-6538/): TrackR Bravo mobile application stores account passwords in cleartext (high 8.8)
- [CVE-2016-6540](https://insights.sbomify.com/CVE-2016-6540/): Missing authorization in Bravo Mobile Application (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-6541 is a high-severity authentication bypass vulnerability in TrackR Bravo Mobile Application, published on 6 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-6541 in the wild and no public exploit code.

Affected product: TrackR Bravo Mobile Application. 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-6541/ (Markdown: https://insights.sbomify.com/CVE-2016-6541/index.md)
```

## Sources

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

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