{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-16806 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-16806 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-16806 is a medium-severity vulnerability in n/a, published on 10 Sep 2018. 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-2018-16806 and fix it if it is affected.\n\nWhat it is: CVE-2018-16806 is a medium-severity vulnerability in n/a, published on 10 Sep 2018. 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-2018-16806 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-2018-16806/ (Markdown: https://insights.sbomify.com/CVE-2018-16806/index.md)","id":"CVE-2018-16806","markdown":"https://insights.sbomify.com/CVE-2018-16806/index.md","name":"CVE-2018-16806","record":{"aliases":["GHSA-9vcq-v52v-wfm2"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["security_bypass","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Tesla PKES system","requires_auth":"none","summary":"Attackers can clone Tesla key fobs using weak DST40 encryption, enabling unauthorized vehicle access and potential theft.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"passive_keyless_entry_and_start_system_firmware","vendor":"pektron"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"A Pektron Passive Keyless Entry and Start (PKES) system, as used on the Tesla Model S and possibly other vehicles, relies on the DST40 cipher, which makes it easier for attackers to obtain access via an approach involving a 5.4 TB precomputation, followed by wake-frame reception and two challenge/response operations, to clone a key fob within a few seconds.","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-2018-16806","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2018-16807"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-16805"},"products":["n/a"],"published":"2018-09-10","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 clone Tesla key fobs using weak DST40 encryption, enabling unauthorized vehicle access and potential theft.","url":"https://insights.sbomify.com/CVE-2018-16806/"}