{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-17436 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-17436 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-17436 is a high-severity vulnerability in n/a, published on 7 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-17436 and fix it if it is affected.\n\nWhat it is: CVE-2017-17436 is a high-severity vulnerability in n/a, published on 7 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-17436 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-17436/ (Markdown: https://insights.sbomify.com/CVE-2017-17436/index.md)","id":"CVE-2017-17436","markdown":"https://insights.sbomify.com/CVE-2017-17436/index.md","name":"CVE-2017-17436","record":{"aliases":["GHSA-rvq2-hqr6-pgqq"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Vaultek Gun Safe","requires_auth":"none","summary":"Attackers can eavesdrop on unencrypted Bluetooth communications to steal passcodes from Vaultek Gun Safes, bypassing advertised security features.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vt20i_firmware","vendor":"vaulteksafe"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-326","name":"Inadequate Encryption Strength"}],"description":"An issue was discovered in the software on Vaultek Gun Safe VT20i products. There is no encryption of the session between the Android application and the safe. The website and marketing materials advertise that this communication channel is encrypted with \"Highest Level Bluetooth Encryption\" and \"Data transmissions are secure via AES256 bit encryption.\" These claims, however, are not true. Moreover, AES256 bit encryption is not supported in the Bluetooth Low Energy (BLE) standard, so it would have to be at the application level. This lack of encryption allows an individual to learn the passcode by eavesdropping on the communications between the application and the safe.","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":"Weak cryptography in n/a","id":"CVE-2017-17436","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Null dereference in n/a","id":"CVE-2017-17439"},"packages":[],"prev":{"headline":"An issue was discovered in the software on Vaultek Gun Safe VT20i products, aka BlueSteal.","id":"CVE-2017-17435"},"products":["n/a"],"published":"2017-12-07","related":[{"cvss_score":8.8,"headline":"An issue was discovered in the software on Vaultek Gun Safe VT20i products, aka BlueSteal.","id":"CVE-2017-17435","kev_date_added":null,"published":"2017-12-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-08-05","vendors":["n/a"]},"summary":"Attackers can eavesdrop on unencrypted Bluetooth communications to steal passcodes from Vaultek Gun Safes, bypassing advertised security features.","url":"https://insights.sbomify.com/CVE-2017-17436/"}