CVE-2019-20470
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 on TK-Star Q90 Junior GPS horloge 3.1042.9.8656 devices. It performs actions based on certain SMS commands. This can be used to set up a voice communication channel from the watch to any telephone number, initiated by sending a specific SMS and using the default password, e.g., pw,<password>,call,<mobile_number> triggers an outbound call from the watch. The password is sometimes available because of CVE-2019-20471.
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 · high confidenceThe TK-Star Q90 Junior GPS watch (firmware 3.1042.9.8656) accepts unauthenticated SMS commands that trigger actions including outbound voice calls. An attacker can send an SMS in the format `pw,<password>,call,<mobile_number>` to the watch's SIM card number, initiating a call from the watch to any target telephone number. The required default password may be obtainable through the related CVE-2019-20471 vulnerability.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 TK-Star Q90 Junior GPS watches in your environmentReview asset inventories, device procurement records, or network scans to determine if any TK-Star Q90 Junior GPS watches are deployed in your organizationAffected if The organization has deployed TK-Star Q90 Junior GPS watches
-
Determine the firmware version of the deviceAccess the device settings through its mobile application or admin interface and navigate to the device information or firmware version sectionAffected if The firmware version is exactly 3.1042.9.8656
-
Verify the device has SMS communication capabilityConfirm the watch has an active SIM card and can receive SMS messages - this is typically indicated by the device being powered on and having cellular network connectivityAffected if The device can receive SMS messages (SIM card is active and has cellular service)
Your organization is affected if you have deployed TK-Star Q90 Junior GPS watches running firmware version 3.1042.9.8656 that have active SIM cards capable of receiving SMS commands.
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 dataSince this is an IoT device vulnerability requiring vendor firmware remediation, organizations should contact TK-Star for a security patch, consider network-level controls to restrict SMS-based device management, or replace affected devices with updated models that address this vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20470 — 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-20470 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