{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-7729 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-7729 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-7729 is a high-severity vulnerability in n/a, published on 11 Jul 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-7729 and fix it if it is affected.\n\nWhat it is: CVE-2017-7729 is a high-severity vulnerability in n/a, published on 11 Jul 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-7729 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-7729/ (Markdown: https://insights.sbomify.com/CVE-2017-7729/index.md)","id":"CVE-2017-7729","markdown":"https://insights.sbomify.com/CVE-2017-7729/index.md","name":"CVE-2017-7729","record":{"aliases":["GHSA-74w8-fgf9-wcw8"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"iSmartAlarm cube","requires_auth":"none","summary":"Attackers can intercept cleartext keys transmitted by iSmartAlarm cube devices, potentially bypassing access controls and reading sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cubeone_firmware","vendor":"ismartalarm"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"}],"description":"On iSmartAlarm cube devices, there is Incorrect Access Control because a \"new key\" is transmitted in cleartext.","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-2017-7729","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2017-7730"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2017-7728"},"products":["n/a"],"published":"2017-07-11","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2017-13664","kev_date_added":null,"published":"2017-12-01"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2017-7728","kev_date_added":null,"published":"2017-07-11"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2017-13663","kev_date_added":null,"published":"2017-12-01"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2017-7726","kev_date_added":null,"published":"2017-07-11"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2017-7730","kev_date_added":null,"published":"2017-07-11"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2018-16224","kev_date_added":null,"published":"2018-11-20"}],"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 intercept cleartext keys transmitted by iSmartAlarm cube devices, potentially bypassing access controls and reading sensitive data.","url":"https://insights.sbomify.com/CVE-2017-7729/"}