{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-2898 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-2898 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-2898 is a critical vulnerability in Circle, published on 7 Nov 2017. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-2898 and fix it if it is affected.\n\nWhat it is: CVE-2017-2898 is a critical vulnerability in Circle, published on 7 Nov 2017. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-2898 in the wild and no public exploit code.\n\nAffected product: Circle. 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-2017-2898/ (Markdown: https://insights.sbomify.com/CVE-2017-2898/index.md)","id":"CVE-2017-2898","markdown":"https://insights.sbomify.com/CVE-2017-2898/index.md","name":"CVE-2017-2898","record":{"aliases":["GHSA-mhxp-xvr8-vwjm"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Circle with Disney","requires_auth":"low_privilege","summary":"Attackers can install unsigned firmware via crafted packets due to a race condition in signature verification, leading to arbitrary code execution on Circle devices.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"circle_with_disney_firmware","vendor":"meetcircle"}],"cvss":{"score":9.9,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"An exploitable vulnerability exists in the signature verification of the firmware update functionality of Circle with Disney. Specially crafted network packets can cause an unsigned firmware to be installed in the device resulting in arbitrary code execution. An attacker can send a series of packets to trigger this vulnerability.","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":"Race condition in Circle","id":"CVE-2017-2898","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Integer overflow in Blender","id":"CVE-2017-2899"},"packages":[],"prev":{"headline":"Memory corruption in libxls","id":"CVE-2017-2897"},"products":["Circle"],"published":"2017-11-07","related":[{"cvss_score":9.9,"headline":"Command injection in Circle","id":"CVE-2017-2866","kev_date_added":null,"published":"2017-11-07"},{"cvss_score":9.9,"headline":"Command injection in Circle","id":"CVE-2017-2890","kev_date_added":null,"published":"2017-11-07"},{"cvss_score":9.9,"headline":"Path traversal in Circle","id":"CVE-2017-2916","kev_date_added":null,"published":"2017-11-07"},{"cvss_score":9.9,"headline":"Command injection in Circle","id":"CVE-2017-2917","kev_date_added":null,"published":"2017-11-07"},{"cvss_score":9.6,"headline":"Command injection in Circle","id":"CVE-2017-2865","kev_date_added":null,"published":"2017-11-07"},{"cvss_score":9.6,"headline":"Command injection in Circle","id":"CVE-2017-2881","kev_date_added":null,"published":"2017-11-07"}],"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-09-16","vendors":["Circle Media"]},"summary":"Attackers can install unsigned firmware via crafted packets due to a race condition in signature verification, leading to arbitrary code execution on Circle devices.","url":"https://insights.sbomify.com/CVE-2017-2898/"}