{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-17483 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-17483 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-17483 is a high-severity missing authorization vulnerability in n/a, published on 16 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-17483 and fix it if it is affected.\n\nWhat it is: CVE-2020-17483 is a high-severity missing authorization vulnerability in n/a, published on 16 Dec 2023. 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-2020-17483 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-2020-17483/ (Markdown: https://insights.sbomify.com/CVE-2020-17483/index.md)","id":"CVE-2020-17483","markdown":"https://insights.sbomify.com/CVE-2020-17483/index.md","name":"CVE-2020-17483","record":{"aliases":["GHSA-jj8x-8hrh-x979"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"GPS Tracker","requires_auth":"none","summary":"An attacker can access sensitive device information via an unauthenticated JSON endpoint on the GPS Tracker's port 9000.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gps_tracker","vendor":"uffizio"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"An improper access control vulnerability exists in Uffizio's GPS Tracker all versions that lead to sensitive information disclosure of all the connected devices. By visiting the vulnerable host at port 9000, we see it responds with a JSON body that has all the details about the devices which have been deployed.","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":"Missing authorization in n/a","id":"CVE-2020-17483","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Open redirect in n/a","id":"CVE-2020-17484"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2020-17482"},"products":["n/a"],"published":"2023-12-16","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2020-17485","kev_date_added":null,"published":"2023-12-16"},{"cvss_score":7.1,"headline":"Uffizio GPS Tracker Cross-site Scripting","id":"CVE-2021-32927","kev_date_added":null,"published":"2022-04-22"},{"cvss_score":6.1,"headline":"Open redirect in n/a","id":"CVE-2020-17484","kev_date_added":null,"published":"2023-12-16"},{"cvss_score":4.3,"headline":"Uffizio GPS Tracker Cross-site Request Forgery","id":"CVE-2021-32929","kev_date_added":null,"published":"2022-04-22"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"An attacker can access sensitive device information via an unauthenticated JSON endpoint on the GPS Tracker's port 9000.","url":"https://insights.sbomify.com/CVE-2020-17483/"}