{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-20470 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-20470 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-20470 is a high-severity authentication bypass 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."},"fix_prompt":"Check this codebase for CVE-2019-20470 and fix it if it is affected.\n\nWhat it is: CVE-2019-20470 is a high-severity authentication bypass 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.\nExploitation: There is no known exploitation of CVE-2019-20470 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-20470/ (Markdown: https://insights.sbomify.com/CVE-2019-20470/index.md)","id":"CVE-2019-20470","markdown":"https://insights.sbomify.com/CVE-2019-20470/index.md","name":"CVE-2019-20470","record":{"aliases":["GHSA-mc4h-8cxf-938r"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass","other"],"network_reachable":"yes","non_default_config":false,"product_category":"GPS smartwatch","requires_auth":"none","summary":"Attackers can initiate unauthorized outbound calls from TK-Star GPS watches by exploiting default SMS command passwords, bypassing authentication controls.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"q90_junior_gps_horloge_firmware","vendor":"tk-star"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-1188","name":"Initialization of a Resource with an Insecure Default"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"An 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,\u003cpassword\u003e,call,\u003cmobile_number\u003e triggers an outbound call from the watch. The password is sometimes available because of CVE-2019-20471.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Auth bypass in n/a","id":"CVE-2019-20470","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2019-20471"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2019-20469"},"products":["n/a"],"published":"2021-02-01","related":[{"cvss_score":9.8,"headline":"Misconfiguration in n/a","id":"CVE-2019-20468","kev_date_added":null,"published":"2021-02-01"},{"cvss_score":7.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2019-20471","kev_date_added":null,"published":"2021-02-01"},{"cvss_score":6.8,"headline":"Security feature bypass in n/a","id":"CVE-2019-20473","kev_date_added":null,"published":"2021-02-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can initiate unauthorized outbound calls from TK-Star GPS watches by exploiting default SMS command passwords, bypassing authentication controls.","url":"https://insights.sbomify.com/CVE-2019-20470/"}