{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-10721 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-10721 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-10721 is a medium-severity vulnerability in n/a, published on 17 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-10721 and fix it if it is affected.\n\nWhat it is: CVE-2017-10721 is a medium-severity vulnerability in n/a, published on 17 Jun 2019. 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-10721 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-2017-10721/ (Markdown: https://insights.sbomify.com/CVE-2017-10721/index.md)","id":"CVE-2017-10721","markdown":"https://insights.sbomify.com/CVE-2017-10721/index.md","name":"CVE-2017-10721","record":{"aliases":["GHSA-w6vm-69jx-3557"],"analysis":{"component_type":"iot_embedded","fix_type":"configuration_change","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Shekar Endoscope","requires_auth":"low_privilege","summary":"Attackers can access video feeds and gain network footholds because the endoscope device has Telnet enabled by default.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"endoscope_camera_firmware","vendor":"ishekar"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"Recently it was discovered as a part of the research on IoT devices in the most recent firmware for Shekar Endoscope that the device has Telnet functionality enabled by default. This device acts as an Endoscope camera that allows its users to use it in various industrial systems and settings, car garages, and also in some cases in the medical clinics to get access to areas that are difficult for a human being to reach. Any breach of this system can allow an attacker to get access to video feed and pictures viewed by that user and might allow them to get a foot hold in air gapped networks especially in case of nation critical infrastructure/industries.","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":"Misconfiguration in n/a","id":"CVE-2017-10721","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2017-10722"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2017-10720"},"products":["n/a"],"published":"2019-06-17","related":[{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-10723","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-10724","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2017-10720","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2017-10722","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2017-10718","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":6.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2017-10719","kev_date_added":null,"published":"2019-06-17"}],"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-05","vendors":["n/a"]},"summary":"Attackers can access video feeds and gain network footholds because the endoscope device has Telnet enabled by default.","url":"https://insights.sbomify.com/CVE-2017-10721/"}