{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-14937 exists.","fix":"No fix has been published for CVE-2017-14937 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-14937 is a medium-severity vulnerability in n/a, published on 20 Oct 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-14937 and fix it if it is affected.\n\nWhat it is: CVE-2017-14937 is a medium-severity vulnerability in n/a, published on 20 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-14937 exists.\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-14937/ (Markdown: https://insights.sbomify.com/CVE-2017-14937/index.md)","id":"CVE-2017-14937","markdown":"https://insights.sbomify.com/CVE-2017-14937/index.md","name":"CVE-2017-14937","record":{"aliases":["GHSA-j2vv-fr99-j8xg"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Vehicle Airbag Control Unit","requires_auth":"low_privilege","summary":"Attackers with CAN bus access can detonate airbags due to weak authentication keys and lack of rate limiting, posing physical injury risks.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pcu","vendor":"pcu"}],"cvss":{"score":4.7,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"The airbag detonation algorithm allows injury to passenger-car occupants via predictable Security Access (SA) data to the internal CAN bus (or the OBD connector). This affects the airbag control units (aka pyrotechnical control units or PCUs) of unspecified passenger vehicles manufactured in 2014 or later, when the ignition is on and the speed is less than 6 km/h. Specifically, there are only 256 possible key pairs, and authentication attempts have no rate limit. In addition, at least one manufacturer's interpretation of the ISO 26021 standard is that it must be possible to calculate the key directly (i.e., the other 255 key pairs must not be used). Exploitation would typically involve an attacker who has already gained access to the CAN bus, and sends a crafted Unified Diagnostic Service (UDS) message to detonate the pyrotechnical charges, resulting in the same passenger-injury risks as in any airbag deployment.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":null,"kind":"metasploit","ref":"post/hardware/automotive/pdt","stars":null,"title":"Check For and Prep the Pyrotechnic Devices (Airbags, Battery Clamps, etc.)"}],"tier":"weaponised"},"has_fix":null,"headline":"Weak cryptography in n/a","id":"CVE-2017-14937","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Denial of service in n/a","id":"CVE-2017-14938"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2017-14935"},"products":["n/a"],"published":"2017-10-20","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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers with CAN bus access can detonate airbags due to weak authentication keys and lack of rate limiting, posing physical injury risks.","url":"https://insights.sbomify.com/CVE-2017-14937/"}