{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-20473 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-20473 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-20473 is a medium-severity vulnerability in n/a, published on 1 Feb 2021. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-20473 and fix it if it is affected.\n\nWhat it is: CVE-2019-20473 is a medium-severity vulnerability in n/a, published on 1 Feb 2021. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-20473 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-20473/ (Markdown: https://insights.sbomify.com/CVE-2019-20473/index.md)","id":"CVE-2019-20473","markdown":"https://insights.sbomify.com/CVE-2019-20473/index.md","name":"CVE-2019-20473","record":{"aliases":["GHSA-rm3m-q3m3-2p24"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"GPS smartwatch","requires_auth":"none","summary":"The device prevents SIM PIN usage, allowing attackers to easily access the SIM card if the device is stolen.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"q90_junior_gps_horloge_firmware","vendor":"tk-star"}],"cvss":{"score":6.8,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"An issue was discovered on TK-Star Q90 Junior GPS horloge 3.1042.9.8656 devices. Any SIM card used with the device cannot have a PIN configured. If a PIN is configured, the device simply produces a \"Remove PIN and restart!\" message, and cannot be used. This makes it easier for an attacker to use the SIM card by stealing the device.","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":"Security feature bypass in n/a","id":"CVE-2019-20473","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2019-20474"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2019-20472"},"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":7.5,"headline":"Auth bypass in n/a","id":"CVE-2019-20470","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":"The device prevents SIM PIN usage, allowing attackers to easily access the SIM card if the device is stolen.","url":"https://insights.sbomify.com/CVE-2019-20473/"}