{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-29438 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-29438 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-29438 is a medium-severity vulnerability in n/a, published on 30 Nov 2020. 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-2020-29438 and fix it if it is affected.\n\nWhat it is: CVE-2020-29438 is a medium-severity vulnerability in n/a, published on 30 Nov 2020. 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-2020-29438 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-2020-29438/ (Markdown: https://insights.sbomify.com/CVE-2020-29438/index.md)","id":"CVE-2020-29438","markdown":"https://insights.sbomify.com/CVE-2020-29438/index.md","name":"CVE-2020-29438","record":{"aliases":["GHSA-pjjj-hpx9-qmc6"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Tesla Model X key fob","requires_auth":"none","summary":"Attackers can bypass signature verification on Tesla key fobs to extract unlock codes from the secure enclave chip.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"model_x_firmware","vendor":"tesla"}],"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-347","name":"Improper Verification of Cryptographic Signature"}],"description":"Tesla Model X vehicles before 2020-11-23 have key fobs that accept firmware updates without signature verification. This allows attackers to construct firmware that retrieves an unlock code from a secure enclave chip.","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":"Security feature bypass in n/a","id":"CVE-2020-29438","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in n/a","id":"CVE-2020-29439"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2020-29437"},"products":["n/a"],"published":"2020-11-30","related":[{"cvss_score":4.6,"headline":"Auth bypass in n/a","id":"CVE-2020-29439","kev_date_added":null,"published":"2020-11-30"},{"cvss_score":4.6,"headline":"Security feature bypass in n/a","id":"CVE-2020-29440","kev_date_added":null,"published":"2020-11-30"}],"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-04","vendors":["n/a"]},"summary":"Attackers can bypass signature verification on Tesla key fobs to extract unlock codes from the secure enclave chip.","url":"https://insights.sbomify.com/CVE-2020-29438/"}