CVE-2019-20468
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe SeTracker2 GPS watch companion app requests three unnecessary Android permissions (READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE, and READ_CONTACTS) that are not required for its core GPS tracking functionality. These excessive permissions violate the principle of least privilege and create potential for unauthorized data access or exfiltration if the app is compromised.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.1042.9.8656CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the SeTracker2 companion app installationOn the Android device, go to Settings > Apps and search for SeTracker2, or use adb shell pm list packages to list installed packages. Look for packages containing 'setracker' in the name.Affected if The SeTracker2 app is installed on the device
-
Check the Tk Star Q90 Junior GPS watch firmware versionConnect the GPS watch to the SeTracker2 app and navigate to the device settings within the app. The firmware version is typically displayed under Device Info or Settings > About Device. Alternatively, check the watch itself or consult the device manual for firmware version retrieval.Affected if The firmware version is exactly 3.1042.9.8656
-
Extract and inspect the AndroidManifest.xmlUse APK extraction tools (such as APK Extractor or adb pull) to obtain the SeTracker2 APK from the device, then use a tool like apktool or AXMLPrinter2 to decompile the AndroidManifest.xml file.Affected if The APK cannot be extracted or does not exist on the device
-
Check for unnecessary permissions in AndroidManifest.xmlLocate the <uses-permission> tags within the AndroidManifest.xml file. Inspect whether any of the following permissions are declared: android.permission.READ_EXTERNAL_STORAGE, android.permission.WRITE_EXTERNAL_STORAGE, or android.permission.READ_CONTACTS.Affected if Any of these three permissions are present in the manifest file
The environment is affected if the SeTracker2 companion app is running with Tk Star Q90 Junior firmware version 3.1042.9.8656 and the AndroidManifest.xml contains READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE, or READ_CONTACTS permissions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReview and remove unnecessary permissions from the AndroidManifest.xml, retaining only permissions required for legitimate GPS tracking features (likely ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION, and INTERNET). Verify functionality remains intact after removal.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20468 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-20468 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data