{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-2913 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-2913 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-2913 is a high-severity vulnerability in Circle, published on 7 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-2913 and fix it if it is affected.\n\nWhat it is: CVE-2017-2913 is a high-severity vulnerability in Circle, published on 7 Nov 2017. 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-2017-2913 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-2913/ (Markdown: https://insights.sbomify.com/CVE-2017-2913/index.md)","id":"CVE-2017-2913","markdown":"https://insights.sbomify.com/CVE-2017-2913/index.md","name":"CVE-2017-2913","record":{"aliases":["GHSA-9gq9-g9hm-vm5f"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Circle with Disney","requires_auth":"none","summary":"Attackers can bypass SSL certificate validation in Circle with Disney devices by exploiting a flaw in the Bluecoat library, allowing man-in-the-middle attacks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"circle_with_disney_firmware","vendor":"meetcircle"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"An exploitable vulnerability exists in the filtering functionality of Circle with Disney. SSL certificates for specific domain names can cause the Bluecoat library to accept a different certificate than intended. An attacker can host an HTTPS server with this certificate 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":"Security feature bypass in Circle","id":"CVE-2017-2913","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in Circle","id":"CVE-2017-2914"},"packages":[],"prev":{"headline":"Security feature bypass in Circle","id":"CVE-2017-2912"},"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":"Race condition in Circle","id":"CVE-2017-2898","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 bypass SSL certificate validation in Circle with Disney devices by exploiting a flaw in the Bluecoat library, allowing man-in-the-middle attacks.","url":"https://insights.sbomify.com/CVE-2017-2913/"}