{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-23306 exists.","fix":"No fix has been published for CVE-2023-23306 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-23306 is a critical memory corruption vulnerability in n/a, published on 23 May 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-2023-23306 and fix it if it is affected.\n\nWhat it is: CVE-2023-23306 is a critical memory corruption vulnerability in n/a, published on 23 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-23306 exists.\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-2023-23306/ (Markdown: https://insights.sbomify.com/CVE-2023-23306/index.md)","id":"CVE-2023-23306","markdown":"https://insights.sbomify.com/CVE-2023-23306/index.md","name":"CVE-2023-23306","record":{"aliases":["GHSA-r7vh-g6cm-2j84"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Garmin Connect IQ","requires_auth":"none","summary":"A malicious application can exploit a type confusion flaw in the Ant BurstPayload API to overwrite memory and execute arbitrary code on the device.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"connect-iq","vendor":"garmin"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"The `Toybox.Ant.BurstPayload.add` API method in CIQ API version 2.2.0 through 4.1.7 suffers from a type confusion vulnreability, which can result in an out-of-bounds write operation. A malicious application could create a specially crafted `Toybox.Ant.BurstPayload` object, call its `add` method, override arbitrary memory and hijack the execution of the device's firmware.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2023-23306","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2023-23313"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2023-23305"},"products":["n/a"],"published":"2023-05-23","related":[{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2023-23298","kev_date_added":null,"published":"2023-05-23"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-23300","kev_date_added":null,"published":"2023-05-23"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-23301","kev_date_added":null,"published":"2023-05-23"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-23302","kev_date_added":null,"published":"2023-05-23"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-23303","kev_date_added":null,"published":"2023-05-23"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-23305","kev_date_added":null,"published":"2023-05-23"}],"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-31","vendors":["n/a"]},"summary":"A malicious application can exploit a type confusion flaw in the Ant BurstPayload API to overwrite memory and execute arbitrary code on the device.","url":"https://insights.sbomify.com/CVE-2023-23306/"}