{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-17627 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-17627 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-17627 is a medium-severity vulnerability in n/a, published on 16 Oct 2019. 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-2019-17627 and fix it if it is affected.\n\nWhat it is: CVE-2019-17627 is a medium-severity vulnerability in n/a, published on 16 Oct 2019. 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-2019-17627 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-2019-17627/ (Markdown: https://insights.sbomify.com/CVE-2019-17627/index.md)","id":"CVE-2019-17627","markdown":"https://insights.sbomify.com/CVE-2019-17627/index.md","name":"CVE-2019-17627","record":{"aliases":["GHSA-m65f-5cxc-g5pg"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Yale Bluetooth Key app","requires_auth":"none","summary":"Attackers can unlock Yale smart locks by sniffing Bluetooth traffic and calculating weak authentication keys, bypassing security controls.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"yale_bluetooth_key","vendor":"yalehome"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"The Yale Bluetooth Key application for mobile devices allows unauthorized unlock actions by sniffing Bluetooth Low Energy (BLE) traffic during one authorized unlock action, and then calculating the authentication key via simple computations on the hex digits of a valid authentication request. This affects the Yale ZEN-R lock and unspecified other locks.","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-2019-17627","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-17629"},"packages":[],"prev":{"headline":"XML Injection in ReportLab","id":"CVE-2019-17626"},"products":["n/a"],"published":"2019-10-16","related":[],"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 unlock Yale smart locks by sniffing Bluetooth traffic and calculating weak authentication keys, bypassing security controls.","url":"https://insights.sbomify.com/CVE-2019-17627/"}