# CVE-2019-20468: Misconfiguration in n/a

> The SeTracker2 app requests excessive permissions, allowing potential unauthorized access to external storage and contacts.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Feb 2021
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-65g2-386j-x397

## What is CVE-2019-20468?

CVE-2019-20468 is a critical vulnerability in n/a, published on 1 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in SeTracker2 for TK-Star Q90 Junior GPS horloge 3.1042.9.8656 devices. It has unnecessary permissions such as READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE, and READ_CONTACTS.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2019-20468?

It affects 1 product.


Products: Tk-Star Q90 Junior Gps Horloge Firmware.

## How do I fix CVE-2019-20468?

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

## Is CVE-2019-20468 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-20471](https://insights.sbomify.com/CVE-2019-20471/): Hardcoded credentials in n/a (high 7.8)
- [CVE-2019-20470](https://insights.sbomify.com/CVE-2019-20470/): Auth bypass in n/a (high 7.5)
- [CVE-2019-20473](https://insights.sbomify.com/CVE-2019-20473/): Security feature bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-20468 and fix it if it is affected.

What it is: CVE-2019-20468 is a critical vulnerability in n/a, published on 1 Feb 2021. 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-2019-20468 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-2019-20468/ (Markdown: https://insights.sbomify.com/CVE-2019-20468/index.md)
```

## Sources

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

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