{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-2354 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-2354 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-2354 is a high-severity missing authorization vulnerability in n/a, published on 22 Apr 2016. 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-2016-2354 and fix it if it is affected.\n\nWhat it is: CVE-2016-2354 is a high-severity missing authorization vulnerability in n/a, published on 22 Apr 2016. 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-2016-2354 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-2016-2354/ (Markdown: https://insights.sbomify.com/CVE-2016-2354/index.md)","id":"CVE-2016-2354","markdown":"https://insights.sbomify.com/CVE-2016-2354/index.md","name":"CVE-2016-2354","record":{"aliases":["GHSA-59jx-p9cf-966v"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Vehicle diagnostic tool","requires_auth":"none","summary":"Remote attackers can pair without a PIN to send arbitrary CAN commands, potentially disrupting vehicle braking or steering systems.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"bluedriver","vendor":"lemurmonitors"}],"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-284","name":"Improper Access Control"}],"description":"The Bluetooth functionality in Lemur Vehicle Monitors BlueDriver before 2016-04-07 supports unrestricted pairing without a PIN, which allows remote attackers to send arbitrary CAN commands by leveraging access to a device inside or adjacent to the vehicle, as demonstrated by a CAN command to disrupt braking or steering.","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":"Missing authorization in n/a","id":"CVE-2016-2354","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2016"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2016-2355"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2016-2353"},"products":["n/a"],"published":"2016-04-22","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":"Remote attackers can pair without a PIN to send arbitrary CAN commands, potentially disrupting vehicle braking or steering systems.","url":"https://insights.sbomify.com/CVE-2016-2354/"}