# CVE-2020-13425: Denial of service in n/a

> Attackers can trigger the alarm feature on TrackR devices, causing battery exhaustion and resulting in a denial of service.

- **Severity:** High 7.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** Yes
- **Published:** 23 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8hf2-8wmv-gjp5

## What is CVE-2020-13425?

CVE-2020-13425 is a high-severity denial of service vulnerability in n/a, published on 23 May 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

TrackR devices through 2020-05-06 allow attackers to trigger the Beep (aka alarm) feature, which will eventually cause a denial of service when battery capacity is exhausted.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2020-13425?

It affects 1 product.


Products: Thetrackr Trackr Firmware.

## How do I fix CVE-2020-13425?

No fix published yet.

## Is CVE-2020-13425 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-6539](https://insights.sbomify.com/CVE-2016-6539/): TrackR Bravo MAC address can be exposed in close proximity and used to obtain the device ID (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-13425 and fix it if it is affected.

What it is: CVE-2020-13425 is a high-severity denial of service vulnerability in n/a, published on 23 May 2020. 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-2020-13425 in the wild and no public exploit code.

Affected product: n/a. 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-2020-13425/ (Markdown: https://insights.sbomify.com/CVE-2020-13425/index.md)
```

## Sources

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

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