{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-27483 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-27483 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-27483 is a critical vulnerability in n/a, published on 16 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-27483 and fix it if it is affected.\n\nWhat it is: CVE-2020-27483 is a critical vulnerability in n/a, published on 16 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-27483 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-27483/ (Markdown: https://insights.sbomify.com/CVE-2020-27483/index.md)","id":"CVE-2020-27483","markdown":"https://insights.sbomify.com/CVE-2020-27483/index.md","name":"CVE-2020-27483","record":{"aliases":["GHSA-cr23-gw9g-5cwj"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Garmin Forerunner watch","requires_auth":"low_privilege","summary":"A malicious ConnectIQ app can leak runtime memory or achieve remote code execution on Garmin Forerunner 235 watches via unchecked stack offsets.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"forerunner_235_firmware","vendor":"garmin"}],"cvss":{"score":9.9,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-129","name":"Improper Validation of Array Index"}],"description":"Garmin Forerunner 235 before 8.20 is affected by: Array index error. The component is: ConnectIQ TVM. The attack vector is: To exploit the vulnerability, the attacker must upload a malicious ConnectIQ application to the ConnectIQ store. The ConnectIQ program interpreter trusts the offset provided for the stack value duplication instruction, DUP. The offset is unchecked and memory prior to the start of the execution stack can be read and treated as a TVM object. A successful exploit could use the vulnerability to leak runtime information such as the heap handle or pointer for a number of TVM context variables. Some reachable values may be controlled enough to forge a TVM object on the stack, leading to possible remote code execution.","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":"Information disclosure in n/a","id":"CVE-2020-27483","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Integer overflow in n/a","id":"CVE-2020-27484"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2020-27481"},"products":["n/a"],"published":"2020-11-16","related":[{"cvss_score":9.9,"headline":"Integer overflow in n/a","id":"CVE-2020-27484","kev_date_added":null,"published":"2020-11-16"},{"cvss_score":9.9,"headline":"Memory corruption in n/a","id":"CVE-2020-27485","kev_date_added":null,"published":"2020-11-16"},{"cvss_score":9.9,"headline":"Memory corruption in n/a","id":"CVE-2020-27486","kev_date_added":null,"published":"2020-11-16"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"A malicious ConnectIQ app can leak runtime memory or achieve remote code execution on Garmin Forerunner 235 watches via unchecked stack offsets.","url":"https://insights.sbomify.com/CVE-2020-27483/"}